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 🙂
I created the same issue when I rebooted my QNAP NAS with iSCSI LUNs. Your fix did the trick, Many thanks.
You’re welcome Jack. Unfortunately I stumbled a while until I got this, and thought it might be a bit faster for the others.
Thanks! This was a lifesaver. How did you find the solution? I couldn’t find a kb on this.
I really don’t remember right now. It might be this one, but I don’t think back then I actually have found a KB but the command and improvised.
Well, in any case thank goodness for Google LOL.
Hi, I get stuck after running that command.
e2fsck:Cannont continue , aborting
Rodrigo, what if you boot in recovery mode?
How do i do that ?
Hi Victor, I have the same issue. How can we boot in recovery mode the vCenter?
You just saved my day, thanks!
Glad I can give back some days back to the community 🙂
Thanks Victor! You saved my bacon.
Thanks! It worked for me! Disco Dancing!
Worked for me! Had a network outage today and it seemed to corrupt my vCenter
Add my name to the ever-growing list of folks who were helped by this. Thank you!!
Nearly and instant fix to a major problem. thank you so much!
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?