Yesterday I went to access some files on my unRAID server and noticed that I couldn't get into any of the shares.  I checked the status of the drives through the web interface and it appeared that everything was ok, so I restarted the server.  When everything was back up and running, I could access the shares, but after checking the web interface again, I noticed that one of my 5 disks (not including parity) was red rather than green.  After doing some investigating, it appeared that the solution to my problem was to remove the drive from the array and then re-add it.  Following this, the drive should be rebuilt.

 

I went through that process and all drives are now green, but now several files are missing.  The directories they were in appear, but they are all empty.  I just started to run a parity check and after only 1%, it shows hundreds of thousands of sync errors being detected.

 

I have a couple of questions:

 

Most importantly - can I recover from this type of issue?  The reason I went to unpaid in the first place was for redundancy.

Did I properly try to recover from the bad disk (red orb)?  Should I have done something differently?

 

 

Any help would be greatly appreciated.  I'm in a bit of a panic state since many of these files can't be replaced.

 

I am currently running unRAID 5.0.5

I have 4 WD Red 3TB drives, 1 WD Red 2TB drive and a WD Red 3TB parity drive

 

thanks in advance,

Nick

A quick update - I shut everything down and checked all of the connections.  Now I am showing that all drives are OK, except disk 5 is missing.  If I start up with the missing disk, all files appear to be intact.  The obvious issue is that I am now running unprotected.

 

What is the proper procedure to recover from this issue (assuming it isn't just a bad cable that needs replacing)?

Post SMART reports.

Thanks for replying.  Sorry for not posting the SMART reports in my original post.

 

I swapped the cable on drive 5 and it re-appeared.  I had to add it back into the array, but the system automatically rebuilt the files and everything appears to be running correctly now.