Troubleshooting an ESX host that does not boot (10065)
- When an ESX host boots and gets to the login screen, you see a line of errors similar to:
Error: Signature mismatch between VmkCtl ( DateTime) and VMKernel ( _Unknown_)
Can't access TTY: Job control turned off
- The line or error changes every time it reboots. It also displays the error:
Util : 815 : Status 0xbad0001 trying to get a valid VMKernel MAC address. Various vmkernel subsystems will provide lower quality of service
- If you restart the ESX host, you see the error:
Grub error 15: File not found
This issue occurs if the esx.conf file in the initial ramdisk (INITRD) is corrupted or contains invalid configuration. Use the esxcfg-boot command-line utility on the ESX host to create a new initial ramdisk based on the configuration file at /etc/vmware/esx.conf.
To create a new intial ramdisk:
- Select the Troubleshooting or Service Console Only boot option when the GRUB bootloader appears.
- Log into the terminal as root.
- Run these commands:
- ESX 3.x:
- ESX 4.x:
- ESX 3.x:
- Reboot the ESX host using the reboot command.
- Previous ESX 3.0 configuration files can be recovered from /var/log/oldconf. Other ESX hosts with identical configurations can be inspected to compare settings.