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

Post a Comment

Popular posts from this blog

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

-
Hi Folks, In another post " raid type " I've mentioned how to find if the server is running with Software or Hardware RAID. Here, we can go ahead and check the health of the Hardware RAID array in the server. The first thing we need to detect is the controller in which the raid is configured and you can easily get it from the another post that I mentioned earlier. However, I'm providing it here again for your convenience. 1. Login to the server as the root user. 2. Execute the following command. /sbin/lspci -vv | grep -i raid 3. This will show the raid controller running on the server. The different types of controller I've worked with includes a. Megaraid which uses megacli b. Adaptec which uses arcconf . c. 3ware raid which uses tw_cli d. HPraid which uses hpacucli . How to check the Megaraid array health status? The Megaraid is usually installed in the /opt/MegaRAID and you can execute the following command to verify the health of the arr...
Read more

AWS Command line Tasks : Create EC2 instance and EC2 instance with 500GB root volume.

-
To create an EC2 instance from command line. aws ec2 run-instances  --image-id ami-efe09bf8 --count 1 --instance-type m4.4xlarge --key-name mysshkey --security-group-ids sg-126adasd2--subnet-id subnet-148fd971 --block-device-mapping /dev/sda1=:500:false --region us-east-1 --image-id : The AMI ID which we are going to create the instance. --count : The number of instances that we need to create. --instance-type : The type of EC2 instance that we are going to use it. --key-name : The pem that we are going to use to connect to this server. --secrutiy group : The security group this instance is getting used. --subnet-id : The subnet in which we want the ec2 instance. --block device mapping - device:space in gb : to terminate volume [true or false.] To create an EC2 instance with 500GB root volume. aws ec2 run-instances --image-id ami-efe09bf8 --block-device-mappings  '[{"DeviceName":"/dev/sda1","Ebs":{"VolumeSize":500,"DeleteO...
Read more

Add a specific tag to EC2 instances?

-
COUNTER=0 for instance_id in `aws ec2 describe-instances --query "Reservations[*].Instances[*].{Instance:InstanceId}"  --filters "Name=tag:Name,Values=*<Common_name>*"  --output text --region <region_name>` do let COUNTER++ printf $COUNTER; echo ". Setting up tag for the instance "$instance_id; aws ec2 create-tags --resources $instance_id --region <region_name>   --tags "Key"="<key_that_needs_to_be_added>","Value"="<value_that_needs_to_be_added>" ; done;
Read more