I removed my dad’s Linux installation; it was more than two years old and he wasn’t using it, so it just took up half his hard drive as that’s how we had partitioned it. Getting rid of GRUB was the first step, so I booted into the XP recovery console from the installation disc. I was prompted for an Administrator password, but it turned out to be blank, so I just hit enter. Woo, security. I didn’t run
bootcfg /rescan or
fixmbr alone was enough to do it. It successfully booted with the Windows bootloader upon restarting, so I used the XP partition manager to remove the Linux partitions. I couldn’t seem to remove the extended partition, nor resize the volume, which made sense because the extended partition was there. I booted up into System Rescue CD, fdisk’d away the extended partition, then fell back to GParted to expand the single remaining partiton and its filesystem to fill the drive. Presto: double the free space available to Windows!
I also decided to try to dual-boot Debian Squeeze and Debian Wheezy on my netbook. This is because in Physics 260 we use
python-visual in our computer homework, and the version in Squeeze has a problem that results in simple renderings containing, for instance, nothing but a sphere and a box taking seconds per frame. The error message
i915_program_error: Exceeded max instructions is also emitted. I used the Debian installer’s guided full-disk encryption to set up this machine, so I have an
ext2 partition mounted as
/boot, then logical volumes for
/, and swap within an encrypted LVM. I wasn’t sure if two installations of Debian sharing a
/boot partition was a good idea, but I assumed it wasn’t and so halved the existing one and added another
ext2 partition for the new installation. I wonder if
ext3 is a more dependable choice. Then I had to make another logical volume in the encrypted volume group for use as
/ for the Debian Wheezy installation. After poking around online to get an idea of what to do, I booted into a LiveUSB, started with
cryptsetup luksOpen to open the encrypted container. Then
vgscan to find volume groups, and
vgchange -a y to make the logical volumes available. LVM is an alternative to partitions, so I then shrank my
resize2fs, then shrank the logical volume around it with
lvreduce. It was a little scary when
lvreduce appeared to treat units differently, but it seems to have been fine. If my understanding is correct,
resize2fs reports size in
4kiB blocks (which it prints as
lvreduce speaks of base 10 units, yet seems to mean base 2.
lvcreate was the easy part.
Amazingly, my system still booted after all this, so I installed Debian Wheezy. It took some fiddling to get
partman to recognize the contents of my logical volumes. I had to trigger loading
cryptsetup by going into the encryption setup, (IIRC pressing finish, same for LVM) then used
vgchange as before, then going out of and back into
partman. The bootloader failed to install, but I continued without it and ran
update-grub once back in Squeeze and although it detected Wheezy in the LVM, the entry it generated wouldn’t boot because it fails to prompt for the crypt container’s passphrase. I’m not sure why; that’s about as far as I’ve gotten. I tried without a separate boot partition and as would be expected it couldn’t even find the kernel. There are wishlist bugs filed in Debian about the installer’s support for encrypted LVM: #498199, #529343, and #566497 to name a few. I hope I can figure this out, but I don’t feel comfortable spending a great deal of time on it. I may just install to my flash drive.
Edit Jan 11, 2012:
I got it working! It wasn’t prompting for the passphrase because it was missing
/etc/crypttab. Once I added that and
chrooted in from the installer’s rescue mode to generate a new
update-initramfs -u, it worked! Hooray!