March 1, 201115 yr I've been running Unraid for almost a year, never any issues. I woke up to the error below in the syslog. Good news, I have no sync errors. The error also created a Ultra DMA CRC Error Count on the drive, now 1. The controller (PCIx-1 from Monoprice) was just added three days ago. 1TB of data was added since to the drive. Everything went well, no errors. The drive was an existing drive. Other than the Ultra DMA CRC Error Count SMART report looks good just like the other drives. Is it the cable? controller? Or HD? Mar 1 00:00:01 Tower kernel: mdcmd (1357): check NOCORRECT Mar 1 00:00:01 Tower kernel: Mar 1 00:00:01 Tower kernel: md: recovery thread woken up ... Mar 1 00:00:01 Tower kernel: md: recovery thread checking parity... Mar 1 00:00:02 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Mar 1 00:00:11 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Mar 1 00:00:11 Tower kernel: ata1.00: irq_stat 0x00020002, device error via D2H FIS Mar 1 00:00:11 Tower kernel: ata1.00: failed command: READ DMA EXT Mar 1 00:00:11 Tower kernel: ata1.00: cmd 25/00:00:ff:94:03/00:04:00:00:00/e0 tag 0 dma 524288 in Mar 1 00:00:11 Tower kernel: res 51/84:8f:ff:94:03/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) Mar 1 00:00:11 Tower kernel: ata1.00: status: { DRDY ERR } Mar 1 00:00:11 Tower kernel: ata1.00: error: { ICRC ABRT } Mar 1 00:00:11 Tower kernel: ata1: hard resetting link Mar 1 00:00:13 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Mar 1 00:00:13 Tower kernel: ata1.00: configured for UDMA/100 Mar 1 00:00:13 Tower kernel: ata1: EH complete Need help from the experts.
March 1, 201115 yr I typically see 2 to 4 of those a week for the 2+ years the 1T Seagates have been in my server. No big deal if it resets and continues to work. Peter
March 2, 201115 yr I've been running Unraid for almost a year, never any issues. I woke up to the error below in the syslog. Good news, I have no sync errors. The error also created a Ultra DMA CRC Error Count on the drive, now 1. The controller (PCIx-1 from Monoprice) was just added three days ago. 1TB of data was added since to the drive. Everything went well, no errors. The drive was an existing drive. Other than the Ultra DMA CRC Error Count SMART report looks good just like the other drives. Is it the cable? controller? Or HD? Mar 1 00:00:01 Tower kernel: mdcmd (1357): check NOCORRECT Mar 1 00:00:01 Tower kernel: Mar 1 00:00:01 Tower kernel: md: recovery thread woken up ... Mar 1 00:00:01 Tower kernel: md: recovery thread checking parity... Mar 1 00:00:02 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Mar 1 00:00:11 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Mar 1 00:00:11 Tower kernel: ata1.00: irq_stat 0x00020002, device error via D2H FIS Mar 1 00:00:11 Tower kernel: ata1.00: failed command: READ DMA EXT Mar 1 00:00:11 Tower kernel: ata1.00: cmd 25/00:00:ff:94:03/00:04:00:00:00/e0 tag 0 dma 524288 in Mar 1 00:00:11 Tower kernel: res 51/84:8f:ff:94:03/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) Mar 1 00:00:11 Tower kernel: ata1.00: status: { DRDY ERR } Mar 1 00:00:11 Tower kernel: ata1.00: error: { ICRC ABRT } Mar 1 00:00:11 Tower kernel: ata1: hard resetting link Mar 1 00:00:13 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 0) Mar 1 00:00:13 Tower kernel: ata1.00: configured for UDMA/100 Mar 1 00:00:13 Tower kernel: ata1: EH complete Need help from the experts. ICRC errors are communication errors detected in communicating with the drive over the SATA cable. (It has its own checksums) If you have bundled the SATA cables with the power cables, separate them. You might want to re-seat the SATA cable, just in case.
March 2, 201115 yr Author I'll give that a try Joe. That's what I get for trying to tidy things up after adding the new card. I've got some new cables on order too, didn't have the right length and had to use the ones that came with the motherboard. Thanks
Archived
This topic is now archived and is closed to further replies.