Re: after sidux upgrade: "Can not access device" with 1 of 4 luks partitions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

Milan
--
mbroz@xxxxxxxxxx


---------------------------------------------------------------------
dm-crypt mailing list - http://www.saout.de/misc/dm-crypt/
To unsubscribe, e-mail: dm-crypt-unsubscribe@xxxxxxxx
For additional commands, e-mail: dm-crypt-help@xxxxxxxx


[Index of Archives]     [Device Mapper Devel]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux