Bug 20319 - Encrypted root-fs does not boot after installation
Summary: Encrypted root-fs does not boot after installation
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: NEEDINFO
Keywords: 6sta2
Depends on:
Blocks:
 
Reported: 2017-02-19 20:25 CET by Ulrich Beckmann
Modified: 2017-03-03 16:55 CET (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
CLI-output: trying to identify partition (3.94 KB, text/plain)
2017-02-19 20:28 CET, Ulrich Beckmann 		Details
report.bug.xz from 2nd attempt sda16 (186.58 KB, application/x-xz)
2017-02-21 21:49 CET, Ulrich Beckmann 		Details
grub2-install /dev/sda --debug --debug-image=all (45.74 KB, application/gzip)
2017-02-23 19:30 CET, Ulrich Beckmann 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Ulrich Beckmann 2017-02-19 20:25:53 CET 
I tested the installation with an encrypted root filesystem, type xfs, on real UEFI hardware, classical installer. Boot-partition was /dev/sda13, root-partition /dev/sda14, no separate home-partition. The installation went smooth. I got a message of sucess. The subsequent boot failed then.

I could rescue the installation with the following steps:
- open the encrypted root-partition
- mount /boot
- chroot into the root-partition
- repeat the installation of grub ( # grub2-install /dev/sda )
- recreate the initramfs ( # mkinitrd )
- run grub2-mkconfig

I repeated this test with /dev/sda12 (boot) and /dev/sda16 (root) and got the same error. Booting in rescue mode get the error message:

Dracut warning: Could not boot.
[...] dracut warning: /dev/disk/by-uuid/04d0c5a5-6519-445f ... does not exist.

I can not identify such partition in my system. It does not exist.
Comment 1 Ulrich Beckmann 2017-02-19 20:28:40 CET 
Created attachment 8969 [details]
CLI-output: trying to identify partition
Ulrich Beckmann 2017-02-19 20:29:09 CET

Keywords: (none) => 6sta2

Comment 2 Marja Van Waes 2017-02-21 20:44:18 CET 
Please attach /root/drakx/report.bug.xz from one or both of those installs :-)

There's some vague memory that there was something with XFS, but I don't remember what it was :-/

CC: (none) => marja11, zen25000
Assignee: bugsquad => mageiatools
Whiteboard: (none) => NEEDINFO

Comment 3 Ulrich Beckmann 2017-02-21 21:49:20 CET 
Created attachment 8973 [details]
report.bug.xz from 2nd attempt sda16

The 2nd test is still untouched. I did not try any rescue.
Comment 4 Barry Jackson 2017-02-22 00:36:39 CET 
You could try running:

grub2-install /dev/sda --debug --debug-image=all > grub2_install_debug.txt

...which may give some clues - it will give a lot of output.
Comment 5 Ulrich Beckmann 2017-02-23 19:30:56 CET 
Created attachment 8981 [details]
grub2-install /dev/sda --debug --debug-image=all

I tested grub2-install as indicated in #4.
The installation succeeds, and I could not spot any error. Unfortunately the subsequent boot is also in debug mode. I could repeat the test until the error message.

Ulrich
Comment 6 Ulrich Beckmann 2017-02-23 19:34:47 CET 
Sorry, I could *not* repeat the test until the error message.
Comment 7 Ulrich Beckmann 2017-03-03 16:55:53 CET 
Retested twice with current sta2 classical iso of 2017-03-01. I chose ext4 and xfs as encrypted root filesystem. Both work fine at reboot, so the issue is resolved.

It looks like it was not a grub related issue, as grub2* remained unchanged since Jan. I guess that it was an initrd issue and it was fixed with Martin Whitaker's recent changes of partitioning in the install media.

Thanks, Marja and Barry

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.