One of my drives just red balled. It showed some errors. I didn't expect it from this drive, it does not show any errors in the SMART report. So I rebooted the computer, thinking that it might bring it back online. I forgot to get the system log first though.

 

Did a SMART short test and didn't get any errors. (I'll attach the report)

 

How can I re-add the drive and see if this was just a freak incident? Or is there a reason not to add it back?

 

smart_report.txt

I think the red ball means that unRAID has removed it from the array. It's probably from a write error. I don't think it will bring it back online unless forced to. I'm not sure it will do it with the same drive.

 

I had a similar problem, and I replaced the drive in the system. unRAID rebuilt the data from parity onto the new drive, and everything was fine.

I think the red ball means that unRAID has removed it from the array. It's probably from a write error.

It WAS a write error.  it is the only time unRAID will mark a drive as invalid and show the "red" indicator.   

I don't think it will bring it back online unless forced to.

That is true.  The array must "forget" the model/serial number of the current drive to have it use it as its own replacement.

I'm not sure it will do it with the same drive.

Yes it will.  Here's how:

 

1. Stop the array by pressing "Stop" on the main web-management page.

2. Power down the array and check the connections to the drive.  It could be as simple as a loose cable.

3. Power back up.

 

4.  Un-assign the drive with the "red" indicator on the devices page.

5.  Use the "Start" button on the main web-management page to start the array without the failed drive assigned  (This causes it to forget the model/serial number)

6.  Stop the array once more by pressing "Stop" on the main web-management page.

7.  Re-assign the failed drive on the "Devices" page.

8.  Use the "Start" button on the main web-management page to start the array.  The contents of the failed drive will be re-constructed onto itself.  The re-constructed contents will contain the correct contents of the "write" that had originally failed as well as any subsequent "writes" you may have made to the drive.

 

When the re-construction is complete, the indicator will go back to being "green"

I had a similar problem, and I replaced the drive in the system. unRAID rebuilt the data from parity onto the new drive, and everything was fine.

If you replace the failed drive with a different drive it is only necessary to "Start" the array. No need to use the devices page at all to un-assign the old drive and assign the new.  unRAID will figure it out on its own when it see the new disk.

 

Joe L.

Make sure you try to figure out why the drive was kicked from the array.  It normally is caused by a bad or intermitent cable connection. At a minimum you should reattach both cables. If you do nothing but rebuild the data, whatever happened will likely happen again.

Next time the drive is removed from the array post a copy of your syslog BEFORE you reboot the machine.  Your last reboot erased the syslog file that contained clues as to how the drive failed.

Thanks Joe L. Soon as I got the unraid interface back up after the reboot I realized if forgot to get the syslog. I meant to but forgot.

 

I'll check the data cables and such, I haven't been inside the comp in over a month. I notice that anytime there is drive that gets write errors that everyone's first response is to check the cabling. I understand that is a necessary thing to check but, if you haven't been inside the computer and it hasn't been moved you would think nothing would have changed inside. Can cables actually go bad?? I also use locking cables to help prevent a cable from coming loose.

 

I thought I might have to basically do what you outlined Joe L. but wasn't sure and didn't want to do something wrong. User error is about all I worry about with unraid, glad that this forum is here and everyone is so helpful.

 

Thanks all.

 

Oh, I was also wondering if it would be possible for the syslog to automatically be saved every shutdown? I know it is not hard to save it but would be nice if it did it one it's own so you would not have to remember to save it.