I have a disk that showed up as not installed part way during a parity check, but I believe it was a power connector problem. I unassigned and reassigned it, and now it's blue. I believe parity info is fine, but have no problem redoing parity-sync afterwards.

I'd just like to know how to proceed right now without having to rebuild the disk and get the whole array green again when I start it up. I believe all the data is there, I don't want to run an initconfig if that's the wrong thing to do. Help appreciated.

I have a disk that showed up as not installed part way during a parity check, but I believe it was a power connector problem. I unassigned and reassigned it, and now it's blue. I believe parity info is fine, but have no problem redoing parity-sync afterwards.

I'd just like to know how to proceed right now without having to rebuild the disk and get the whole array green again when I start it up. I believe all the data is there, I don't want to run an initconfig if that's the wrong thing to do. Help appreciated.

If you are absolutely certain it was a power problem you can initialize the disk configuration.  If you have any doubt and the disk is actually bad, you'll lose the parity protection and the data on the disk.

 

Best just to let the disk re-construct it onto itself.  Don't initialize the configuration.

 

Just start the array.  The description should say something about re-constructing the replacement drive.

Hi Joe

 

Thanks for the response. Something weird happened. I did an initconfig. All disks are blue-balled. I tried mdcmd set invalidslot 99, but I don't get:

 

 

 

cmdOper=set

cmdResult=ok

 

I just get the next command prompt.

 

 

 

Hi Joe

 

Thanks for the response. Something weird happened. I did an initconfig. All disks are blue-balled. I tried mdcmd set invalidslot 99, but all I get is:

 

 

-bash: mdcmd: command not found

 

WTF that's never happened before.

It is in the /root directory.

 

Use

/root/mdcmd set invalidslot 99

 

Hi Joe

 

Yes I screwed up and accidentally typed cd /boot instead of cd /root the first time. However, when I fixed it (before your post - thanks again!), the above happened - see my edited post. So I've got everything blue-balled and haven't hit start yet.