Hi,

 

I have a system with 10 drives running 4.7 in the past year. Recently I found a bad drive (disk6 turned red on the Main), so I followed the instruction (http://lime-technology.com/forum/index.php?topic=2591.msg20919#msg20919) on the forum to remove the drive. When I started parity sync, it was very very slow, so I took a look at the syslog and found the following messages:

 

Dec 30 23:33:00 Tower kernel: ata12: drained 32768 bytes to clear DRQ.

Dec 30 23:33:00 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Dec 30 23:33:00 Tower kernel: ata12.00: failed command: READ DMA EXT

Dec 30 23:33:00 Tower kernel: ata12.00: cmd 25/00:00:0f:d9:07/00:04:01:00:00/e0 tag 0 dma 524288 in

Dec 30 23:33:00 Tower kernel:          res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation)

Dec 30 23:33:00 Tower kernel: ata12.00: status: { Busy }

Dec 30 23:33:00 Tower kernel: ata12.00: error: { ICRC UNC IDNF ABRT }

Dec 30 23:33:00 Tower kernel: ata12: hard resetting link

Dec 30 23:33:00 Tower kernel: ata12: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Dec 30 23:33:00 Tower kernel: ata12.00: configured for UDMA/100

Dec 30 23:33:00 Tower kernel: ata12: EH complete

Dec 30 23:34:24 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec 30 23:34:24 Tower kernel: ata12.00: BMDMA2 stat 0x6d0009

Dec 30 23:34:24 Tower kernel: ata12.00: failed command: READ DMA EXT

Dec 30 23:34:24 Tower kernel: ata12.00: cmd 25/00:00:27:28:72/00:04:01:00:00/e0 tag 0 dma 524288 in

Dec 30 23:34:24 Tower kernel:          res 51/04:bf:27:28:72/00:00:00:00:00/e0 Emask 0x1 (device error)

Dec 30 23:34:24 Tower kernel: ata12.00: status: { DRDY ERR }

Dec 30 23:34:24 Tower kernel: ata12.00: error: { ABRT }

Dec 30 23:34:24 Tower kernel: ata12.00: configured for UDMA/100

Dec 30 23:34:24 Tower kernel: ata12: EH complete

Dec 30 23:34:37 Tower kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Dec 30 23:34:37 Tower kernel: ata12.00: BMDMA2 stat 0x6d0009

Dec 30 23:34:37 Tower kernel: ata12.00: failed command: READ DMA EXT

Dec 30 23:34:37 Tower kernel: ata12.00: cmd 25/00:00:27:5e:82/00:04:01:00:00/e0 tag 0 dma 524288 in

Dec 30 23:34:37 Tower kernel:          res 51/04:6f:27:5e:82/00:00:00:00:00/e0 Emask 0x1 (device error)

Dec 30 23:34:37 Tower kernel: ata12.00: status: { DRDY ERR }

Dec 30 23:34:37 Tower kernel: ata12.00: error: { ABRT }

Dec 30 23:34:37 Tower kernel: ata12.00: configured for UDMA/100

Dec 30 23:34:37 Tower kernel: ata12: EH complete

 

The complete syslog is attached.

I have to stop the parity rebuild since it won't go any further. Now the array is in not protected state. I'd appreciate if anyone could help.

 

Thanks,

--Tom

syslog_20121230.txt

Attach smartctl scan report for all the drive. I am not familiar where to look, so please let me know if there is any indication of disk error.  On the unRAID main page, all the disks show green so far except for the Parity disk which shows red. I am not sure if it is because of syn error?

 

--Tom

smartctl_report_20121231.txt

I suspected the issue with the drive and then the SATA port. The smartctl report no error on every drive, so it might be the port. I opened the case, found the "problem(not really bad)" drive was connected to a 2-port SATA card. I move the cable from the card to the port on the motherboard, which was originally connected to the failure drive I just removed earlier.  I then SYNC the array again and no error at all. The conclusion is that I have a failure drive and bad SATA card in the system from the beginning. Both need to be fixed.

 

--Tom