Host booting in maintenance mode

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

darianve

New Member
Mar 21, 2025
2
0
1
I there

I have two identical servers running esxi 7.0-1

That are meant to auto start a vSphere virtual server on boot up.

One server works fine but the other always boots into maintenance mode, this prevents the auto start of the virtual machines including vSphere.



If I access the ESXI html and exit maintenance mode and start them up manually all works fine but on next start up it will be in maintenance mode again.

Is there any way to prevent this maintenance mode on boot issue? I cant seem to find any errors or reason for it be doing this.
 

nabsltd

Well-Known Member
Jan 26, 2022
706
496
63
It could be an issue with your boot media not accepting the writes, but not throwing any errors you can see.

Essentially, ESXi boots up, grabs all the config settings from the bootbank, creates config files from the settings, writes the files, then applies the settings. As you change runtime settings (like maintenance mode), the changes are written to disk, but not to the config on the bootbank. This is done in an "all at once" manner before shutdown. If the write to the bootbank fails, then you don't really see anything, but the changes aren't saved.
 
  • Like
Reactions: darianve

darianve

New Member
Mar 21, 2025
2
0
1
It could be an issue with your boot media not accepting the writes, but not throwing any errors you can see.

Essentially, ESXi boots up, grabs all the config settings from the bootbank, creates config files from the settings, writes the files, then applies the settings. As you change runtime settings (like maintenance mode), the changes are written to disk, but not to the config on the bootbank. This is done in an "all at once" manner before shutdown. If the write to the bootbank fails, then you don't really see anything, but the changes aren't saved.
Thanks, I'm probably going to image the working server and run that on the one with this issue. The servers run on separate systems