9230 SATA M.2 RAID in UEFI: Status, Deletion, RAID 1 Creation and Rebuild
This is an archived Inspur OEM example for a Marvell 9230-based SATA M.2 RAID controller. Match the actual firmware, server boot mode and supported replacement drive; a generic 88SE9230 chip specification does not prove every feature is exposed by this OEM firmware. The source’s screenshots are already in English. Viewing, deleting, creating and rebuilding are separate operations; deleting/recreating a working array is not a routine repair for a failed mirror member.
1. RAID configuration
1.1 View the existing array
The source enters Advanced → CSM Configuration:
Its example shows Boot Mode UEFI Mode with UEFI Network/Storage/Video/Other PCI option-ROM policies. CSM Support itself remains Enabled in the picture. Match the actual boot layout and vendor procedure rather than treating this as an instruction to switch an existing OS blindly or disable CSM:
Return to Advanced and open Marvell Boot optimized M.2 Raid controller:
Choose Physical/Virtual Disk Information → Virtual Disk Info → the intended virtual disk. The source illustrates New_VD:
Inspect its actual mode, members, capacity and status. This capture shows VD0, Functional, RAID 1, 447GB, 64K stripe, members 0/1 and BGA Not running:
1.2 Delete the verified array only when its data may be discarded
Select Delete RAID Configuration, then select the intended virtual disk. Change its selection from Disabled to Enabled:
The next page warns that deleting the VD deletes its data. Change the confirmation from No to Yes only after verifying the real target and backup. The source first shows No, then the Yes choice in an open selector:
Review the final data-loss warning and choose Next when the destructive operation is authorized. The source success page instructs a reboot for the settings to take effect; it is a settings result, not a successful OS boot test:
1.3 Create the source RAID 1 example
Choose Create RAID Configuration. Enable the two verified target drives and select Next. The source lists two INTEL SSDSCKKB480GZ drives:
Review all settings rather than accepting defaults without checking them. The pictured values are RAID 1, 64K, 447GB, Quick Initialization Yes and a blank Name field, with creation confirmation initially No. Change the confirmation to Yes only for the intended new array:
Choose Next and review the warning that applying the configuration deletes all data on the physical disks used. Protect required data first. The following Successful page again requires a reboot; acknowledge OK and perform the planned reboot/verification through the service procedure:
1.4 Passthrough/JBOD
The source states that unconfigured drives default to passthrough when not used for RAID1. No separate JBOD conversion or data-preservation procedure is included. Verify actual controller/OS presentation; passthrough is not an excuse to erase an existing required mirror.
2. A single member goes offline
For its single-member RAID 1 failure case, the source says the array becomes Degraded while the surviving member provides I/O and a supported replacement triggers rebuilding. This depends on surviving data and compatible replacement; confirm the M.2 assembly’s service and power requirements rather than assuming hot swap.
The final screenshot is a separate 223GB example, not the 447GB volume pictured above. It shows Rebuilding and BGA Running[6%]. Continue monitoring the actual rebuild and final status through the supported procedure; 6% is not completion:
No controller configuration, deletion, installation or replacement was performed during this translation. Verify the real volume, completed rebuild, OS boot and required data access before returning a system to service.