I recently upgraded one of my CloudAtCost servers from Developer 1 to Developer 3 because I needed more disk space. The upgrade got off to a rocky start. It took a week for the work to actually get done and then I was informed that I needed to extend my partition. I had no idea how to do that, and if CloudAtCost’s tech support did, they weren’t sharing.
As it turns out, this is all pretty easy. This document simply condenses the instructions I found here for my own future reference.
rsync. The following
copies everything out of the hypothetical
git repositories on my server to my local machine.
Login to your server.
You’ll need to know where the new partition lives:
After the next step is complete, there will be a new device in the list (probably at
Also, make note of the file system’s current size:
This will be helpful in verifying that the following steps actually worked.
From the interface provided:
- Select the unallocated space
- Select New
- Select Logical and allocate all the available space (shown by default)
- Select Type and enter 8E
- Select Write, type yes, and hit Enter
- Reboot the server (
Once rebooted and re-logged in, run
and verify that there is, in fact, a new device that wasn’t there before (again, probably mounted at
/dev/sda6). If there isn’t, you’re out of luck, because this is all just magic to me.
Assuming the new device lives at
Make note of the name associated with VG Name. Mine was called
ubuntu1204-vg even though I’m running Ubuntu 14.04.
Make note of the path associated with LV Name used for the root filesystem (mine was
should reveal a file system much bigger than what you say in Step 1.