Arch Linux

Description:

Being fed up with Ubuntu, I wanted to try Arch. I told the Arch installer to set up dm_crypt with ext3 on top, mountpoint "/". When starting the newly installed OS, booting stopped with fsck reporting a bad superblock on the root file system. Then Arch dropped me into a maintenance shell with the root FS mounted read-only.

I found out that mkinitcpio has a hook "encrypt" which mounts the root partition into /dev/mapper/root. The name "root" is hardcoded in the encrypt hook, and that's the problem.

The installer asked me what I want to name the device and I said "/dev/mapper/arch-root". The installer then made an fstab to mount "/dev/mapper/arch-root" with the mountpoint "/" (correct). But the encrypt hook didn't get the memo about the name "arch-root", and made up the name "/dev/mapper/root". So fsck reads fstab, tries to check /dev/mapper/arch-root, sees it isn't there, and freaks out.

I read the encrypt hook script, but I don't understand enough of it to fix the problem. For instance I can't tell where the variable $cryptdevice is supposed to be coming from.

Might be related: when booting, the encrypt hook prints a message telling me that "deprecated syntax" is being used. However the installer set that all up for me. I didn't put no "deprecated syntax" anywhere. It's a little unfortunate that the installer creates conf files which just one reboot later cause major breakage.

Any workaround would be greatly appreciated. Where am I supposed to set the "$cryptdevice" variable?

Additional info:

Package cryptsetup-1.0.7-1 (this is what you get when you install Arch today)
Arch installer

Steps to reproduce:

Install Arch, telling the installer to encrypt the root partition. Name it "/dev/mapper/something". Reboot into newly installed system, which won't boot.