I'm running 4.5 release

 

The icon is red, unmenu says the drive is disabled, yet I can't figure out what is wrong. The syslog looks ok, I think and the Smart Report doesn't show anything bad that I can tell. I've checked the cables and still nothing has changed. The Errors counters are all 0. I can even access the drive share. Is there an easy way to see why unraid has marked it disabled? There's obviously something it doesn't like. It would be nice if it clearly stated it somewhere. I've attached the syslog. Any help is appreciated.

 

Thanks,

Adrian

syslog-2010-01-16.txt

The syslog apparently is from after you rebooted the server.  It does not contain the clues as to why your disk has been taken out of service.

 

a disk in unRAID is disabled when a "write" to it fails.    Once a disk is disabled, it is "simulated" with all of its data, by reconstructing what would be there if it was not disabled.  Since the "write" to it failed, the data on it is considered out-of-date and invalid. 

 

You say you've run a SMART report... That is good if the disk can respond.  It might still be an intermittent power or data cable to the disk that caused it to go off-line.  It will NOT go back on-line until you

1. stop the server

2. un-assign the drive on the devices page (this will cause it to forget the model/serial of the existing drive)

3. re-start the server with the disk un-assigned.  (An un-assigned disk is exactly like a failed disk, you will still be able to get to its contents through the RAID array's ability to simulate the drive by reconstructing the contents on the fly from parity and the other data disks.)

4. stop the server once more

5. re-assign the failed disk (it will think it is new, since it forgot the model/serial number in the above step)

6. re-start the server a final time.  It will probably prompt you to reconstruct the failed data onto the "new" disk it sees.  check the box under "Start" and press "Start' to begin the process.  DO NOT press the button labeled "restore" as it will immediately invalidate parity and the data on the failed disk will be lost.  (a really bad thing if the disk does have an intermittent fault)

 

Since "writes" to the disk have failed, you are NOT a candidate for the trust-parity process you might find mentioned while browsing through the forums. (in my opinion)

 

as I said, if you had captured a syslog before rebooting we might have had more clues to work on.

 

Whatever you do, don't press "restore" and don't add or remove any of the other disks.  You are not protected from a second disk failure until you get all green indicators once more.  Be extra careful in moving the cables to the drives... don't want to add to your headache.

 

Joe L.

I had actually already started all the steps described, with the difference that I actually also moved it to another free port thinking it could have been the port that was bad. So glad that you've confirmed the steps I've taken so far. I had replaced the cable and nothing changed. It is currently rebuilding the data on the drive. Looks like it has another 10-11 hours to go. There was a power issue about 2 days ago, so hopefully that is was caused it to disable the drive. Otherwise, I guess I'll have to run out and buy a replacement drive tomorrow.