File system corrupted on the OpenVZ container.

It happens rarely but when it does, it is hard to handle. The OpenVZ VM's are usually stable in nature, but I've encountered situations where OpenVZ VM was showing file system error and was refusing to start.

You can follow the below steps to recover the VM.


1. ~# vzctl stop ctid

2. # ploop mount /vz/private/ctid/root.hdd/DiskDescriptor.xml

3. now do a df -h and you will get the ploop id for the VM.

4. fdisk -l /dev/ploop12345

5. e2fsck /dev/ploop12345p1

6. ploop umount -d /dev/ploop12345

7. vzctl start ctid

Comments

Popular posts from this blog

Cheat sheet for Hardware RAID health check - Megaraid, Adaptec, 3wareraid and HPraid.

Add a specific tag to EC2 instances?

List volumes without a tag