Hi guys.....

 

I had a power outage the other day and since it's come back up, one of the disks is giving trouble. See the attached image. It has about 700,000,000 "Errors" as is the only disk spinning although they are all set to spin down after 30 minutes.

 

When I brought the machine back up that disk was shown as "missing" in the array but was listed down in "Unassigned Devices". I was able to reboot and the array started back up.

 

The machine is new (but that disk is 2 years old) so only added the parity disk last night. Parity seemed to build OK and unRAID is telling me that parity is valid (so parity was build while this disk was showing these errors).

 

Last night the error count was 200,000,000 and now it's at 700,000,000+ but hasn't increased in the last few hours. I'm guessing the parity had something to do with it.

 

So what's my best course of action here? Get all the files off that disk to the empty 3TB one (also 2 years old) and replace it?

 

You have another disk with read errors, post the diagnostics, it would be best if they include the parity sync, i.e., you haven't rebooted since.

Thanks appreciate the response. I'm a bit new to all this.... What files do you need as the diagnostics add up to around 5MB (syslog.1.txt is massive). Or will I just put it all up on Dropbox and share?

Upload to dropbox and post the link.

Here you go. Again - appreciate the help

 

https://dl.dropboxusercontent.com/u/25925672/gru-diagnostics-20160708-0805.zip

There were many errors during the parity sync, so parity can't be used.

 

Disk4 dropped offline, so there's no SMART report, you should check/replace cabling, reboot and grab new diags.

 

Disk2 has pending sectors and should be replaced, since you don't have valid parity you should copy all data you can to another disk(s).

Great, thanks. I presume you mean the other way around with the disks?

 

Check disk 2 cabling a replace disk 4?

OK, might have just lost disk 4. See attached.

 

Are disks generally readable from another Linux based system (Mac with a USB->SATA adapter)?

Great, thanks. I presume you mean the other way around with the disks?

 

Check disk 2 cabling a replace disk 4?

 

No, disk 2 has pending sectors, it's not cable related, disk4 dropped offline, it can be a bad disk or bad cable, since there's no SMART report can't tell yet.

Thanks. Currently have the data being copied off disk2 so hopefully that will complete tomorrow. I'll have to RMA disk2 as I only bought it a few months ago. Disk4 is two months out of warranty so that's a write-off I think.

Changed the cable on Disk4 and it seems to be back up but is "unmountable". Any way to get the data off prior to formatting again?

Is there a green ball or red x net to it? Also post a SMART report for disk4.

Neither, an orange triangle. Running an extended SMART test now. I have a feeling that when I tried adding the drive back into the array, unRAID didn't recognise it and tried to rebuild the data (even though it's invalid).

 

Just realised I have a back up of the data on that drive so not overly concerned with recovering it (although it would be more convenient if I could). More concerned at this stage if I can trust this drive. I've ordered two replacement WD Reds anyway so I might just save this drive for a spare if I need it.

 

I'll RMA disk2 as it's still within warranty or get a refund through Amazon.

 

 

If you rebuild it data is probably all lost, since you're parity was invalid, if not doing a new config may bring it back.

SMART report for Disk4. Still running an extended test on Disk2

WDC_WD30EZRX-00DC0B0_WD-WCC1T1676060-20160710-1953.txt

SMART looks good.

Hopefully that looks like Disk4 is ok so maybe it was a cabling issue.

 

I'll RMA Disk2 or maybe just get a refund since I bought two Reds during the week

Came across this post when looking for the significance of reported disc errors. Yesterday, I saw that one of the discs reported 240 errors, see attached image. I had run a parity check before, which didn't turn up any errors, and then also a full SMART test, again, allegedly without showing errors; the report is attached as well. My question, and I hope someone more experienced than I can answer this, is whether or not this disc needs to be replaced right away. Also, in that case, and I haven't had to do this, how difficult is it to replace a disc and restore the array? I am imagining that one would somehow hook up the disc and run the preclear.sh routine before pulling the old disc and installing the new one in its place.

 

Thanks in advance for any advice,

Carsten

WDC_WD10EADS-00L5B1_WD-WCAU49184354-20160918-0824.txt

Came across this post when looking for the significance of reported disc errors. Yesterday, I saw that one of the discs reported 240 errors, see attached image. I had run a parity check before, which didn't turn up any errors, and then also a full SMART test, again, allegedly without showing errors; the report is attached as well. My question, and I hope someone more experienced than I can answer this, is whether or not this disc needs to be replaced right away. Also, in that case, and I haven't had to do this, how difficult is it to replace a disc and restore the array? I am imagining that one would somehow hook up the disc and run the preclear.sh routine before pulling the old disc and installing the new one in its place.

 

Thanks in advance for any advice,

Carsten

In something like this, diagnostics would tell the real truth as to what happened.

 

But, unRaid was unable to read 240 sectors from that disk.  It then re-wrote those sectors by calculating the appropriate values from the parity disk / other disks.  Since the write succeeded, the drive is not disabled.

 

Smart is clean on the drive, and its still a young drive.

 

Odds on, there was a momentary blip with the power to the drive (cabling?) or with the sata cable to the drive.

Thanks. I'll keep an eye on the error count in case it shoots up like reported by some forum members when a drive actually goes south hard.