https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c Ye Yuan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yyuan@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c1 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jnelson-suse@jamponi.net --- Comment #1 from Thomas Renninger 2013-10-30 08:45:20 UTC --- Could you be somewhat more specific and explain what exactly does not work? I tried crypto support and the text/serial console based approach did not work for both, mkinitrd and dracut: https://bugzilla.novell.com/show_bug.cgi?id=843668 which got a duplicate of: https://bugzilla.novell.com/show_bug.cgi?id=834063 and there mkinitrd and dracut was affected. Dracut asked for the password and everything seemed to be in place that far. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c3 Jon Nelson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jnelson-suse@jamponi.net | --- Comment #3 from Jon Nelson 2013-11-04 00:42:35 UTC --- More results. With dracut + plymouth, it simply hangs for a very long time, eventually timing out, unable to find the root device. It never asks for a passphrase. The following all take place /without/ plymouth installed: With dracut and without plymouth, I get a blank screen. With dracut, without plymouth, and by removing "quiet" and "splash=silent" from the boot options, I get a very slow boot and - after a very long delay - a message about failure to find the root device (which is mounted by UUID). Following the (excellent!) Fedora docs, I added 'auto.rd' to the boot opts and removed "quiet" and "splash=silent". This time, I was asked *three times* for passphrases, but it did boot. In all cases but the last, 'systemd-modules-load.service' also fails. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c5 Shawn Dunn changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sfalken@opensuse.org --- Comment #5 from Shawn Dunn 2014-02-13 02:57:04 UTC --- (In reply to comment #3)

More results.

With dracut + plymouth, it simply hangs for a very long time, eventually timing out, unable to find the root device. It never asks for a passphrase.

The following all take place /without/ plymouth installed:

With dracut and without plymouth, I get a blank screen.

With dracut, without plymouth, and by removing "quiet" and "splash=silent" from the boot options, I get a very slow boot and - after a very long delay - a message about failure to find the root device (which is mounted by UUID).

Following the (excellent!) Fedora docs, I added 'auto.rd' to the boot opts and removed "quiet" and "splash=silent". This time, I was asked *three times* for passphrases, but it did boot.

In all cases but the last, 'systemd-modules-load.service' also fails.

John, you might try the new version that's in Base:System right now (dracut-036), as it improves encrypted volume support. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c7 --- Comment #7 from Julian Wolf 2014-03-10 16:53:40 UTC --- Tomas: Tried this setup last week and couldn't reproduce that issue. Could you please attach some logs (journalctl, dmesg, /var/log/messages)? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c9 --- Comment #9 from Tomáš Chvátal 2014-03-12 08:17:15 UTC --- Created an attachment (id=581810) --> (http://bugzilla.novell.com/attachment.cgi?id=581810) mkinitrd command output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c11 --- Comment #11 from Tomáš Chvátal 2014-03-12 08:20:37 UTC --- Created an attachment (id=581813) --> (http://bugzilla.novell.com/attachment.cgi?id=581813) mount command output -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c13 Tomáš Chvátal changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|tchvatal@suse.com | --- Comment #13 from Tomáš Chvátal 2014-03-12 08:32:52 UTC --- When I try to remount the thing localy it says I can't change the data mode. So the solution: mount -t tmpfs none /etc/ mount -o remount,rw /dev/system/root / When I edit the fstab to not contain only noatime in options the root is properly mounted with RW option. So maybe the issue is related with wrongly doing the remount from the read-only state by dracut? (note it really works fine with the old mkintrd) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c15 --- Comment #15 from Julian Wolf 2014-03-12 10:24:10 UTC --- There seems to be a bug mounting root with data=writeback. It is mounted in ordered mode instead (bnc#864669). This obviously happens here, too. As you say it works when you remove everything from fstab besides noatime this might be related. Just found a similiar bug for Fedora which points to data=writeback, too (https://bugzilla.redhat.com/show_bug.cgi?id=969648) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c17 --- Comment #17 from Julian Wolf 2014-04-11 15:43:04 UTC --- Digged into this issue today and it seems like dracut mounts the volume with data=ordered (and read-only, but that doesn't hurt at this point) from the beginning no matter what is specified in fstab. This stuff is happening here: modules.d/95rootfs-block/mount-root.sh I just jumped out of the boot process with 'rd.break rd.shell' which afaik happens just before switching root. So I think it should be mounted with writeback here already. But that is not the case: /dev/mapper/system-root on /sysroot type ext4 (ro,relatime,data=ordered) As a result the remount with another data mode won't work: [ 60.218562] EXT4-fs (dm-1): Cannot change data mode on remount and systemd-remount-fs fails to do so. So the initial dracut mount is kept. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c19 --- Comment #19 from Tomáš Chvátal 2014-04-14 11:34:12 UTC --- Yeah bug#864669 is duplicate. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c21 --- Comment #21 from Julian Wolf 2014-04-25 11:12:52 UTC --- So finally we found the issue and the behavior seems "works as designed". mount(8) says: "To use modes other than ordered on the root filesystem, pass the mode to the kernel as boot parameter, e.g. rootflags=data=journal." So if I specify rootflags=data=writeback as boot parameter everything works as expected and the data=writeback option is written into sysroot.mount. All mounting is done by systemd, first with sysroot.mount (generated by fstab-generator) and later remounted by systemd-remount-fs. dracut has functionality to mount, parse fstab and remount with desired options afterwards (mount-root.sh, mentioned in comment 17) but this is only used when systemd isn't included in initrd. I think mkinitrd had some built-in functionality for this, too. systemd does not do that. It takes a look into fstab for other partitions (data=writeback in fstab works fine for non-root-partitions) but for the root-partition it does not do a remount with fstab options. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=847159 https://bugzilla.novell.com/show_bug.cgi?id=847159#c22 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #22 from Thomas Renninger 2014-06-17 15:28:30 UTC --- So this is working as expected, right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.