On Fri, Jan 18, 2013 at 01:26:36PM -0500, Bill Davidsen wrote:
> David A. De Graaf wrote:
> >Fedora 18.
> >
> >What a disaster! What were they thinking when they threw away a
> >perfectly good installer and inflicted this new User Interface on us?
Despite the obstacles presented by the new installer User Interface,
I have succeeded in installing F18 on a laptop - with one exception.
So I have one specific question that I hope some expert out there can
answer.
How can I regain access to the encrypted partition that contains the
old F17 root filesystem? I need pretty precise instructions, or a
pointer to documentation that provides the same.
Access to encrypted partitions entails arcane magic that used to be
embedded in the installer. That is, all the partitions that use the
same key during the installer's configuration just showed up after
first-boot in /dev/mapper, eg
$ /bin/ls -l /dev/mapper
total 0
crw------- 1 root root 10, 236 Jan 18 14:07 control
lrwxrwxrwx 1 root root 7 Jan 18 14:17 f17enc -> ../dm-3
lrwxrwxrwx 1 root root 7 Jan 18 14:07
luks-0fc2a8e0-9d71-4af7-853e-afb3c89794e2 -> ../dm-1
lrwxrwxrwx 1 root root 7 Jan 18 14:07
luks-9800d5dd-f281-4750-b0cf-42282401ace0 -> ../dm-2
lrwxrwxrwx 1 root root 7 Jan 18 14:07
luks-dc53437b-7efa-426c-870c-972d96f5f0ca -> ../dm-0
and once you decoded that crazy UUID notation, could be mounted.
Because the partitions' roles were designated during installation,
the mounting was handled automatically.
With the new inept installer, it is impossible to designate a
particular partition's role as, say, a filesystem to be mounted as
/f17. As a result, the LUKS decryption fails to include that
partition in the /dev/mapper set.
As I said in the original post, I've found a manual workaround.
But that isn't good enough. I need to have that partition decrypted
automatically and included in /dev/mapper/ so an entry in /etc/fstab
will mount the filesystem automatically, every time.
What magic is required to add a specific partition back into the list
of LUKS filesystems that are decrypted automatically at boot time?
All the encrypted partitions use a common key. I just don't know how
to persuade the boot process to include them all.
> >Workaround
> >
> >Here's how to mount the encrypted old f17 partition:
> > # cryptsetup luksOpen /dev/sda5 f17enc
> > Enter passphrase for /dev/sda5: ++++++++++++++++
> >That creates the required entry in /dev/mapper that the installer forgot:
> > # ll /dev/mapper
> > total 0
> > crw------- 1 root root 10, 236 Jan 16 19:33 control
> > lrwxrwxrwx 1 root root 7 Jan 17 11:38 f17enc -> ../dm-3
> > lrwxrwxrwx 1 root root 7 Jan 16 19:33 luks-0fc2a8e0-9d71-4af7-853e-afb3c89794e2 -> ../dm-1
> > lrwxrwxrwx 1 root root 7 Jan 16 19:33 luks-9800d5dd-f281-4750-b0cf-42282401ace0 -> ../dm-2
> > lrwxrwxrwx 1 root root 7 Jan 16 19:33 luks-dc53437b-7efa-426c-870c-972d96f5f0ca -> ../dm-0
> >
> >It can then be mounted in the usual way:
> > # mount /dev/mapper/f17enc /f17
> >
> >I don't know yet how to accomplish this automatically on a reboot.
> >
--
David A. De Graaf DATIX, Inc. Hendersonville, NC
dad@xxxxxxxx www.datix.us
Q: Why do programmers confuse Halloween and Christmas?
A: Because OCT 31 == DEC 25.
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
