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