Physical Server - No Boot Device Available

 

CMOS Battery Failed

Issue: CMOS Battery has failed. The iDrac event logs may indicate the battery has failed and the system time will be an erroneous date. Symptoms of this could be a boot failure, "No Boot Device Available". When the battery dies the BIOS is unable to retain custom settings and may default to UEFI mode depending on the model and build.

Resolution: You can temporarily modify the settings to boot with Legacy mode until a new battery is acquired, but the settings will only save until the next reboot.

 To modify, press F2 to launch BIOS on boot up

• BIOS: Under System Bios Settings -> Boot Settings change from UEFI to BIOS

You will most likely need to modify the system time once Windows loads as well.

Lithium batteries can be shipped domestically, including Alaska and Hawaii. If this is an international shipment, the customer will need to acquire one locally. Lithium batteries are considered a hazardous material due to fire risk.

RAID Missing

Issue: Raid missing. This is typically only found on the R340 that has a PERC H330 RAID card.

Resolution: Confirm the RAID configuration. 

1. To confirm, go into the RAID utility (Ctrl+R) at boot and look at the resulting screens:
   • 
2. In this case, the RAID card appears to have "forgotten" its RAID configuration as stored on the RAID controller card.  However, the RAID configuration is still present. Note the screen called "Foreign View" shown in the above screen shot.  The RAID controller recognizes that disks that had previously been used in a RAID are attached and are displayed there. Navigate to the Foreign View screen by using Ctrl+N.
3. Once at that screen, navigate to the top of the virtual device tree shown there:
   • 
4. In this case, you should select the line, "Disk Group 0" or perhaps the line above.
5. Press F2 on the keyboard and a menu will appear with two options: Clear or Import
6. Select Import
   • This should re-import the RAID configuration information back into the RAID controller's memory.
7. Return to the VD Mgmt screen
   • The two virtual drives (250 GB + 5.2 TB) should now appear there
8. If necessary, the RAID will go into a rebuild process automatically.  Allow the rebuild process to complete, though this may take hours.
9. After the RAID rebuild is complete, reboot the unit.
10. The unit should now boot normally and work as it did before.