Hello. I had a power outage a few days ago and when I restarted the server a parity check began. 48 hours later, parity check was still running and I finally gave up and cancelled it. There are quite a few errors in the logs from a specific disk, most of which read as follows. I did not attach the log file because it is nearly 5M and I wasn't sure it was necessary. If someone has any insight I would appreciate it -- but my gut is telling me I have a bad drive. I will gladly post the entire log if necessary.

 

TIA for any assistance,  erik

v 5.0-beta6a

 

 

 

ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen

Apr  6 05:19:49 Tower kernel: ata5.00: failed command: READ DMA EXT

Apr  6 05:19:49 Tower kernel: ata5.00: cmd 25/00:f8:a8:1d:1e/00:02:af:00:00/e0 tag 0 dma 389120 in

Apr  6 05:19:49 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)

Apr  6 05:19:49 Tower kernel: ata5.00: status: { DRDY }

Apr  6 05:19:49 Tower kernel: ata5: hard resetting link

Apr  6 05:19:49 Tower kernel: ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 310)

Apr  6 05:19:49 Tower kernel: ata5.00: configured for UDMA/100

Apr  6 05:19:49 Tower kernel: ata5.00: device reported invalid CHS sector 0

Apr  6 05:19:49 Tower kernel: ata5: EH complete

Apr  6 05:20:20 Tower kernel: ata5.00: limiting speed to UDMA/33:PIO4

 

The above repeats numerous times, and then there are groups of these:

 

 

Apr  6 05:20:51 Tower kernel: md: disk4 read error

Apr  6 05:20:51 Tower kernel: handle_stripe read error: 2937986408/3, count: 1

Apr  6 05:20:51 Tower kernel: md: disk4 read error

Apr  6 05:20:51 Tower kernel: handle_stripe read error: 2937986416/3, count: 1

Apr  6 05:20:51 Tower kernel: md: disk4 read error

Apr  6 05:20:51 Tower kernel: handle_stripe read error: 2937986424/3, count: 1

Apr  6 05:20:51 Tower kernel: md: disk4 read error

Apr  6 05:20:51 Tower kernel: handle_stripe read error: 2937986432/3, count: 1

 

 

Paste a SMART report.

Post a smart report but you probably have a loose cable to that drive.

Thanks for your replies and sorry for the delayed response. It's been a hectic week for me. Attached are 2 SMART reports on the smae drive. One is before reseating the cable (failed) and one after reseating (passed). I'm thinked bjp999 may have been correct. I am in process on a new parity check to see what happens. Will update after check is complete (tomorrow hopefully).

Nothing is attached.

Oops 

 

sdf_SMART_Report_Before_Cable_Reseat.txt

sdf_SMART_Report_After_Cable_Reseat.txt

Those two reports are for different disks going by the serial numbers!  I thought you were suggesting they were the same disk?

 

The first one is for a very sick disk that should be removed from service, and if still under warranty RMA'ed.

 

The second one looks fine.

Darn it! Double embarrasment   

 

I did grab the wrong disk the second time. I just reran and it failed again. Looks like I need to replace, it is well out of warranty. Thanks for catching that.

 

Can anyone point me the way to the proper procedure to replace a disk. This is my first failure. Here is what I want to do:

 

1) replace failed disk

2) upgrade failed disk and parity disk to 4TB (currently both are 2TB)

3) upgrade to current release version of UnRAID.

 

I will now begin my search through the wiki & forum for the proper way, but any pointers or links to detailed instructions would be appreciated.

 

Thanks in advance.

 

 

erik

Darn it! Double embarrasment   

 

I did grab the wrong disk the second time. I just reran and it failed again. Looks like I need to replace, it is well out of warranty. Thanks for catching that.

 

Can anyone point me the way to the proper procedure to replace a disk. This is my first failure. Here is what I want to do:

 

1) replace failed disk

2) upgrade failed disk and parity disk to 4TB (currently both are 2TB)

3) upgrade to current release version of UnRAID.

 

I will now begin my search through the wiki & forum for the proper way, but any pointers or links to detailed instructions would be appreciated.

 

Thanks in advance.

 

 

erik

 

There is a procedure that will allow you to replace your parity drive with a larger disk, and recover you failed disk onto what used to be the parity disk. It is called parity swap disable. I have never done it myself, but seems like what you need 

 

Follow the instructions HERE.

Thanks bjp! That sounds even better (cheaper anyhow). Does the new disk need to be pre-cleared or anything prior to taking these steps? Any other things I should do first?

 

erik

Thanks bjp! That sounds even better (cheaper anyhow). Does the new disk need to be pre-cleared or anything prior to taking these steps? Any other things I should do first?

 

erik

 

If it is a new disk, I would preclear it. Would be good to know the disk passed this pretty good burnin test before putting it in service.

 

But preclearing does not speed up the swap disable process and is not technically required.