Hello,

 

I've been using my old server for over 10 years got my first alert email tonight about a disabled disk.  I just want to make sure it's just a bad disk and not that it's time to build out a new system entirely.  I haven't had to replace anything in the last 10 years of ownership.  I have upgraded the system to unraid 6.11.1.

 

Attached are output of the diagnostic logs and smart out put for disk1 which is now disabled.  Is there a way to confirm that it's simply the disk and not the sata port?  I don't have any extra ports on my mobo.  

 

Thanks!

tower-diagnostics-20230211-2229.zip tower-smart-20230211-2127.zip

Interestingly enough the SMART report you posted separately shows being unable to access the drive, while the one included in the diagnostics shows the drive accessible.  Did you reboot (or power cycle) the server between obtaining them?   The drive looks as though it could be OK although it is showing 1 Pending sector (i.e. a sector that cannot be read reliably), but these can often clear when the sector is rewritten.

 

Experience shows that cabling is more likely to be the cause of disk disabling than anything else.  Over time vibration can make SATA connections in particular prone to temporary disconnects if they are not properly seated.  Always worth checking the power and SATA cables are well seated.

 

Regarding the disk I think there is a good chance the disk is fine.   I would recommend running an Extended SMART test on the drive and if it completes without error assume the disk is fine, and can be re-used.  

 

The disabled state for a drive is cleared by rebuilding its contents.  The process is described here in the online documentation.  You need to decide whether to rebuild to the existing disk, or to rebuild to a new one.  Keeping the existing disk intact is slightly safer as it gives your more options if the rebuild fails for any reason but often this is not practical or economical for some reason.

 

BTW:  If you have just upgraded Unraid why did you go with 6.11.1 rather than 6.11.5 which is the current stable release?

Ok I'll buy a new disk and rebuild to that if it's safer.  No there was no power cycle in-between reports.  I just never clicked the upgrade array buttons to go to 6.11.5, I will when I get the array healthy again.

 

It looks like today the server started a read check.  It's going to take another 8 hours to complete but found 0 errors so far.  I'm not familiar with a read check but it looks like disk1 is still disabled.

 

 

I did not take any actions on the server to start rebuilding the disk or start / stop the array or anything.

 

Thanks!

1 hour ago, cobolstinks said:

It looks like today the server started a read check.  It's going to take another 8 hours to complete but found 0 errors so far.  I'm not familiar with a read check but it looks like disk1 is still disabled.

A read check is what happens when a ‘parity check’ is started but you currently do not have your array in a protected state.   In your case with a disabled data drive and single parity your array is not protected against further failure.

 

The disk will stay disabled until you carry out the rebuild process.