All,

 

Version beta5.0-beta6a

 

I've had issues with disk4 in my array.  I noticed a month or so ago that it had been disabled.  I replaced it with a new drive, but didn't really thing the original drive was bad.  It is still sitting on my desk waiting for me to test it.  Now I see as of yesterday disk4 is again disabled.

 

I shutdown, opened the case and replaced the IDE cable with a new one, and checked the power connection.  I restarted.

 

I can now via unMenu run a smart test on it and it passes, I've attached the report.

 

I looked at my syslog and don't see anything in the log file that would hint as to what is wrong with hdf or disk 4.  I've attached it as well.

 

I've stopped and restarted the array, but the disk4 continues having a red dot by it, not sure what that means, but its not green so I'm assuming it is bad.  I don't have an option to run a parity check and unRaid reports that my configuration is valid.

 

Ideas?

 

thanks,

dave

smarttest.txt

syslog-2011-07-09.txt

All,

 

Version beta5.0-beta6a

 

I've had issues with disk4 in my array.  I noticed a month or so ago that it had been disabled.  I replaced it with a new drive, but didn't really thing the original drive was bad.  It is still sitting on my desk waiting for me to test it.  Now I see as of yesterday disk4 is again disabled.

 

I shutdown, opened the case and replaced the IDE cable with a new one, and checked the power connection.  I restarted.

 

I can now via unMenu run a smart test on it and it passes, I've attached the report.

 

I looked at my syslog and don't see anything in the log file that would hint as to what is wrong with hdf or disk 4.  I've attached it as well.

 

I've stopped and restarted the array, but the disk4 continues having a red dot by it, not sure what that means, but its not green so I'm assuming it is bad.  I don't have an option to run a parity check and unRaid reports that my configuration is valid.

 

Ideas?

 

thanks,

dave

it is in the wiki:

http://lime-technology.com/wiki/index.php?title=FAQ#What_does_the_Red_Ball_mean.3F

http://lime-technology.com/wiki/index.php?title=FAQ#How_do_I_re-enable_a_failed_disk.3F

 

Joe,

 

I tried what it says:

 

1. recorded drive assignment

2. stopped array

3. unassigned disk4 (no device)

4. reboot

 

Upon reboot the red dot still is there, and disk4 is assigned to the drive that I previously unassigned it from.

 

What am I doing wrong?

 

thanks,

dave

Joe,

 

I tried what it says:

 

1. recorded drive assignment

2. stopped array

3. unassigned disk4 (no device)

4. reboot

 

Upon reboot the red dot still is there, and disk4 is assigned to the drive that I previously unassigned it from.

 

What am I doing wrong?

 

thanks,

dave

you did not do what it says.

 

stop array

un-assign drive

start array with it un-assigned

stop array

re-assign drive

start array once more. (might have to check "I'm sure" checkbox)  Disk will be re-constructed onto itself.

 

Nowhere do you need to reboot.

 

Joe L.

I want to rebuild the drive as I've done writes to the drive (many pictures) and need to keep these.  

So here is what I read:

If however you have made changes to the drive that you do not want to lose, or do not want to risk file-system corruption, then you will need to rebuild the drive in-place, with the following procedure (very similar to replacing a failed drive).

 

   On the Devices page of unRAID Web Management, record the current drive assignments by screen capture, screen print, or old-fashioned notes by hand

   Stop the array, go to the Devices page and un-assign the disk

   Reboot the server

   Stop the array, go to the Devices page and re-assign the disk

   Go back to the Main page - the system should detect a "new" drive for the one disabled, click the Start button to start the rebuild (parity-reconstruct) of the disk (you may have to click the little check box under the Start button that says "I'm sure I want to do this") (post with screen shots)

   Drive will now be rebuilt, takes a while; the array can be used at the same time, but we recommend waiting until the rebuild is complete. The procedure of un-assigning the drive, starting the array without it, and then re-assigning it allows a drive to be used as its own replacement.

 

Does this no longer work?

 

BTW I did what you outlined above and it is rebuilding now.

 

Rebuild just finished and it ran fine.  Ordered a new single rail 650W Corsair power supply as I think it is power supply related.

 

Thanks Joe for the help.