Owners Manual

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 using Hardware-Independent Imaging (HII).
Drive failure
Issue: An installed drive is not listed in the BOSS conguration utility.
OpenManage reports Physical Disk oine state.
Probable cause: Drive is either in failure state or has corrupted rmware.
Corrective action: Reseat drive to ensure drive is inserted correctly. If error persists, attempt to update drive rmware using DUP. If
error is still present, replace erroneous drive.
Fault in controller
Issue:
Controller's UEFI Conguration Utility Menu entry is not appearing.
Probable cause: Either a rmware or a hardware fault
Corrective action:
1 Flash the latest rmware on the BOSS adapter.
2 If the problem persists, shutdown the system, and then unplug the BOSS adapter.
3 Plug the BOSS adapter into the PCIe slot.
4 Boot the system and check the UEFI Conguration Utility Menu again.
If the problem still persists, see BOSS card is not detected.
NOTE: Ensure that the system is completely disconnected from all power sources before making any hardware changes.
NOTE: If you replace the SAS HBA330 controller you must update to the latest HBA rmware version.
BOSS card is not detected
Issue:
BOSS device is not detected in the system.
Probable cause: Hardware fault on the card.
Corrective action: Replace the BOSS adapter with a new one.
Unable to boot to M.2 drive installed in slot 1
Issue:
When two uncongured bootable M.2 drives are inserted into the BOSS device, only the slot 0 drive boots.
BOSS card 137