In my case I had a network outage in my lab which resulted in the VCA, NSX Manager, Platform Services Controller, nearly everything to crash or hang. Upon restart of the VCA and PSC I received the some errors associated with /dev/mapper/log_vg-log partition. Asking me to fix the error manually.
The problem was if I follow the instructions to enable the shell so I can run fsck, I simply get an unknown command error.
Here is what I had to do to get moving again.
- Hit Control-D or Reboot the vCSA using the vSphere Client.
- When the GRUB bootloader appears, press the spacebar to disable autoboot.
- Select “p” and enter the root password
- Type “e” to edit the boot commands.
- Scroll to the second line displaying the kernel boot parameters. You see this line:kernel /vmlinuz-3.0.101-0.35-default
- Type e to edit the boot command.
- Append init=/bin/bash to the kernel boot options.
- Press Enter. The GRUB menu re-appears.
- Type b to start the boot process. The system boots to a temporary BASH shell.
- Set the default Shell to BASH by running this command:
chsh -s /bin/bash root
- Reboot the vCSA using the vSphere Client
Ah this looks familiar
This time however we will;
- enter the root password
- at the repair filesystem prompt type the following command
- Control-D to reboot
Its all good again.