http://bugzilla.suse.com/show_bug.cgi?id=942940 http://bugzilla.suse.com/show_bug.cgi?id=942940#c17 --- Comment #17 from Thomas Blume <thomas.blume@suse.com> --- (In reply to Alexander Nolting from comment #16)

(In reply to Thomas Blume from comment #13)

...

(In reply to Alexander Nolting from comment #12)

...

Hello Thomas,

I'm followed the test Jan did on github -> https://github.com/systemd/systemd/issues/1027. As I said in my initial comment I didn't get the systemd-tty-aks-password command output due to the fact that it is not called/running or shown on the right tty. This is one thing which needs to be examined or if the rdsosreport is right, than the issue may be the fact the the root partition is not mounted before the unit cr_home is called. That this may be the right way to do further investigations is also found in the rdsosreport as there uuid for home partition is found as valid and the system try's to mount it which in the fails because of no root partition.

Regards Alex

Hm, due to 'rd.break=initqueue' your boot stops with the Emergency shell in the initqueue stage of dracut:

-->-- [ 3.989095] linux-gwd0 systemd[1]: Starting dracut initqueue hook... [ 3.989253] linux-gwd0 systemd[1]: Reached target System Initialization. [ 3.989413] linux-gwd0 systemd[1]: Starting System Initialization. [ 3.989564] linux-gwd0 systemd[1]: Reached target Basic System. [ 3.989714] linux-gwd0 systemd[1]: Starting Basic System. [ 3.988182] linux-gwd0 kernel: audit: type=1130 audit(1442329999.592:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 3.996942] linux-gwd0 kernel: ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 4.003987] linux-gwd0 dracut-initqueue[276]: Warning: Break before initqueue [ 4.007767] linux-gwd0 dracut-initqueue[276]: Warning: /dev/disk/by-uuid/000a0e56-93f7-4edf-8f3b-d3130b789cf4 does not exist [ 4.025155] linux-gwd0 systemd[1]: Starting Setup Virtual Console... [ 4.026968] linux-gwd0 systemd-vconsole-setup[283]: /usr/bin/setfont failed with error code 1. [ 4.027164] linux-gwd0 systemd-vconsole-setup[283]: mapscrn: cannot open map file _trivial_ [ 4.033324] linux-gwd0 systemd[1]: Started Setup Virtual Console. [ 4.033503] linux-gwd0 unknown[1]: <audit-1130> pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-vconsole-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' [ 4.033797] linux-gwd0 kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input6 [ 4.034545] linux-gwd0 systemd[1]: Starting Dracut Emergency Shell... --<--

At this stage, neither system root not any other mount is started. All that comes later later. Where did you actually see that the /home mount is done before the /sysroot mount?

Additionally I would like to point exactly on this fact: In this line

[ 4.007767] linux-gwd0 dracut-initqueue[276]: Warning: /dev/disk/by-uuid/000a0e56-93f7-4edf-8f3b-d3130b789cf4 does not exist

this is what I'm find curious. I will give the new systemd immidiately a try and then I will update the case. But I'm having some concerns that my issue is not related to systemd but more to way dracut trys to find devices --> searching by-uuid folder which is for some reason not present here.

Yes, it tells you that the system root device doesn't exist yet. But this is only a warning. Before you test the new systemd, please remove the rd.break boot parameter or the system will stop again at the initqueue stage. If you still see the issue that /home doesn't get mounted with the new systemd, please remove the 'quiet' boot parameter and add: debug rd.debug rd.udev.debug instead. When the system is up, please provide the output of: journalctl -axb -- You are receiving this mail because: You are on the CC list for the bug.