Hello, I've recently made a few changes to my machine, and one of the unfortunate side effects is the following error.
Mar 5 17:15:32 localhost kernel: [ 7.396912] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 7.398906] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ 7.706463] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 300) Mar 5 17:15:32 localhost kernel: [ 17.691838] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 17.742749] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ 17.792643] ata14: limiting SATA link speed to 1.5 Gbps Mar 5 17:15:32 localhost kernel: [ 18.098235] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Mar 5 17:15:32 localhost kernel: [ 48.103265] ata14.00: qc timeout (cmd 0xa1) Mar 5 17:15:32 localhost kernel: [ 48.154184] ata14.00: failed to IDENTIFY (I/O error, err_mask=0x4) Mar 5 17:15:32 localhost kernel: [ 48.509669] ata14: SATA link up 1.5 Gbps (SStatus 113 SControl 310) This causes my boot to pause while the kernel probes ports, which I'm fairly confident do not exist. I have x5 sata devices attached to my computer. They are all reported, and work great. I'm not sure where it's getting "ata14 from". I recently RMA'd my motherboard, and one of the first side effects I noticed was my ethernet (eth0) was completely missing. Through google, I found out udev had written the old device info from my previous motherboard in /etc/udev/rules.d/70-persistent-net.rules. Simply deleting this file and rebooting fixed that. Is it possible something very similar is going on here, but with my ata devices? I also swapped out a few disks today. I dropped an old raid0 in favor of an ssd, but everything went fine as far as I can tell. I'm not positive, but I think this error existed before I did this. Thanks for your time, Alan
