Upgrade causes disks to be renamed but does not update crypto setup

[Adam Greig]

My Ubuntu installation is on two partitions that are both encrypted (inside, LVM).
When upgrading from 8.10 to 9.04, the labels for the disks - sda, sdb and sdc - all swapped around.
For instance, sda became sdb, sdc became sda and sdb became sdc.

This presents a major problem as the encryption setup seems to mount the disks by their path name (or potentially by something else that has also changed). This means the only way to be able to boot from the hard drives is to enter an incorrect passphrase six times, at which point the system hangs waiting for root, eventually gives up and drops me to a busybox prompt.

From there I am able to use cryptsetup to mount the two encrypted partitions properly from the new names, and the boot proceeds as normal from there onwards.

It seems that something is causing the disks to be renamed, but the cryptography setup is not changing to reflect the new disk names, making the boot process fail.

I'm not sure which package to report this under - is it the crypt program's fault for not detecting the new drives, the updater's fault for not tying it all together or something else's fault for renaming the drives in the first place?

[Adam Greig (adamgreig)]

This can be fixed manually by updating /etc/crypttab to reflect the new hard drive names.

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

[Fabio Marconi (fabiomarconi)]

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Fabio Marconi (fabiomarconi)]

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

[Adam Greig (adamgreig)]

Sorry for the delay. I've since upgraded the machine that had the issue to 10.04 with a fresh install, so didn't find out if the bug is still around.

However, as I understand it the crypto set up now uses the UUID for the disks, which I believe will mean even if the device names changed the crypto should still work.