all disks foreign

NoobofNoobs,

With your current situation you would need to Import the foreign configuration. A good rule of thumb with Foriegn configs is that if the Virtual DIsk is bootable you would Clear the Foreign, when it isn't bootable you would need to IMport it.

To explain the situation, a foreign is basically identified when the Virtual Disk configuration details stored on the drives doesn't match what is stored on the controller. By Importing you are telling the controller to use the configuration stored on the drives, where selecting to Clear it would tell it to use the configuration info stored on the controller.

Now the reason we are selecting to Import the foreign over clearing it is that you can't boot, because if the controllers configuration data was correct you would be able to do so, since you can't we need to go with the configuration on the drives.

Let me know if this helps.

. 

is it possible to try both?

import foriegn no clear

then if issues, import foriegn with clear

one of the virtual disks is ok, online

its the second vd that has all the foreign disks..

Hi Chris, that was confusing and i had to read it multiple times

you are saying do a straight import, dont clear the config 

correct

Hello,

Yes, that is something you can do - try the import, then try clearing it, should importing fail. The import process is not destructive. The controller just attempts to read the RAID metadata and then import the drives.

THANKS

import worked, no clear

machine booted and partition readable

one drive degraded state after import ,all good getting replaced