Monday, October 5, 2015

FIX: Multiple volumes on AWS EC2 root partition

So, I'm dealing with some AWS EC2 instances that were imported by a tool used by contracted third party.

Some of those imports had a typo that put the boot and data partitions on the same root volume, which is definitely not within best practices. A large part of my issue was in not having messed with much partition management prior to this.

The solution (in rough form) is to:

1) add a disk the same size or larger as your current C partition
2a) mirror your System Volume (if you have one) to the new disk via diskpart
2b) mirror your C: to it (yes you can add both partitions to the same mirror)
3) add a disk the same size as your data volume
4) mirror your data volume to it
5) wait for all mirrors to finish syncing
6) in msconfig, point to the new C volume as your default boot volume
7) shut down
8) detach all drives
9) attach the new C as /dev/sda1
10) break the mirror
11) attach the new data volume
12) break the mirror

Let's maybe try this again (?)

So, it has been a while since I have posted here. There have been some life changes between then and now.

Notsomuch doing the VMware these days. More Windows, PowerShell, AWS and maybe some Ansible or Puppet on the horizon.