VMware vCenter Server Appliance 6.5 – failed to boot – Failed to start Network Service


If you ever encounter an issue with the vCenter server that’s so bad that the server itself doesn’t start, well try the following:

fsck -fy /dev/mapper/log_vg-log

If it tells you that it fixed something, just press CTRL+D and let the damn thing boot.

My LAB environment’s “reliable” storage system is a Synology NAS (XPEnology actually) and I present iSCSI LUNs out of it for all my devices, including the 2x SUPER-AWESOME Supermicro SYS-5028D-TN4T that I’ve aquired in June 2016.

So, from time to time (to be read as less as possible) I reboot the NAS due to different reasons but nothing really bad happened until now as I do my homework and shutdown anything that might use that shared storage system. This time, I forgot to shutdown the vCenter server, which you guessed… was using one of the iSCSI LUNs as its underlying storage and one of the partitions got corrupted and the vCenter Server crashed and failed to boot.

Hope this helps you. I wondered a bit until figured out what’s wrong 🙂



Victor an End User Computing Consultant. You find him most of the time on Twitter (@01004753) but also on LinkedIn evangelizing new technologies and processes that can change in good, the world we live in. Victor has expertise in Server & Client Virtualization, Client Management, GPU Virtualization, HyperConvergence and Enterprise Security

Tagged with:
Posted in error, fixes, HowTo, Uncategorized, vCenter, VMware
17 comments on “VMware vCenter Server Appliance 6.5 – failed to boot – Failed to start Network Service
  1. Jack White says:

    I created the same issue when I rebooted my QNAP NAS with iSCSI LUNs. Your fix did the trick, Many thanks.

  2. forbsy says:

    Thanks! This was a lifesaver. How did you find the solution? I couldn’t find a kb on this.

  3. Rodrigo says:

    Hi, I get stuck after running that command.

    e2fsck:Cannont continue , aborting

  4. Michael says:

    You just saved my day, thanks!

  5. Steve says:

    Thanks Victor! You saved my bacon.

  6. Quinton Coelho says:

    Thanks! It worked for me! Disco Dancing!

  7. Hazard says:

    Worked for me! Had a network outage today and it seemed to corrupt my vCenter

  8. Daylate says:

    Add my name to the ever-growing list of folks who were helped by this. Thank you!!

  9. Aaron Artino says:

    Nearly and instant fix to a major problem. thank you so much!

  10. Edward says:

    This has worked for me in the past, but this time for an unknown I found my i could not login to my vcenter. I fixed sda3 and rebooted then the network service will not start. I run the command but after a reboot I get the same error. Am on 6.7 now, can anyone help please?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Follow Victor Homocea on WordPress.com
My Gravatar


Storage, Virtualization, Container Orchestration

Marius Sandbu



cu camera pe bord

Ingmar Verheij

About Citrix, Remote Desktop, Performance, Workspace, Monitoring and more...

Carl Stalhood

Filling gaps in EUC vendor documentation


Virtualization trend to the max

Victor Homocea


Ray Heffer

Enterprise Technologies

Elvis Apostol

Calatorind prin lumi indepartate, pictez in cuvinte, lacrimi de culori.

%d bloggers like this: