Alternatively, if you want to keep the RAID drive, refer to
Virtual Disk Not visible to Operating System
Virtual disk not visible to operating system
Issue:
In RAID mode a virtual disk is not appearing for use by an operating system.
Probable Cause:
Virtual disks will not be presented to the system if they are not native to the controller.
Corrective Action:
Import the virtual disk via HII as specified in section
.
Drive replacement
Issue:
An installed drive is not listed in the BOSS-S1 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.
Controller replacement
Issue:
Controller's UEFI configuration utility menu entry not appearing.
Probable Cause:
This is either a firmware or a hardware fault.
Corrective Action:
•
Flash the latest firmware on the BOSS adapter.
•
If the problem persists, shutdown the server and unplug the BOSS-S1 adapter.
•
Plug the BOSS-S1 adapter into the PCIe slot.
•
Boot the system and check the UEFI configuration utility menu again.
If the issue persists, see
NOTE:
Ensure that the system is completely disconnected from all power sources before making any hardware changes.
Controller failure
Issue:
BOSS-S1 device is not presented to system.
Probable Cause:
Hardware fault on the card.
Corrective Action:
Replace the BOSS-S1 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-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.
30
Troubleshooting
