I tried to "backup" my system to a crypt_LUKS partition on a USB drive.
This has been the way I've been backing up for quite some time.
This now fails with Rawhide:
[root@tlondon packages]# mount /dev/sdc1 /mnt mount: unknown filesystem type 'crypto_LUKS' [root@tlondon packages]#
I've tried booting older kernels, reverting device-mapper, lvm2 and util-linux-ng packages to no avail.
[root@tlondon packages]# fdisk /dev/sdc
The number of cylinders for this disk is set to 38913. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): print
Disk /dev/sdc: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0005772c
Device Boot Start End Blocks Id System /dev/sdc1 1 38913 312568641 83 Linux
Command (m for help): quit
[root@tlondon packages]#
Anyone successfully mounting LUKS encrypted partitions with rawhide?
This a known issue?
I've BZ'ed this here: https://bugzilla.redhat.com/show_bug.cgi?id=506960
Help appreciated.
tom
I do not believe this is an issue with Rawhide. Try to unlock the partition by issuing a
cryptsetup luksOpen /dev/sdc1 usbStick
This command should create a block device '/dev/mapper/usbStick' which you should be able to mount normally
mount /dev/mapper/usbStick /mnt
-Sean
On Fri, Jun 19, 2009 at 11:12 AM, Tom London selinux@gmail.com wrote:
I tried to "backup" my system to a crypt_LUKS partition on a USB drive.
This has been the way I've been backing up for quite some time.
This now fails with Rawhide:
[root@tlondon packages]# mount /dev/sdc1 /mnt mount: unknown filesystem type 'crypto_LUKS' [root@tlondon packages]#
I've tried booting older kernels, reverting device-mapper, lvm2 and util-linux-ng packages to no avail.
[root@tlondon packages]# fdisk /dev/sdc
The number of cylinders for this disk is set to 38913. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with:
- software that runs at boot time (e.g., old versions of LILO)
- booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): print
Disk /dev/sdc: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0005772c
Device Boot Start End Blocks Id System /dev/sdc1 1 38913 312568641 83 Linux
Command (m for help): quit
[root@tlondon packages]#
Anyone successfully mounting LUKS encrypted partitions with rawhide?
This a known issue?
I've BZ'ed this here: https://bugzilla.redhat.com/show_bug.cgi?id=506960
Help appreciated.
tom
Tom London
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Fri, Jun 19, 2009 at 10:29 AM, Sean Maddenspmadden@gmail.com wrote:
I do not believe this is an issue with Rawhide. Try to unlock the partition by issuing a
cryptsetup luksOpen /dev/sdc1 usbStick
This command should create a block device '/dev/mapper/usbStick' which you should be able to mount normally
mount /dev/mapper/usbStick /mnt
-Sean
On Fri, Jun 19, 2009 at 11:12 AM, Tom London selinux@gmail.com wrote:
I tried to "backup" my system to a crypt_LUKS partition on a USB drive.
This has been the way I've been backing up for quite some time.
This now fails with Rawhide:
[root@tlondon packages]# mount /dev/sdc1 /mnt mount: unknown filesystem type 'crypto_LUKS' [root@tlondon packages]#
I've tried booting older kernels, reverting device-mapper, lvm2 and util-linux-ng packages to no avail.
[root@tlondon packages]# fdisk /dev/sdc
The number of cylinders for this disk is set to 38913. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with:
- software that runs at boot time (e.g., old versions of LILO)
- booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): print
Disk /dev/sdc: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0005772c
Device Boot Start End Blocks Id System /dev/sdc1 1 38913 312568641 83 Linux
Command (m for help): quit
[root@tlondon packages]#
Anyone successfully mounting LUKS encrypted partitions with rawhide?
This a known issue?
I've BZ'ed this here: https://bugzilla.redhat.com/show_bug.cgi?id=506960
Help appreciated.
Thanks. Will have to wait until I get home....
Just curious, if not Rawhide, what? Carry over from F11?
tom
Tom London on 06/19/2009 12:37 PM wrote:
Thanks. Will have to wait until I get home....
Just curious, if not Rawhide, what? Carry over from F11?
tom
You've always had to unlock the LUKS partition before you can mount it. This is not a Fedora feature. Maybe you used nautilus to mount the usb stick? That would have prompted you for a password (which does the unlocking for you).
On Fri, Jun 19, 2009 at 10:40 AM, Michael Cronenworthmike@cchtml.com wrote:
Tom London on 06/19/2009 12:37 PM wrote:
Thanks. Will have to wait until I get home....
Just curious, if not Rawhide, what? Carry over from F11?
tom
You've always had to unlock the LUKS partition before you can mount it. This is not a Fedora feature. Maybe you used nautilus to mount the usb stick? That would have prompted you for a password (which does the unlocking for you).
The passphrase/key to unlock has been stored in my keyring for quite a while, so the unlocking/mounting has proceeded automatically.
Something has changed this behavior in the last several weeks.....
tom
On Fri, Jun 19, 2009 at 10:47 AM, Tom Londonselinux@gmail.com wrote:
On Fri, Jun 19, 2009 at 10:40 AM, Michael Cronenworthmike@cchtml.com wrote:
Tom London on 06/19/2009 12:37 PM wrote:
Thanks. Will have to wait until I get home....
Just curious, if not Rawhide, what? Carry over from F11?
tom
You've always had to unlock the LUKS partition before you can mount it. This is not a Fedora feature. Maybe you used nautilus to mount the usb stick? That would have prompted you for a password (which does the unlocking for you).
The passphrase/key to unlock has been stored in my keyring for quite a while, so the unlocking/mounting has proceeded automatically.
Something has changed this behavior in the last several weeks.....
And prior to that, gnome-mount (?) would present a popup for my key when the drive was plugged in.
tom
On Fri, Jun 19, 2009 at 10:48 AM, Tom Londonselinux@gmail.com wrote:
On Fri, Jun 19, 2009 at 10:47 AM, Tom Londonselinux@gmail.com wrote:
On Fri, Jun 19, 2009 at 10:40 AM, Michael Cronenworthmike@cchtml.com wrote:
Tom London on 06/19/2009 12:37 PM wrote:
Thanks. Will have to wait until I get home....
Just curious, if not Rawhide, what? Carry over from F11?
tom
You've always had to unlock the LUKS partition before you can mount it. This is not a Fedora feature. Maybe you used nautilus to mount the usb stick? That would have prompted you for a password (which does the unlocking for you).
The passphrase/key to unlock has been stored in my keyring for quite a while, so the unlocking/mounting has proceeded automatically.
Something has changed this behavior in the last several weeks.....
And prior to that, gnome-mount (?) would present a popup for my key when the drive was plugged in.
OK, now that I'm back home, I can test some more.
It appears that the "automagic" disk/partition mounting (DeviceKit-disks ?, gnome-disk-utility? gnome-mount? other?) is properly running "cryptsetup" on the partition, since I see a newly created /dev/dm-2:
[tbl@tlondon ~]$ ls -l /dev/dm* brw-rw----. 1 root disk 253, 0 2009-06-19 17:54 /dev/dm-0 brw-rw----. 1 root disk 253, 1 2009-06-19 17:54 /dev/dm-1 brw-rw----. 1 root disk 253, 2 2009-06-19 17:57 /dev/dm-2 [tbl@tlondon ~]$
[dm-0 is / and dm-1 is swap, I believe]
I can mount /dev/dm-2:
[root@tlondon ~]# [root@tlondon ~]# mount /dev/dm-2 /mnt [root@tlondon ~]# [root@tlondon ~]# mount /dev/mapper/vg_tlondon-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw) /dev/sda2 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw,rootcontext="system_u:object_r:tmpfs_t:s0") none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) gvfs-fuse-daemon on /home/tbl/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=tbl) /dev/sdb1 on /media/E0FD-1813 type vfat (rw,nosuid,nodev,uhelper=devkit,uid=500,gid=500,shortname=lower,dmask=0077,utf8=1,flush) /dev/dm-2 on /mnt type ext4 (rw) [root@tlondon ~]#
So, the crypto is properly working as is gnome-keyring.
But the subsequent "mount" on /media/Backup (Backup is the partition's label) fails.
If I run palimpsest before I manually mount, I see no options to mount.
I will reassign the BZ to gnome-disk-utility (I'm guessing here, since only it and DeviceKit-disks have been updated recently) and hope for the best.
tom