[Hardy] Cryptsetup fails with 2.6.24-14-generic

Bug #211729 reported by Martin Gräßlin
2
Affects Status Importance Assigned to Milestone
linux-meta (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: linux-image-generic

I have a problem with cryptsetup since kernel update to 2.6.24-14-generic.

First I have to describe my setup:
I have a completely encrypted filesystem with cryptsetup. And there is a script wich mounts my usb key and reads the passphrase for the / partition from a file on the usb key.

Since the upgrade to 2.6.24-14-generic I have the problem that the script cannot mount the usb key so cryptsetup fails and I can't start the system. But I can see that the script is executed. So during creation of the initial ramdisk everything seems to work fine. With 2.6.24-12-generic I have no problems. Script is working correctly.

Do you have any idea what could be the problem? Is it possible that the /dev/sd* changed with this update? Or is perhaps a module renamed which I need to access the usb key?

If you need any more information, pls ask. I kindly attach all the config files, scripts which are used in this setup.

Revision history for this message
Martin Gräßlin (ubuntu-martin-graesslin) wrote :

I have no idea why it changed, but the reason is that the USB-key is now /dev/sdc and not /dev/sdb
So it is working agian.

Revision history for this message
Matt Zimmerman (mdz) wrote :

Device names (particularly for removable devices) are not persistent, and may vary each time the device is connected. In order to avoid problems like this, you should mount the device by UUID rather than by a hardcoded device name, as is done for the root filesystem in a default Ubuntu installation.

Changed in linux-meta:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.