F17 luks weirdness

[Rick Stevens]

On 05/23/2012 11:09 AM, Peter A wrote:
> All,
>
> I'm having an issue with encrypted disk setup on my Dell M6600 laptop.
> During boot of Fedora 17 (originally installed from alpha, yum updated
> current ever since), I get prompted for the password but the device
> shown in the prompt changes. If it ends up picking md127p1 the boot
> device is not decrypted the devices but instead fails with a luks error
> trying to access the device. If I get prompted for the pass phrase for
> any other device, boot up is successful, including mounting the md127p1
> partition.
>
> I've got four drives in the system: Two MSATA (one in the optical bay in
> a sata to msata converter) 120GB disks for OS and most other stuff (sdc
> and sdd), two Momentus XT 750GB for data (sda and sdb). They are set up
> as two mirrors in the Intel bios (Intel 82801 in a QM67).
>
> The boot raid consists of sdc and sdd. The drives are partitioned into 3
> partitions:
> Number Start End Size File system Name Flags
> 1 1049kB 2097kB 1049kB bios_grub
> 2 2097kB 526MB 524MB ext4 ext4 boot
> 3 526MB 120GB 120GB
> Mount point for p2 is /boot, for 3 /
>
> The other raid consists of sda and sdb. The drives are partitioned into
> 2 partitions:
> Number Start End Size File system Name Flags
> 1 1049kB 17.2GB 17.2GB
> 2 17.2GB 750GB 733GB
> First partition is swap, the second is mounted under my home as
> /home/loony/data
>
> MD seems to look good too
> # cat /proc/mdstat
> Personalities : [raid1]
> md124 : active raid1 sda[1] sdb[0]
> 732571648 blocks super external:/md125/0 [2/2] [UU]
>
> md126 : active raid1 sdc[1] sdd[0]
> 117218304 blocks super external:/md127/0 [2/2] [UU]
>
> md127 : inactive sdc[1](S) sdd[0](S)
> 4776 blocks super external:imsm
>
> md125 : inactive sdb[1](S) sda[0](S)
> 5608 blocks super external:imsm
>
> unused devices: <none>
>
> Dracut related boot messages from a successful boot are:
> [ 3.399954] dracut: dracut-018-35.git20120510.fc17
> [ 3.494352] dracut: rd.lvm=0: removing LVM activation
> [ 4.763255] dracut: Starting plymouth daemon
> [ 4.891705] dracut: rd.dm=0: removing DM RAID activation
> [ 5.322356] dracut: luksOpen /dev/md126p3
> luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160 none
> [ 11.592058] dracut: Checking ext4:
> /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160
> [ 11.596940] dracut: issuing e2fsck -a
> /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160
> [ 11.615698] dracut:
> /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160: clean,
> 481162/7299072 files, 7478284/29175296 blocks
> [ 11.622597] dracut: Remounting
> /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160 with -o ro
> [ 11.653308] dracut: Mounted root filesystem
> /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160
> [ 11.787906] dracut: Switching root
>
> The grub entry for the kernel is:
> linux /vmlinuz-3.3.4-5.fc17.x86_64
> root=/dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160 ro
> rd.md.uuid=19fdc234:857a89e5:8831880f:c92180dc rd.lvm=0 rd.dm=0
> SYSFONT=True rd.md.uuid=39828da2:5ba3ed07:e158fca9:b46f3ac3 KEYTABLE=us
> rd.md.uuid=92c96695:945f79c8:050bcb03:353f85c5
> rd.luks.uuid=luks-6fbe3ef9-b08b-4d59-92fa-c4a4746c6817
> rd.md.uuid=b0b5044d:22352807:56f708f9:0264f70c
> rd.luks.uuid=luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160 LANG=en_US.UTF-8
>
>
> The issue I have is that I get randomly asked at boot time for pass
> phrases for md127p1 (does not work), or for any of the other encrypted
> partitions (works).
> The error I'm getting with md127p1 appears only after 15-20 seconds and
> says that /dev/mapper/luks-a417a2f6-988b-49bf-be2e-e2cf34dcc160 wasn't
> found.
>
> If I enter a incorrect password when prompted for md127p1 it works as
> expected and prompts again after a second or two. Only if I enter the
> correct password, I see this error..
>
> So, I have two issues. For one, why am I prompted for a different device
> on boot up? Shouldn't I always be prompted for the same device? And
> second, why does md127p1 fail?
>
> I somehow have the suspicion that the answer is in the grub kernel entry
> but I can't find any documentation if multiple rd.luks.uuid entries are
> valid, if the order matters and what is the appropriate entry to be
> there...

Technically, this doesn't belong on this list as F17 hasn't been
released yet. It belongs on the fedora test list
(test at lists.fedoraproject.org).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks at alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-  Silence!  Or I shall replace you with a very small shell script!  -
-                                                - The Wizard of OS  -
----------------------------------------------------------------------