Woke up this morning to a red balled disk.

 

History

 

There was a monthly no correct parity check last night. It never finished.

 

Can not run a smart report on the disk, "No such device".

 

We did have a short power failure yesterday and it appears the tower did okay since I have an UPS.

 

This is my newest disk, Oct-2012, survived preclear. I have not shut it down in case someone wants me to something first. 

 

I'm on 4.7, syslog attached.

 

What do I do next?

syslog-2013-02-01.zip

If you cannot get a SMART report, and it no longer exists as a device, either a cable to it has loosened, or gone bad, or the drive has died, or locked up.

 

In any case, stop the array, power down, re-seat the cables to the drive (and re-seat the drive tray if it is in one)

 

Be super careful to NOT disturb any other cables.  (Don;t want two bad drives)

 

Then power up and see if the drive shows itself in the BIOS, or will respond to a SMART report request.

Make sure you use the correct device name, as it can change from one boot to the next.

 

If the drive does not respond, or no longer shows itself to unRAID, you can try a  different cable, or different disk controller port.  If it still does not respond, RMA it. 

 

Joe L.

Thanks for the reply Joe.

 

Powered down, reseated cable, powered up. obtained smart report (attached), s/n matches disabled disk. Looks good, I think?

 

What next?  Trust or Rebuild? I have not written to the drive since it was red balled.

smartdisk2.txt

Thanks for the reply Joe.

 

Powered down, reseated cable, powered up. obtained smart report (attached), s/n matches disabled disk. Looks good, I think?

 

What next?  Trust or Rebuild? I have not written to the drive since it was red balled.

The only way it would be "red" is if a write to it failed. Even if you do not write to it, it is written to when being mounted. (or attempted to be mounted)  In that respect, the parity drive was updated to show the "writes", but the disk was not.  Parity is therefore potentially out-of-sync.  You can try the "trust" process, but I'd run a parity check afterwords regardless, and not be surprised if there are some corrections to parity.

I got impatient and decided to do a rebuild and exercise the disk since it needs to write everything and we'll see about what turns up in the next smart report.