8.10 alternate installer breaks in multiple ways with raid/luks/lvm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
debian-installer (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
So. I tried to do an install of 8.10 on a mirrored encrypted lvm, with /boot on a separate mirror. With the alternate installer of course, since it's funky stuff.
First thing I noticed was that the partitioning tool forgets that I said to use the /boot mirror as /boot every time I do some luks and lvm setup. No biggie, just a reinstall with me reminding the installer of this at the end. Yay. Success. Or is it?
No. The system doesn't boot but tosses me into the initrd shell prompt. With no query of the LUKS password at all. So it doesn't even seem to try to set up LUKS at all.
'course, after I cryptsetup manually, I do get my md1_crypt. But wait, it isn't the lvm physical volume. Turns out the installer creates a "partition" (!) on the md1_crypt volume called md1_cryptp1 and installs there. I lose interest in finding the correct magic (presumably dmsetup is involved) to set that up even manually. This may be related to Debian bug 494910. Except it was really well hidden in the Ubuntu installer, didn't complain. Just asked to create a partition. I didn't think much of it since it asked that in the previous release as well. It just didn't actually, you know make it, so I figured it's just a silly partman internal thing where it has to think everything has partitions in it.
Sooyeah. In the future, you know, it'd probably cover quite a few installation failure scenarios if you'd just see if a raid/luks/lvm install manages to boot.
Meanwhile, I'll ponder about doing a fresh 8.04 and then upgrading, or switching to Debian unstable...
Changed in debian-installer: | |
status: | Incomplete → Confirmed |
Changed in debian-installer: | |
assignee: | nobody → kamion |
Changed in debian-installer (Ubuntu): | |
assignee: | Colin Watson (cjwatson) → nobody |
By the way, I did the 8.04 route. I seem to have forgotten that it didn't setup the dm_crypt root properly either, basically forgoing the creation of /etc/crypttab. Manually creating that and running mkinitrd again fixes the bootup from the encrypted root. That part of the problem is probably the same still.
What I did recall correctly is that 8.04 didn't suffer from the problem of creating a spurious device mapper "partition" before being able to create an LVM PV on the encrypted volume (though I was also correct in that the installer wanted to make believe we were doing that).