-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Milan,
I can confirm that this fixed the problem!
It must have been that the partition in question was created with an old
version of cryptsetup.
Thanks to all involved in the bug fixing!
- --
Guy
On 16/06/10 12:19, Milan Broz wrote:
If
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 23:01, Marco d'Itri wrote:
And did udev create links to sdc1 in /dev/disk/ this time?
No :-(
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.14 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
On 06/16/2010 12:01 AM, Marco d'Itri wrote:
On Jun 15, Guy Heatley guy.encr...@member.fsf.org wrote:
r2d2:/home/guy# blkid -o udev /dev/sdc1
ID_FS_LABEL=/
ID_FS_LABEL_ENC=\x2f
ID_FS_UUID=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
ID_FS_UUID_ENC=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/06/2010 11:39, Milan Broz wrote:
Nope. You are mixing up two UUIDs:
luksUUID is the UUID from LUKS header of underlying device (/dev/sdc1),
ID_FS_UUID is UUID of fs on top of it (here labeled /, it is device
/dev/mapper/sdc1_crypt or
On 06/16/2010 12:57 PM, Guy Heatley wrote:
On 16/06/2010 11:39, Milan Broz wrote:
I'm not sure this is true - this device had not been opened by
cryptsetup at this point: There was no entry in /dev/mapper , it was not
an active Luks device.
If that device was LUKS formatted long ago, maybe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 16/06/2010 12:19, Milan Broz wrote:
On 06/16/2010 12:57 PM, Guy Heatley wrote:
On 16/06/2010 11:39, Milan Broz wrote:
I'm not sure this is true - this device had not been opened by
cryptsetup at this point: There was no entry in /dev/mapper ,
On Jun 15, Guy Heatley g...@member.fsf.org wrote:
If I run cryptsetup luksUUID /dev/sdb1 I get the UUID of this partition.
If I run udevadm info --name=/dev/sdb1 --query=all | grep -i uuid I
get nothing!
Please report the output of: blkid -o udev /dev/sda6 .
--
ciao,
Marco
signature.asc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jun 15, Guy Heatley g...@member.fsf.org wrote:
Please report the output of: blkid -o udev /dev/sda6 .
Err ... do you mean /dev/sb2 rather than /dev/sda6 ?
Yes.
- --
ciao,
Marco
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 12:11, Marco d'Itri wrote:
On Jun 15, Guy Heatley g...@member.fsf.org wrote:
If I run cryptsetup luksUUID /dev/sdb1 I get the UUID of this partition.
If I run udevadm info --name=/dev/sdb1 --query=all | grep -i uuid I
get nothing!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/06/2010 12:11, Marco d'Itri wrote:
On Jun 15, Guy Heatley g...@member.fsf.org wrote:
If I run cryptsetup luksUUID /dev/sdb1 I get the UUID of this partition.
If I run udevadm info --name=/dev/sdb1 --query=all | grep -i uuid I
get nothing!
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Marco,
On this boot, the problem partition is /dev/sdc1
r2d2:/home/guy# blkid -o udev /dev/sdc1
ID_FS_LABEL=/
ID_FS_LABEL_ENC=\x2f
ID_FS_UUID=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
ID_FS_UUID_ENC=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
On Jun 15, Guy Heatley guy.encr...@member.fsf.org wrote:
r2d2:/home/guy# blkid -o udev /dev/sdc1
ID_FS_LABEL=/
ID_FS_LABEL_ENC=\x2f
ID_FS_UUID=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
ID_FS_UUID_ENC=5e6cf0a2-ac35-4d8b-b1cf-f75ad8427551
ID_FS_SEC_TYPE=ext2
ID_FS_TYPE=ext3
And did udev create
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: udev
Version: 157-1
Severity: normal
- --- Please enter the report below this line. ---
I have a harddrive with an encrypted luks partition. It usually appears
as /dev/sdb1 on my system.
I want to move to a persistent naming convention
13 matches
Mail list logo
