1 |
Hello, |
2 |
|
3 |
I've recently made a few changes to my machine, and one of the unfortunate |
4 |
side effects is |
5 |
the following error. |
6 |
|
7 |
Mar 5 17:15:32 localhost kernel: [ 7.396912] ata14.00: qc timeout (cmd |
8 |
0xa1) |
9 |
Mar 5 17:15:32 localhost kernel: [ 7.398906] ata14.00: failed to |
10 |
IDENTIFY (I/O error, err_mask=0x4) |
11 |
Mar 5 17:15:32 localhost kernel: [ 7.706463] ata14: SATA link up 1.5 |
12 |
Gbps (SStatus 113 SControl 300) |
13 |
Mar 5 17:15:32 localhost kernel: [ 17.691838] ata14.00: qc timeout (cmd |
14 |
0xa1) |
15 |
Mar 5 17:15:32 localhost kernel: [ 17.742749] ata14.00: failed to |
16 |
IDENTIFY (I/O error, err_mask=0x4) |
17 |
Mar 5 17:15:32 localhost kernel: [ 17.792643] ata14: limiting SATA link |
18 |
speed to 1.5 Gbps |
19 |
Mar 5 17:15:32 localhost kernel: [ 18.098235] ata14: SATA link up 1.5 |
20 |
Gbps (SStatus 113 SControl 310) |
21 |
Mar 5 17:15:32 localhost kernel: [ 48.103265] ata14.00: qc timeout (cmd |
22 |
0xa1) |
23 |
Mar 5 17:15:32 localhost kernel: [ 48.154184] ata14.00: failed to |
24 |
IDENTIFY (I/O error, err_mask=0x4) |
25 |
Mar 5 17:15:32 localhost kernel: [ 48.509669] ata14: SATA link up 1.5 |
26 |
Gbps (SStatus 113 SControl 310) |
27 |
|
28 |
This causes my boot to pause while the kernel probes ports, which I'm fairly |
29 |
confident do not exist. I have x5 |
30 |
sata devices attached to my computer. They are all reported, and work |
31 |
great. I'm not sure where it's getting |
32 |
"ata14 from". |
33 |
|
34 |
I recently RMA'd my motherboard, and one of the first side effects I noticed |
35 |
was my ethernet (eth0) was |
36 |
completely missing. Through google, I found out udev had written the old |
37 |
device info from my previous motherboard |
38 |
in /etc/udev/rules.d/70-persistent-net.rules. Simply deleting this file and |
39 |
rebooting fixed that. |
40 |
|
41 |
Is it possible something very similar is going on here, but with my ata |
42 |
devices? |
43 |
|
44 |
I also swapped out a few disks today. I dropped an old raid0 in favor of an |
45 |
ssd, but everything went fine |
46 |
as far as I can tell. I'm not positive, but I think this error existed |
47 |
before I did this. |
48 |
|
49 |
Thanks for your time, |
50 |
Alan |