PM8204/PM8254 RAID on M6 BMC: JBOD, RAID Creation and Deletion
This archived M6 BMC procedure uses separate examples for viewing storage, configuring JBOD, creating RAID0/RAID1/RAID5 and deleting a logical disk. Match the real controller, firmware, disk identities and retained data before applying a configuration. The RAID examples reuse some disks and logical-disk numbers; they are not a sequence to apply cumulatively to an existing array.
The English illustrations reproduce the original screenshot states. An arrow pointing to a menu option does not mean that option has already been selected. A recorded OK/Optimal state does not establish that initialization, consistency checks, OS access or backup verification have completed. The official BMC manual also notes that storage information is invalid while the server is powered off or starting, and disk identification can be delayed during rebuilding.
1. View the RAID controller and physical drives
Log in to BMC and open Storage → View. Select OCP_RAID to inspect the controller. This source example identifies MT0808M6R (0), firmware 03.01.02.042 and Mixed mode; it is not a universal firmware requirement for every PM8204/PM8254 installation:
Select the intended Disk_* node to view its hardware and assignment details. The example Disk_2i:1:5 is a SEAGATE ST4000NM0025 SAS drive, 3726GB, 512-byte blocks, 12.0GBS link and7200RPM, shown as Unassigned, ready for assignment:
2. RAID configuration
2.1 JBOD/passthrough
Under View, select OCP_RAID and check Mode. The source describes unconfigured drives in this controller’s Mixed mode as passthrough drives that the OS can recognize without a RAID array. Verify actual OS presentation and firmware behavior:
Under Configure → Physical Disk, this controller’s pictured BMC interface exposes location actions only. It does not show the firmware-status/JBOD selection used by the LSI example. The screenshot has neither Start Locate nor Stop Locate selected, a blank duration field and the indicated 1–255 second range:
2.2 Create the RAID0 example
Open Configure → Logical Disk. Choose RAID0 and fill in Disk Name: its red asterisk marks a required field, and the source says an empty name prevents saving. The first image shows the Accelerator menu open with No Acceleration still selected; the arrow points to Controller Cache:
The next example uses 64K stripes, name IEIT, Controller Cache and only Disk_2i:1:5 selected, then Save. The source recommends controller cache for performance, but this is not a measured guarantee or proof of protected write caching. Its overview reports Backup Battery Unit Status No present; verify cache protection and the supported policy before relying on write-back behavior:
Return to View → Logical Disk0 and inspect the result. The pictured logical disk has RAID0, one member Disk_2i:1:5, size 3725GB, 64K stripes, name IEIT and Progress/MsccState OK:
2.3 Create the RAID1 example
RAID1 requires at least two members in this procedure. Select RAID1, enter the required name and select only the intended free drives. The source form shows name inspur, 64K, Controller Cache and Disk_2i:1:6 plus Disk_2i:1:7 checked; Disk_2i:1:8 remains unchecked. Save only after verifying the configuration:
In View → Logical Disk1, this separate example shows RAID1, 3725GB, two elements, 64K, name inspur and OK, with drives 6and7 as members:
2.4 Create the RAID5 example
RAID5 requires at least three members in this procedure. This separate form selects RAID5, 64K, name IEIT, Controller Cache and Disk_2i:1:6, Disk_2i:1:7, Disk_2i:1:8. These overlap the RAID1 example; this is not an in-place RAID1-to-RAID5 conversion instruction:
Its View → Logical Disk1 capture shows RAID5, 7451GB, three elements, 64K, name IEIT and OK:
3. Delete the verified logical disk
The source’s deletion screenshots return to the RAID1 case: Logical Disk1 is RAID1, 3725GB, name inspur, with drives 6and7. They do not show deletion of the three-member RAID5 volume above:
Open Configure → Logical Disk, select the intended volume under Other Actions, choose Delete Logical Disk and use that panel’s Save only when the data may be discarded and the real target has been verified. The pictured dropdown selects Logical Disk1 and the Delete Logical Disk radio is checked. The creation form on the left is unrelated to this deletion action:
In the following View capture, Disk_2i:1:6 and Disk_2i:1:7 are outside a logical disk and boxed as unassigned. Logical Disk0 still contains Disk_2i:1:5, and Disk_2i:1:8 is also outside an array. This is not evidence that the RAID5 case or all three of its members were deleted:
