VMware Cloud Community
9TechIJCoreFau
Contributor
Contributor

BIOS 1 No Boot Device: No bootable media - Assert

Hello, I'm getting this message on ESXi 6.0.0:

pastedImage_0.png

As you can see the server is a Lenovo ThinkSystem SR650. I installed ESXi on the m.2 dirves of the Think System configured on a RAID 1 array.

The server is up and running and it has virtual machines on it running just fine.

I tried to search the error message on Google but it's hard to find information relevant to my case. If you need more info to help determine the cause please let me know .

Tags (2)
Reply
0 Kudos
7 Replies
diegodco31
Leadership
Leadership

Did server install with image customize of IBM?

Diego Oliveira
LinkedIn: http://www.linkedin.com/in/dcodiego
Reply
0 Kudos
9TechIJCoreFau
Contributor
Contributor

Yes. Specifically with VMware-ESXi-6.0.0.update03-6921384-LNV-20180201.iso

Reply
0 Kudos
WinterfellWen
Contributor
Contributor

Hi 9TechIJCoreFau, I have the same problem on my account's environment's SR650 also, but only have 1 of them has this alert.

Do you have any update? Thanks in advance.

Reply
0 Kudos
WinterfellWen
Contributor
Contributor

Hi Mate,

My problem solved after upgrade Bootable Media Creator Firmware of Lenovo.

Hope your problem solved also.

Reply
0 Kudos
liebedd
Contributor
Contributor

Hi WinterfellWen

I have the same problem on my SR850 also

Which fireware has been upgraded?

Reply
0 Kudos
Amplexor
Contributor
Contributor

Hi guys,

I have the same issue as you on SR650 host

Have 4 of them all running the same FW versions on all devices and all of them have M.2 mirror KIT installed.

3 of them run with all health status green OK and one has that BIOS1 No Boot device  issue

What was your solution for that as i have all FW version running on the same revision. was there a specific solution to your problem?

Thx for the reply

Reply
0 Kudos
Amplexor
Contributor
Contributor

Hi,

Just an update to give the solution to others if they have a similar issue.

As stupid as it sounds the issue was fixed with unplugging the server from the power. Letting it discharge for 60 sec and plugging it back in. This is the result of firmware upgrades that are still in the cache and need to have a clean reset and discharge of memory.

That cleared my issue and now health is running all OK

Reply
0 Kudos