Resize Drive Problem in Centos6 on AWS EC2

To Resize the root partition in Centos 6 machine run the below mentioned Commands:

 

1. Install EPEL6 Repo
~]# wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
    or 
~]# wget  http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
~]# rpm -ivh epel-release-6-8.noarch.rpm

2. Install the dracut & cloud-utils growpart modules-growroot
~]# yum install -y dracut-modules-growroot cloud-utils-growpart
  or 
~]# yum -y --quiet install dracut-modules-growroot


~]# dracut -v --force --add growroot /boot/initramfs-$(uname -r).img


~]# reboot

3. The initrd needs to be rebuilt after installing the dracut-modules-growroot.
Create a backup copy of the current initramfs:
~]# cp -p /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

4. Create the initramfs for the current kernel:
~]# dracut -f

5. Result after reboot
~]# reboot


Comments

Post a Comment

Popular posts from this blog

Default ssh Usernames For Connecting To EC2 Instances

Image
Each AMI publisher on EC2 decides what user (or users) should have ssh access enabled by default and what ssh credentials should allow you to gain access as that user. For the second part, most AMIs allow you to ssh in to the system with the ssh keypair you specified at launch time. This is so common, users often assume that it is built in to EC2 even though it must be enabled by each AMI provider. Unfortunately, there is no standard ssh username that is used to access EC2 instances across operating systems, distros, and AMI providers. Here are some of the ssh usernames that I am aware of at this time: OS/Distro Official AMI ssh Username Legacy / Community / Other AMI ssh Usernames Amazon Linux ec2-user Ubuntu ubuntu root Debian admin root RHEL 6.4 and later ec2-user RHEL 6.3 and earlier root Fedora ec2-user root Centos centos root SUSE root BitNami bitnami TurnKey root NanoStack ubuntu FreeBSD ec2-user OmniOS root Even though the above list will get ...
Read more

Deleting a Route 53 Hosted Zone And All DNS Records Using aws-cli

Image
fast, easy, and slightly dangerous recursive deletion of a domain’s DNS Amazon Route 53  currently charges  $0.50/month per hosted zone for your first 25 domains, and $0.10/month for additional hosted zones, even if they are not getting any DNS requests. I recently stopped using Route 53 to serve DNS for 25 domains and wanted to save on the $150/year these were costing. Amazon’s instructions for using the Route 53 Console to  delete Record Sets and a Hosted Zone  make it look simple. I started in the Route 53 Console clicking into a hosted zone, selecting each DNS record set (but not the NS or SOA ones), clicking delete, clicking confirm, going back a level, selecting the next domain, and so on. This got old quickly. Being  lazy , I decided to spend a lot more effort figuring out how to automate this process with the aws-cli, and pass the savings on to you. Steps with aws-cli Let’s start by putting the hosted zone domain name into an environment va...
Read more

JAWS: THE JAVASCRIPT + AWS STACK.

Image
JAWS is a stack from Amazon web services(AWS) to ease the development of massive scalable web applications. It is trying to solve important problems in scalable web application development. 1. No Backend servers : All web and mobile application needs backend server and database server. Since the JAWS back-end is comprised entirely of AWS Lambda Functions, you don't need to write your back end server in Node, Ruby, PHP or python. A back-end comprised of Lambda functions comes with a ton of concurrency and you can easily enable multi-region redundancy. So there is no need for scaling/deploying/maintaing/monitoring servers again. 2. Cheap : Lambda functions run only when they are called, and you only pay for when they are run. You can build your app using following AWS services Lambda  - Build worker tasks that you can spawn and scale infinitely. DynamoDB  - Managed, NOSQL data storage API Gateway  - Launch an API with...
Read more