I presume that means the disk is disabled.  its a brand new drive that I ran a complete preclear on and it passed without any errors.  Once I finished the preclear, I simply added it to my array and then I see this on the main array page.  I looked at syslog and didnt find any errors (red) highlights.  I almost started a reiserfs check, but when I tried to do that, it kept saying the drive was busy so I didnt proceed any further.  I am able to access the GUI unmenu,and access to the shares seems completely normal.  It was just by chance that I happened to log onto the Main UI and thats when I saw the RED label on the new drive. 

 

I know for a fact that there is nothing on this drive, and I was tempted to unplug it, but havent done so.  Will wait for experts input - thank you in advance. 

 

Full syslog attached. 

syslog-2011-03-03.txt

I presume that means the disk is disabled.  its a brand new drive that I ran a complete preclear on and it passed without any errors.  Once I finished the preclear, I simply added it to my array and then I see this on the main array page.  I looked at syslog and didnt find any errors (red) highlights.  I almost started a reiserfs check, but when I tried to do that, it kept saying the drive was busy so I didnt proceed any further.  I am able to access the GUI unmenu,and access to the shares seems completely normal.  It was just by chance that I happened to log onto the Main UI and thats when I saw the RED label on the new drive. 

 

I know for a fact that there is nothing on this drive, and I was tempted to unplug it, but havent done so.  Will wait for experts input - thank you in advance. 

 

Full syslog attached. 

It is disabled because a write to it failed.

 

You might have anything from a loose cable to to a failed drive.

you are able to access its contents as simulated by the unRAID driver.  It is being re-constructed by reading the parity drive in combination with all the other data drives.  It will act normal except it being a tiny bit slower. (but not that much slower were you would see any effect when watching movies etc.)

 

No need to do a file-system-check as that would only check the "simulated" drive.

 

You need to stop the arrray

un-assign the drive

power down

check the connections to the drive, both power and data

power up

Start the array with the drive un-assigned (this will cause the aray to forget the modelseriala number of the drive so it will accept it as its own replacement)

Stop the array

re-assign the drive

Start the array and let it re-construct the disk onto itself.  Even though there are no files on the disk it is formatted and does have contents.

 

Joe L.

Thank you, Joe.  I didnt get your email before I went to bed, so I ran a reiserfsck on the 'disabled' drive and , as you said, it came up fine but still being reported as disabled.  I will go ahead and do as you said and have it reconstruct.  (I thought I had done that prior to my original post, but I will follow what you said and hopefully it does just that) 

 

Will report back when I get some results. 

By the way, when I stop the array, I do not even have an option to unassign it.  Even though it is coming up as disabled, its like the drive isnt even there.  In other words, when I go to the Drives section, the line where it should be is blank and the drop down box shows nothing. 

 

I will proceed as you said though - power down (array is stopped) and power up with it not connected. 

 

If my memory serves me, I did this last night, and even though the drive wasnt connected, it still came up as disabled. 

Ok, update:  stopped the array, powered down, unplugged cable (power and sata) powered up, and it shows the exact same thing - disk is "Not installed".  When I stop the array (it started automatically), and go to the drives section, obviously there is no option to select it since it is not connected.  Then I start the array and it shows the same thing - Disk not installed.  Screen shot attached.

Ok, looks like I am getting somewhere - powered it back down, and moved the card to a different slot (i noticed it wasnt getting recognized in the bios boot process) then it recognized it.  When I powered up , it showed on the drive page, and I assigned it.  There was a check box saying "im sure I want to do this" to start the array, which I did.  Now it says data rebuild in progress, quitting will leave array unprotected."  Letting it run out - might be a few hours. 

 

Thanks will report back when test is done.

Update - finished doing the rebuild.  Parity is good.  Drive shows up normal.  Looks like all is well.  Thank you, Joe L.  

Now run a parity check, just to be safe.  The data rebuild wrote all the data, the parity check will make sure it can be read back again.