VMware Cloud Community
my514k
Contributor
Contributor
Jump to solution

Cannot boot -> ESXi 6.5 NOT_IMPLEMENTED bora/vmkernel/core/bootModule.c:492

Hi all, can you help me?

After reinstall ESXI it works correctly, no problems....but after few days (1, sometimes 2) it is not possible to start. After user loaded successfully, it crash and display only PSOD. Screenshot in attachment. I have tried also install all available patches, check all disks / partitions....everything worked without problem, disk space availabe.....but after few days, the PSOD is back.

I have no idea how to fix it, I have tried to reinstall it at least 10 times.....but after few days / few reboots with the machine it is back and it is not possible to start it correctly.

Please help anybody.

Reply
0 Kudos
1 Solution

Accepted Solutions
hetz
Enthusiast
Enthusiast
Jump to solution

A simple solution: Upgrade to ESXI 6.5 Update 1 (U1)

View solution in original post

Reply
0 Kudos
10 Replies
dekoshal
Hot Shot
Hot Shot
Jump to solution

Looks like the issue is either with the esxi media or partition where esxi is getting installed.

ESXi installation fails with a purple diagnostic screen error: NOT_IMPLEMENTED bora/vmkernel/core/bo...

Download a new esxi image and install on a USB drive or SSD and during installation select preserve existing VMFS datastore to keep your VM's safe.

If you found this or any other answer helpful, please consider the use of the Correct or Helpful to award points.

Best Regards,

Deepak Koshal

CNE|CLA|CWMA|VCP4|VCP5|CCAH

Reply
0 Kudos
vijayrana968
Virtuoso
Virtuoso
Jump to solution

What is the hardware you are using ? Did you use vendor customized image for installation?

Most of the time this error is related to media used for installation, also check the VMware hardware compatibility matrix for system in use.

Reply
0 Kudos
my514k
Contributor
Contributor
Jump to solution

I know, it is not supported CPU...but after many tips on internet, where was written it works with disabled AMD SMT, I have tried it. The installation is always successful, but after few reboots it stop working. My PC configuration:

CPU: AMD Ryzen 7 1700

MB: ASUS PRIME B350M-A

RAM: DDR4 16GB (2x8GB) Kingston 2666Mhz CL15 HyperX Fury Black

SSD: Samsung 960 Evo M.2 512GB

No special customized image, standart installation downloaded from vmware site.

Reply
0 Kudos
vijayrana968
Virtuoso
Virtuoso
Jump to solution

Yes, this can be done via teaks as you disabled SMT. At first attempt, you should change the ISO image you used, download fresh ISO and retry.

Reply
0 Kudos
hetz
Enthusiast
Enthusiast
Jump to solution

A simple solution: Upgrade to ESXI 6.5 Update 1 (U1)

Reply
0 Kudos
dekoshal
Hot Shot
Hot Shot
Jump to solution

have you tried your suggested solution. Is th solution document anywhere?

Best Regards,

Deepak Koshal

Reply
0 Kudos
my514k
Contributor
Contributor
Jump to solution

Until now nothing worked. Tried fresh inatall with new installation media, it looks working and after 4 days again back and every boot finished with PSOD.

Tomorrow I try to reinstall including last update (U1). In one week I can give the feedback if still working or again (after few boots) start to displaying PSOD.

Reply
0 Kudos
my514k
Contributor
Contributor
Jump to solution

Upgrade to U1 helped. Not working stable, but working. After 3-5 days after boot it freeze, but after reset it is able to boot without bootModule error.

Reply
0 Kudos
Maryanno
Contributor
Contributor
Jump to solution

Hi my514k,

I can't help you for your problem but, maybe you can help me.

I have the same motherboard ASUS PRIME B350M-A but and when i tried to install esxi6.5 he can't see my HDD.

It's not M2 HDD but there are one SSD and one mechanical HDD, the both are on sata port.

Did you had this problem ?

Thank you,

Maryan CORNE

Reply
0 Kudos
my514k
Contributor
Contributor
Jump to solution

I had the problem with sata 5 a and sata 6 port. When M2 was connected, sata 5 and sata 6 are not working.

Currently I am not sure if it stopped working after connecting M2, or it is stopped working after enabling M2 in bios. Try different sata ports and check if is correctly recognized by bios. But I am not sure if is is the same situation.

Reply
0 Kudos