Increasing your AWS EC2 root partition (Windows)
15
Jan
2010
As we now have instances which can be booted from EBS (hurray for that), you’re root is also increased to 30gb. But sometimes this still isn’t enough. Here is how you can increase your root partition drive using the AWS Console.
- login to your AWS Console
- Go to [Instances], right click your instance and select [create image (EBS AMI)]
This will make a backup (just in case)
- Your instance will reboot, and come up again when the image is created. After that stop your instance (do not terminate it
)
- Next is to go to [Volumes], you will see a 30Gib volume somewhere which is attached as /dev/sda1 to your instance
Right click it and select [Create Snapshot from this volume].
- Next, go to [Snapshots]. Right click the snapshot that you created in the previous step and select [Create Volume from Snapshot], you can then specify how big this volume has to become (for example 50 Gib).
- After the volume is created go back to volumes again. You will see a volume which is as large as you specified in the previous step. The status of this volume is “available”.
Now select the volume which is currently attached to your instance. It is the one you located in step 4. Right click it and and select [Detach Volume], it will then become available.
- Now select your newly created volume, right click it and select [Attach Volume]. Select your instance (which will have a status of “stopped”). In the textbox “Device” type: /dev/sda1. Now click [Attach]
- Fire up your instance and log in.
- Open up computer management and select [Disk Management] (underneath the option [storage]). You will see that your root partition has some more space behind it.
- Right click your root partition and select [Extend Volume], walk through the wizard. Eventually your root partition will be extended.
1 Response to Increasing your AWS EC2 root partition (Windows)
Ben de Ridder
July 5th, 2010 at 08:53
Marc,
Thanks a lot. For some reason it was hard to find a usefull piece about this, while a lot of Windows (Sharepoint) administrators must have been facing it.
Grtz,
Ben