Users Guide

An installed drive is not listed in the BOSS-S2
Configuration Utility
Issue: An installed drive is not listed in the BOSS-S2 configuration utility.
OpenManage reports Physical disk offline state.
Probable Cause: Drive is either in failure state or has corrupted firmware.
Corrective
Action:
Reseat drive to ensure drive is inserted correctly. If error persists, attempt to update drive firmware using
DUP. If error is still present, replace erroneous drive.
The BOSS-S2 card is not presented to the PowerEdge
server
Issue: The BOSS-S2 card is not presented to the PowerEdge server.
Probable Cause: Hardware fault on the card.
Corrective
Action:
Replace the BOSS-S2 adapter.
Unable to boot to M.2 drive installed in slot 1
Issue:
When two unconfigured bootable M.2 drives are inserted into the BOSS-S2 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.
Unsupported commands, options, and features are
displayed by BOSS-S2 CLI with VMware CLI utility
Issue:
Several commands, options, or other features listed by the VMware CLI utility state that they are
unsupported when run.
Probable Cause: CLI shows the same information on all Marvell products, but only implements the functions which are
pertinent to that platform or system.
Corrective
Action:
Use the supported features. See Manage BOSS-S2 using CLI commands on page 33.
Unable to deploy ESXi on RAID 1 of BOSS-S2
Issue:
Attempting to install ESXi on a RAID 1 results in an invalid partition table error.
Probable Cause: If an unconfigured physical disk containing an ESXi partition is used in a virtual disk, any attempts to
install a partition of ESXi on this virtual disk will raise an error due to failure to clear out the previous
partition.
Troubleshooting 39