Having trouble re-mounting a LVM that I encrypted with LUKS.Hopping someone has something beyond 'yup, you broke it' as I'd like to get back the data.I believ... [by bsdwrangler]
I'm having trouble with the disk setup in the F 19 installer. I used to be able to create a LUKS volume at the device level with the exception of the boot drive. In otherwords from cli I would do a 'cryptsetup luksFormat /dev/sdb <name of volume>'. Once the LUKS volume was created I would go straight to creating the volume group and logical volumes under LVM2.
I have a luks encrypted device that I mount on demand by clicking on it in the places menu (yes I am using Gnome fallback mode). In Fedora 16 everything worked fine but in Fedora 17 I am facing two issues.
First root password is asked to unlock the luks system.
[ update: manually mounting them can now be done if you read all the way though... retaining the entire post as it may help others... BUT root cause is still outstanding in that encrypted disks that automatically setup LVM volumes at boot in F17 will not in F18]
I have been unable to access encrypted LUKS volumes since I used fedup to upgrade to F18.
I have a Debian Linux system (amd64) installed on a RAID-1 system encrypted device (LVM on LUKS) and will have a RAID-6 of >=4 disks where I'll put my data (LUKS and maybe LVM).
I think the basic idea is to unlock the system encrypted partition (at boot at local or via ssh) and to store a keyfile in /etc/crypttab for the RAID-6 encrypted partition. Does that pose a security risk ? I mean ...
I'm running several Linux Desktop Systems with Full Drive Encryption. cryptsetup LUKS. The main LVM group, incl. the root volume, gets opened from inside the initrd. I think many of you will know this.And Linux is a multiuser Operating System, so there are several users all with their own LUKS Key.