SAS3008 IR RAID in UEFI: RAID0/1/1E/10, Global Spares and Rebuild Status
These archived examples use a server BIOS UEFI configuration interface. The original screenshots are already in English and remain unchanged. Confirm the actual controller, drive mapping, firmware, boot mode and supported OS driver. Changing boot/storage modes or entering setup through a restart can interrupt an installed system.
Creation and deletion can destroy existing data; identify the intended available drives and protect required data first. The article contains separate examples, rather than one uninterrupted sequence in which all arrays coexist. A controller’s successful-operation or Normal/Optimal state alone does not verify completed initialization, filesystem access, OS boot or backups.
The source uses LSI SAS3 MPT Controller Version 18.00.00.00 on SAS3008. This is an IR-firmware workflow; the presence of a SAS3008 chip alone does not mean an IT-mode HBA exposes the same RAID menus. The shown disk IDs use the controller’s own enclosure/slot mapping.
1. Set the appropriate UEFI policies
Under Advanced → CSM Configuration, the source keeps CSM Support Enabled, sets Boot Mode to UEFI Mode, and sets Network, Storage, Video OPROM Policy and Other PCI devices to UEFI. Confirm these are appropriate for the actual installation:
2. View a virtual disk
Under Advanced, select LSI SAS3 MPT Controller SAS3008, then LSI SAS3 MPT Controller Version 18.00.00.00. Open Virtual Disk Management → Manage Virtual Disk Properties and select the intended VD:
The property example lists Volume 605, RAID0, 14903 GB, Optimal and Write-Cache Enabled. Other sections reuse volume IDs with different levels, so identify the real configuration rather than assuming every Volume 605 picture is the same array.
3. Delete a virtual disk
Open the controller and Virtual Disk Management. For deletion the actual menu is Select Virtual Disk Operations, rather than the source prose’s Select Virtual Disk Properties. Choose the intended VD; the dropdown includes volumes 604 and 605:
Choose Delete Virtual Disk. The source’s selected target is Volume 604, with Background Init in progress at 0% shown on the underlying page. The delete warning says the operation causes data loss. Set Confirm to Enabled and choose Yes only when deletion is intended and required data is protected. The last source message reports Operation completed successfully:
4. Create RAID0
Open SAS3008 → LSI SAS3 MPT Controller → Controller Management → Create Configuration:
Select RAID0 and open Select Physical Disks. The firmware’s help text lists RAID0 2–10 disks, RAID1 two disks, RAID1E 3–9 disks and RAID10 4–10 disks. These are this interface’s stated limits, not a guarantee that every tool or firmware reports the same limits. The same help text warns that selected-drive data will be deleted:
Enable only the intended members. This example chooses SATA HDDs 0:2:0 and 0:2:1, each shown as 7452 GB, leaving the other listed drives Disabled. Apply Changes:
Set Confirm to Enabled, review the target and choose Yes. The source shows Operation completed successfully, then a property view with RAID0 Optimal. A separate initialization/OS access test is not shown:
5. Create RAID1
Repeat SAS3008 → LSI SAS3 MPT Controller → Controller Management → Create Configuration, then select RAID1 and Select Physical Disks:
This separate example enables drives 0:2:2 and 0:2:3, each 7452 GB. Leave unrelated disks Disabled and choose Apply Changes. Set Confirm to Enabled and choose Yes only for the intended creation. The final message reports successful completion:
6. Create RAID1E
Use the same controller/Create Configuration path. The open level menu still shows an intermediate RAID10 field, but the next form explicitly shows RAID1E. Select the final intended level and physical disks:
The source enables three SATA HDDs, 0:2:0 through 0:2:2, and leaves the remaining disks Disabled. This is another separate configuration example, not simultaneous reuse of members from the earlier arrays. Apply Changes, set Confirm to Enabled and choose Yes when correct. The source then reports Operation completed successfully:
7. Create RAID10
Open the controller, Controller Management and Create Configuration again. Select RAID10 in the level menu, then Select Physical Disks:
The final selection form shows RAID10 with four members enabled, 0:2:0 through 0:2:3, and the rest Disabled. Apply Changes, enable Confirm and choose Yes only for the intended configuration. The last message reports successful completion:
8. Assign a global hot spare
Open the controller → Virtual Disk Management → Manage Virtual Disk Properties and select the intended VD:
The target dropdown picture shows Volume 605 RAID10, 14903 GB, Optimal. The following Manage Global Hotspare Disks picture switches to Volume 604 RAID1, 7451 GB, Optimal and Write-Cache Disabled. Keep those two views distinct. Open Manage Global Hotspare Disks on the verified configuration:
Choose a compatible available disk and set it Enabled. The source candidate is 0:2:5, SATA HDD-512e, 7452 GB; 0:2:6 and 0:2:7 remain Disabled. Select Assign Global Hotspare Disk. The source reports successful operation. This is a global spare assignment rather than a promise of a dedicated spare for one selected VD:
9. Check a degraded array and rebuilding disk
Open the controller → Virtual Disk Management → Manage Virtual Disk Properties. The first property picture here is Volume 605 RAID0 Optimal; the next switches to the separate Volume 604 RAID1 case and shows Degraded, 7451 GB, Write-Cache Disabled:
Follow the server’s supported replacement process for the verified failed member. To inspect a replacement, open Physical Disk Management → View Physical Disk Properties and select the actual device. The dropdown screenshot initially shows 0:2:0 Ready, while the final detail page is Physical Disk ID 0:2:2, State Rebuilding. Do not assume the intermediate default choice identifies the final rebuild destination:
The final rebuilding disk is a 7452 GB SATA ST8000NM0055-series device. The source says a completed rebuild returns to Optimal, but supplies no later completed-state capture in this branch. Rebuilding is still in progress; verify completion and the resulting redundant-array and data-access state afterward. A failed RAID0 member does not gain recoverability from this RAID1 rebuild example.
Broadcom’s English SAS3IRCU guide is a related command-line reference for SAS3008 Integrated RAID and compatible member/spare constraints. It is not an identical UEFI screenshot guide; where its CLI limits differ, follow the installed controller’s supported firmware documentation and actual interface.