IBM Support

QRadar: Drive will not rebuild due to foreign config

Troubleshooting


Problem

When there is foreign configuration found on a replacement drive (hard disk drive or solid-state drive), the rebuild fails to start.

Cause

Each drive in a Broadcom/Avago/LSI RAID controller virtual drive contains a backup copy of the RAID controller's running virtual drive configuration. Foreign configuration is virtual drive configuration that is stored on a drive that does not match the current virtual drive configuration on the host machine. 
The drive might contain a foreign configuration, if a drive was removed from a host machine during a time where the configuration of the virtual drive was updating, or if a replacement drive was previously configured in a virtual drive configuration in a different host.

Diagnosing The Problem

The physical drive state and location information of each drive on controller 0 can be discovered with the show all enclosures; all slots command:
/opt/MegaRAID/storcli/storcli64 /c0/eall/sall show
Example Output 1
Drive Information :
=================

----------------------------------------------------------------------------
EID:Slt DID State DG     Size Intf Med SED PI SeSz Model            Sp Type
----------------------------------------------------------------------------
134:0     0 Onln   0 7.276 TB SAS  HDD N   N  512B MG06SCA800E      U  -
134:1     7 UBad   - 7.276 TB SAS  HDD N   N  512B MG06SCA800E      U  -
134:2     1 Rbld   0 7.276 TB SAS  HDD N   N  512B MG06SCA800E      U  -
....
Example output 1 shows the enclosure ID (EID), drive slot number (Slt), drive ID (DID), drive state, and disk group (DG) for each physical drive.
We also see the physical drives that are listed show slot 0 as online (Onln), slot 1 as unconfigured bad (UBad) and not currently part of a disk group, and slot 2 as rebuilding (Rbld).

Resolving The Problem

To ensure if the drive is rebuilding, first check the status of the replacement drive once it is inserted. If the drive state shows rebuilding (Rbld), no further action is required as the drive is already rebuilding.
/opt/MegaRAID/storcli/storcli64 /c0/eall/sall show
If you see the state of the drive you replaced is UBad or UGood (unconfigured good), take note of the EID and Slot number of the replacement drive.
Example output 2
EID:Slt DID State DG     Size Intf Med SED PI SeSz Model            Sp Type
----------------------------------------------------------------------------
134:0     0 Onln   0 7.276 TB SAS  HDD N   N  512B MG06SCA800E      U  -
134:1     7 UBad   - 7.276 TB SAS  HDD N   N  512B MG06SCA800E      U  -
In example output 2, you are replacing the drive in slot 1 and can see slot 1 drive shows UBad.  Use the EID and Slot number to look at the detailed drive information to verify whether the drive contains foreign configuration. Based on example output 2, you use "/e134/s1" to look up the drive in EID:Slt 134:1.
/opt/MegaRAID/storcli/storcli64 /c0/e134/s1 show all
Check the “Firmware State” and the “Foreign State”

If the “Firmware State” shows “Unconfigured(bad)”, then you need to set the drive to “good” first before you can start the rebuild.
/opt/MegaRAID/storcli/storcli64 /c0/e134/s1 set good
Once the “Firmware State” shows Unconfigured(good), then check the Foreign state. If the foreign state shows – “Foreign State: Foreign”, then we need to clear the foreign config:
/opt/MegaRAID/storcli/storcli64 /c0/fall show
/opt/MegaRAID/storcli/storcli64 /c0/fall delete
Once the Firmware state shows: "Unconfigured(good)" and the Foreign State shows: "None", then you can manually start the rebuild. Start by using the show all disk groups command to obtain the DG, array, and row numbers.
/opt/MegaRAID/storcli/storcli64 /c0/dall show
Example Output 3
TOPOLOGY :
========

----------------------------------------------------------------------------
DG Arr Row EID:Slot DID Type  State BT      Size PDC  PI SED DS3  FSpace TR
----------------------------------------------------------------------------
 0 -   -   -        -   RAID6 Pdgd  N  72.768 TB dsbl N  N   dflt N      N
 0 0   -   -        -   RAID6 Pdgd  N  72.768 TB dsbl N  N   dflt N      N
 0 0   0   134:0    0   DRIVE Onln  N   7.276 TB dsbl N  N   dflt -      N
 0 0   1   134:1    7   DRIVE Msng  N   7.276 TB dsbl N  N   dflt -      N
Example output 3 shows the disk group (DG), array (Arr), row, enclosure ID (EID), drive slot, and drive state for each virtual and physical drive.
In example output 3, the RAID 6 virtual drive is showing as partially degraded (Pdgd). The physical drives listed show slot 0 as online (Onln) and slot 1 shows as missing (Msng).  We can see that the missing drive is in DG 0, array 0, and row 1.
 
Based on example output 3, you would use the following command to replace the missing drive.
/opt/MegaRAID/storcli/storcli64 /c0/e134/s1 insert dg=0 array=0 row=1
Now you can start the rebuild.
/opt/MegaRAID/storcli/storcli64 /c0/e134/s1 start rebuild
To view the rebuild status, the client can use the show rebuild command.
/opt/MegaRAID/storcli/storcli64 /c0/e134/s1 show rebuild

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB24","label":"Security Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"ARM Category":[{"code":"a8m0z000000cwtcAAA","label":"Hardware"}],"ARM Case Number":"TS012007289","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions"}]

Document Information

Modified date:
19 April 2023

UID

ibm16984009