On Mon, 16 Feb 2009 08:34:42 +0100 Milan Broz <mbroz@xxxxxxxxxx> wrote: > orinoco wrote: > > after an auto-software upgrade with siduxcc on an amd64 system on > > friday I cannot mount one of four luks partitions any more. > > It used to work before the upgrade without any problems: > > $ crypsetup luksOpen <device> <mapper> > > permanently results in "Command failed: Can not access device". > > Sometimes altered with "No key available with this passphrase" > > This basically means that cryptsetup cannot open the device before > any key operation. > It can be hw problem (is anything in syslog?) but also some > other subsystem can use the device. > > Try to check "dmsetup table" and "cat /proc/mdstat" if there > is not other mapping of the same device - check for major:minor of > device (ls -l /dev/<device>). > > Maybe some clever tools tries to open the device too? OMG! I found the error and I fear an irrevocable data loss: With the update the kernel switched the internal /dev/sdXX order of the hard disks - again. Unfortunately the former /dev/sdb5 was mounted in crypttab as encrypted swap with /dev/random as key before all other devices. And then I did reboot with the new kernel ... :-((((((( I did address the swap partitions with the /dev/sdXX name because there was not uuid in ls -la /dev/disk/by-uuid/ for them .... :-((((( That explains everything ... but I fear ... If anyone has any idea how to restore this partition I guess he would be a candiate for nobel price ... regards Orinoco
