000026237 - How to fix RSA NetWitness JBOD drives that are in an unconfigured (bad) state

It has been found that in some cases when there is a power outage or some other situation to cause the JBOD to reset or loose communication with the appliance it will mark all drives as unconfigured(bad). When in this state the system will not boot properly due to the mismatch in the /etc/fstab and what is available.

In most cases the fix is to set all the drives to good and then import the foreign configuration. To set the drives to a good state first determine the list of drives and there enclosure ID. Get this from the follwoing command:
  /opt/MegaRAID/CmdTool2/CmdTool2 -PDList -a0 or
  /opt/MegaRAID/MegaCli/MegaCli64 PDList a0
This will dump a verbose list of all the drives and there information. Extract the enclosure ID an list of drives which need to be configured as good (typically all the drives in the enclosure will be in this state when this occurs). Once the information has been obtained enter the following command to configure them good:
  /opt/MegaRAID/CmdTool2/CmdTool2 -PDMakeGood -PhysDrv[E#:S#,E#:S#,...] -Force -a0 or
    /opt/MegaRAID/MegaCli/MegaCli64 PDMakeGood PhyDrv[E#:S#,E#:S#,...] Force a0
Note: The list of drives is a combination of EnclID(E#):SlotID(S#) pairs separated by commas.
After all the drives have been configured good you will likely need to import the foreign configuration. Enter the following command to import foreign configuration:
    /opt/MegaRAID/CmdTool2/CmdTool2 -CfgForeign -Import -a0 or
   /opt/MegaRAID/MegaCli/MegaCli64 CfgForeign Import a0
At this point a rerun of the PDList should show all drives in "Online" state. If so, you should be able to reboot the appliance and the file system should be back to normal. If not, contact support for further assistance.