My unRAID Server has been running perfectly since setting it up in a HP Microserver N40L, however, when I returned home today I found one of my HDD's was 'red-balled'.

 

I first noticed the problem as I could not access the Server via SMB so logged in to check it's status. Initially all disks showed a green blinking light as they were spun down after the day's inactivity. I decided to stop the array and reboot as Windows was complaining about multiple connections, however, when I stopped the array one of the disks showed up as unallocated which gave me my first feelings of dread.

After a reboot the drive had a solid red-ball beside it. As advised online I once again stopped the array and shut-down, taking the drive out and re-inserting it to ensure it was connected/plugged-in correctly - all to no avail.

I then proceeded to run a smart report and saved a syslog and have attached them to this post.

 

Could someone with more experience with unRAID than myself please take a look at the attached files and advise what action I should take (I'm thinking I may need to RMA the drive as it is still under warranty luckily).

 

I should add that I had only just run a Parity check last night (1st of the month as is my routine) and it passed with 0 errors, so hopefully this is a good sign.

smart+syslog.zip

The SMART report has a FAILNG NOW status for the Spin Retry count so I would definitely RMA the drive.  In my experience once SMART report gives this status for ant values then the drive is likely about to experience a hard fail.  I am not sure how imminent a failure s when the Spin Retry count attribute is the one being reported as failing.

 

In the short term you can continue running without that drive present with UNRAID simulating it from the other drives plus parity.    However you will be running unprotected so another drive failing would lead to data loss so you need to decide what risk you are prepared to take.  If you have the space then you also might want to condisder copying the files off the 'failed' disk just in case a rebuild fails when you plug in a replacement.

Thanks for the advice.

 

I have enquired about an RMA already and will report back.

 

Does anyone else have information/experience with this error?