I'm doing a drive rebuild now and these errors are at the bottom of my syslog. I'll see several "failed" commands and not entirely sure what they are. Is it because there is a drive rebuild going on? I did post on another thread this drive took about an hour to mount, I'm not sure what unraid does to a drive before it mounts but maybe because of the drive size. Old drive was 1TB and this new drive is 4TB. And it is not doing a pre-clear or setting 0's. This is a direct drive swap, rebuild.

 

 

Mar 30 07:24:16 sun kernel: ata6.00: failed command: READ DMA EXT

Mar 30 07:24:16 sun kernel: ata6.00: cmd 25/00:00:d8:a1:44/00:02:0e:00:00/e0 tag 0 dma 262144 in

Mar 30 07:24:16 sun kernel:          res 51/40:ef:d8:a1:44/00:01:0e:00:00/e0 Emask 0x9 (media error)

Mar 30 07:24:16 sun kernel: ata6.00: status: { DRDY ERR }

Mar 30 07:24:16 sun kernel: ata6.00: error: { UNC }

Mar 30 07:24:16 sun kernel: ata6.00: configured for UDMA/133

Mar 30 07:24:16 sun kernel: ata6: EH complete

Mar 30 08:01:02 sun kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 30 08:01:02 sun kernel: ata6.00: failed command: IDENTIFY DEVICE

Mar 30 08:01:02 sun kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in

Mar 30 08:01:02 sun kernel:          res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 30 08:01:02 sun kernel: ata6.00: status: { DRDY }

Mar 30 08:01:02 sun kernel: ata6: hard resetting link

Mar 30 08:01:03 sun kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 30 08:01:03 sun kernel: ata6.00: configured for UDMA/133

Mar 30 08:01:03 sun kernel: ata6: EH complete

Mar 30 08:29:47 sun kernel: ata6: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Mar 30 08:29:47 sun kernel: ata6: irq_stat 0x00400040, connection status changed

Mar 30 08:29:47 sun kernel: ata6: SError: { PHYRdyChg DevExch }

Mar 30 08:29:47 sun kernel: ata6: hard resetting link

Mar 30 08:29:54 sun kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 30 08:29:54 sun kernel: ata6.00: configured for UDMA/133

Mar 30 08:29:54 sun kernel: ata6: EH complete

Mar 30 08:57:50 sun kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 30 08:57:50 sun kernel: ata6.00: failed command: IDENTIFY DEVICE

Mar 30 08:57:50 sun kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in

Mar 30 08:57:50 sun kernel:          res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 30 08:57:50 sun kernel: ata6.00: status: { DRDY }

Mar 30 08:57:50 sun kernel: ata6: hard resetting link

Mar 30 08:57:50 sun kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 30 08:57:50 sun kernel: ata6.00: configured for UDMA/133

Mar 30 08:57:50 sun kernel: ata6: EH complete

Mar 30 09:09:11 sun kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Mar 30 09:09:11 sun kernel: ata6.00: failed command: IDENTIFY DEVICE

Mar 30 09:09:11 sun kernel: ata6.00: cmd ec/00:01:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in

Mar 30 09:09:11 sun kernel:          res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)

Mar 30 09:09:11 sun kernel: ata6.00: status: { DRDY }

Mar 30 09:09:11 sun kernel: ata6: hard resetting link

Mar 30 09:09:11 sun kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 30 09:09:11 sun kernel: ata6.00: configured for UDMA/133

Mar 30 09:09:11 sun kernel: ata6: EH complete

Mar 30 09:14:29 sun kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x4010000 action 0xe frozen

Mar 30 09:14:29 sun kernel: ata6.00: irq_stat 0x00400040, connection status changed

Mar 30 09:14:29 sun kernel: ata6: SError: { PHYRdyChg DevExch }

Mar 30 09:14:29 sun kernel: ata6.00: failed command: READ DMA EXT

Mar 30 09:14:29 sun kernel: ata6.00: cmd 25/00:00:18:7d:c8/00:04:23:00:00/e0 tag 0 dma 524288 in

Mar 30 09:14:29 sun kernel:          res 50/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error)

Mar 30 09:14:29 sun kernel: ata6.00: status: { DRDY }

Mar 30 09:14:29 sun kernel: ata6: hard resetting link

Mar 30 09:14:37 sun kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Mar 30 09:14:37 sun kernel: ata6.00: configured for UDMA/133

Mar 30 09:14:37 sun kernel: ata6: EH complete

Here is a page that may answer some of your questions. http://lime-technology.com/wiki/index.php/The_Analysis_of_Drive_Issues

I believe even with a drive swap unraid writes zeros to the drive before it is ready to be added to the array.

My experience is that those errors typically indicate either a cabling issue or a power supply issue.

My experience is that those errors typically indicate either a cabling issue or a power supply issue.

 

That's what I thought it was for me as well, but I replaced my PSU and all of my sata cables and I still have those errors in my log. I've just learned to ignore them since they don't seem to affect anything.

My experience is that those errors typically indicate either a cabling issue or a power supply issue.

 

My Seasonics power supply fan doesn't even come on it runs so efficient and cool in the system. According to all my testing I've done with electrical tester it doesn't seem related to the PSU. "Everything" seems to be running just fine, maybe Tom can throw in a suggestion?

 

Check SMART reports for current_pending_sector RAW_VALUE greater than 0.

Check SMART reports for current_pending_sector RAW_VALUE greater than 0.

 

I checked all 14 of my drives and one drive had a raw value of 32 for current pending sector.

Maybe I should replace that drive. It still has 3 years warranty left on it.

If you have a spare use it now and then pre-clear the drive. Otherwise, start the array with the drive unassigned and then the start the array with the drive assigned. Rebuild the drive and check the pending sector count. It should be zero. No drive may have any pending sectors.