- Notes, cautions, and warnings
- Overview
- Supported operating systems
- Supported PowerEdge systems
- BOSS-S1 card specifications
- Supported M.2 drives
- Management applications for the BOSS-S1 controller
- Update the BOSS-S1 controller
- Update the BOSS-S1 firmware
- Firmware update using an operating system-specific DUP
- Firmware update using UEFI Shell
- Firmware update using BOSS-S1 CLI
- Firmware update using iDRAC
- Firmware update using Lifecycle Controller
- Related documentation
- Features
- Deploying the BOSS-S1 card
- Driver installation
- UEFI or HII RAID configuration utility
- BOSS-S1 CLI commands
- Troubleshooting
- Importing BOSS ESXi CLI offline bundle may fail in VSphere Lifecycle manager
- BOSS ESXi CLI package fails when upgrading from Dell customized versions of 6.7.x to version 7.0
- M.2 drive firmware update from iDRAC fails on unconfigured drives with an existing adapter key on the BOSS-S1 controller
- Unconfigured drives in BOSS-S1 controller is unavailable for OS installation with an existing adapter key
- ROM version for BOSS reported as firmware version in iDRAC interface
- Firmware update of M.2 drive on BOSS-S1 controller fails
- BOSS-S1 CLI displays No Adapter Found error in Linux
- LC log displays fan unavailability error
- Updating BOSS-S1 controller firmware using iDRAC or LC fails
- Physical disk size not updated in iDRAC
- Physical disk/Virtual disk missing in iDRAC
- Back Ground Activity task progress in HII does not report real-time status
- Virtual disk state will be generated twice
- Character limitation while naming a virtual disk
- VMFS datastore is disabled on the 14th generation of PowerEdge systems that are shipped with VMware ESXi installed on BOSS-S1
- Physical disk not visible to operating system
- Virtual disk not visible to operating system
- Drive replacement
- Controller replacement
- Controller failure
- Unable to boot to M.2 drive installed in slot 1
- CLI reports unsupported features
- Failure to install ESXi on RAID 1
- System not responding
- Management port not responding
- Getting help
Dell Boot Optimized Storage Solution-S1 User's Guide
Unable to boot to M.2 drive installed in slot 1
- Issue:
- When two unconfigured bootable M.2 drives are inserted into the BOSS-S1 device, only the slot 0 drive may be used as a boot drive.
- Probable Cause:
- Working as designed, BIOS only allows booting from the first listed boot device, in this case, slot 0 per peripheral controller. This only occurs in legacy BIOS boot mode.
- Corrective Action:
- Remove the drive from slot 1 and install it in slot 0.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\