I had an 8TB WD Red drive die today with the red X.  Had 4 write errors.  I noticed it was only showing me half of my data from my good drive and none from the dead drive.  I could no longer write to my shares either.  I rebooted unRaid and I could write to my shares again but half of my data still is not showing.  I thought the parity drive was supposed to keep all data regardless of a failure?  I am purchasing a new 8TB tomorrow when it rebuilds will it show all my data again?  I really thought I should be able to access all my data even with a bad drive.  If anyone has some advice please let me know.  Thanks.

Go to Tools-diagnostics and attach the complete Diagnostics zip file to your NEXT post. 

Attached

storage-diagnostics-20200319-1919.zip

2 hours ago, ViSioN said:

I thought the parity drive was supposed to keep all data regardless of a failure?

The parity drive is not a backup. The concept of parity is pretty much always the same wherever it is used in computing and communications. Parity is just an extra bit that allows a missing bit to be calculated from all the remaining bits.

 

Disk2 is disabled and the emulated disk is unmountable. But, SMART for that disk looks OK. Best approach is to try to repair the filesystem of the emulated disk, then if that is OK rebuild the disk.

 

See here for repairing the filesystem:

 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

 

Be sure to capture any output so you can post it for further advice.

 

Here is the output.  The directions state it should state when the check is complete which I do not see where it states complete.  Also the directions state it will have in the output what repair I would need to do but I do not see that either.  Can you please look at the output and advise what to do next.

 

Thanks

unRaid check disk.txt

Run xfs_repair without -n, and use -L if needed.

 

Don't rebuild the disk on top of the old before checking data looks complete on the repaired filesystem.

I only used the -v and this is what it states

 

unRaid no -n option but used -v.txt

19 minutes ago, johnnie.black said:

and use -L if needed.

 

If this was very important to not lose any data one thing you might consider is cloning the bad drive to another one of identical size and then working on that cloned disk in another linux pc to try fix it. Just saying in case its like data you absolutely cannot lose.

I put the disk2 drive in another computer and it cannot see any files on the xfs file system.

Here is the output with the -Lv

Check disk with -Lv.txt

It appears all my data is showing.  I will check through and see.

 

Just to confirm you believe from the diag that my drive is good?  That is was just something that happened that caused it to error out?  Right now the duplicate unmounted Disk2 went away and only the Disk2 with the red X is showing now.  If I was going to reuse that drive what would the next steps be?  I have one on order and may still put the new one in and run tests on the current Disk2 and if good keep as a spare.

22 minutes ago, ViSioN said:

Just to confirm you believe from the diag that my drive is good?

Most likely, disk looks fine, but without the diags from when the disk got disable it's harder to say with more certainty.

 

24 minutes ago, ViSioN said:

If I was going to reuse that drive what would the next steps be?

https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive

 

Recommend replacing/swapping cables before doing this just to rule them out in case the same disk gets disable again.

 

Want to thank all you guys who helped me out with this.

5 hours ago, PeteAsking said:

If this was very important to not lose any data one thing you might consider is cloning the bad drive to another one of identical size and then working on that cloned disk in another linux pc to try fix it. Just saying in case its like data you absolutely cannot lose.

Since we were repairing the emulated disk, nothing was changed on the physical disk.