VMware NSX: Recover NSX Manager from Read-only file system – UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

VMware NSX: Recover NSX Manager from Read-only file system – UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

I ran out of this issue after fixing an issue in the storage system. It took sometime to resolve the Storage issue and I started my Virtual Machines, NSX Manager and Controllers. I was waiting to check the NSX Components in my vCenter and it was not there. My NSX Manager VM was up and running and I opened a console and checked the NSX Manager status. I was able to see this in my screen.



(i.e. . without -a or -p options)


File system errors were encountered that could not be fixed automatically. This system cannot continue to boot and therefore be halted until the errors are fixed manually by a System Administrator.

After you press Enter, this system will be halted and powered off.

I hit Enter and my NSX Manager powered off. I tried the same thing again and got the same result. I wanted to start fixing this issue as I was not able to check the NSX components. I was talking to a friend who has more knowledge in Linux and checked a solution for this. Generic fsck commands didn’t accept and started the troubleshooting further. 

Run FSCK using Ubuntu Live Desktop CD

I have downloaded the Ubuntu Desktop , uploaded to the Datastore and mount as an .ISO file.

Set the VM to enter to the BIOS at the next boot

I set the CD-ROM Drive as the first boot device, save and exit from the BIOS. I let the NSX Manager to boot from the Ubuntu CD

NSX Manager started to boot and I was able to see the Ubuntu Screen

I selected try Ubuntu at the next screen

So NSX Manager loaded to the Ubuntu desktop

I opened a Terminal and listed the partitions using ls -l /dev/sd* command, tried to execute the file system check using fsck /dev/sda2 (sda2 was in the initial error screen go top and see my error message). You need to have the root permission to execute the file system check and used sudo fsck /dev/sda2 command. It started to check the file system and entered y each and every time it asked while checking the file system

I was able to see the file system modified message and I executed the sudo fsck /dev/sda2 again and it said my file system is clean after this.

All done. I shut down the VM and ejected the .ISO file from the CD-ROM, hit ENTER to complete the shutdown process

Once the VM powered down I started the VM. My NSX Manager was back in action after the manual file system check

Click to rate this post!
[Total: 7 Average: 5]

4 responses

  1. Salvatore Avatar

    Thank you.. very interesting!

  2. Sundar Avatar

    Its helped us to fix, wondering why VMware has no solution or I missed it… Thank you for this great article

  3. Frantisek Ferencik Avatar

    Aruna hi, nice post. I have experienced this also. Have you succeeded to manage then via Networking & Security Section in vCenter? In my case 30 minutes after successful fix and reboot of NSX Manager and still no NSX Manager accessible via vCenter.

    1. Aruna Lakmal Avatar

      Honestly, I haven’t experience something like that. What about the services?are they all running? What about restarting the vCenter service if possible? Please share how you fix this, just to share the knowledge with the readers. Thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *