Bug 585980 – sys-apps/systemd-230 fails to boot with sys-kernel/dracut-040-r3

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Alexander Pilipenko 2016-06-15 01:28:16 UTC]

With dracut-040-r3 and systemd-230 system not boot (root fs not found, boot only rdshell). With 044 all works.

[Comment 1 Mike Gilbert 2016-06-15 07:30:21 UTC]

I'm guessing this is the issue.

http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=d4efc0aeeecc470d9a267b7f3c130f472488905c

[Comment 2 Mike Gilbert 2016-06-15 07:37:35 UTC]

commit ae2b005c8ca979ae9206deb04903e1717eead108
Author: Mike Gilbert <[e-mail]>
Date:   Wed Jun 15 03:35:03 2016 -0400

    sys-apps/systemd: add blocker on <sys-kernel/dracut-044
    
    Earlier versions of dracut do not include initrd-root-device.target in the
    initramfs image.
    
    Bug: https://bugs.gentoo.org/585980
    
    Package-Manager: portage-2.3.0_rc1_p20

 sys-apps/systemd/{systemd-230-r1.ebuild => systemd-230-r2.ebuild} | 1 +
 sys-apps/systemd/systemd-9999.ebuild                              | 1 +
 2 files changed, 2 insertions(+)

[Comment 3 Steffen Hau 2016-06-16 10:29:37 UTC]

It seems that sys-kernel/dracut-044 does not contain the fix from #c1, it was released month before the mentioned commit. 

/usr/lib/dracut/modules.d/01systemd-initrd/module-setup.sh:
    inst_multiple -o \
        $systemdsystemunitdir/initrd.target \
        $systemdsystemunitdir/initrd-fs.target \
        $systemdsystemunitdir/initrd-root-fs.target \
        $systemdsystemunitdir/initrd-switch-root.target \
        $systemdsystemunitdir/initrd-switch-root.service \

Would you mind creating a revbump of sys-kernel/dracut-044 with the commit?

[Comment 4 Mike Gilbert 2016-06-16 14:57:16 UTC]

Oops, my mistake. In that case, I have no idea why dracut-040 doesn't work for you.

Are you able to test with other dracut versions to narrow down where the problem was introduced?

As for backporting that patch, that's probably worth filing a separate bug for the dracut maintainers.

[Comment 5 Alexander Tsoy 2016-06-16 16:27:52 UTC]

Note that many systemd-related patches cannot be backported to dracut-040 without modification due to [1]. So I'm not sure if we really need to care about <dracut-041 + new systemd versions.

[1] http://git.kernel.org/cgit/boot/dracut/dracut.git/commit/?id=28eae10b7007c6a2b64876244e976eb4788e95b1

[Comment 6 Alexander Tsoy 2016-06-16 16:34:52 UTC]

(In reply to Alexander Tsoy from comment #5)

I meant <dracut-042 + new systemd versions

[Comment 7 Mike Gilbert 2016-06-16 16:50:47 UTC]

(In reply to Alexander Tsoy from comment #5)

I was just talking about backporting d4efc0aeeecc470d9a267b7f3c130f472488905c to dracut-044.

[Comment 8 Mike Gilbert 2016-06-16 16:54:33 UTC]

I guess you are right that there's really no point in figuring out exactly which dracut version works with systemd-230. The blocker on <dracut-044 will suffice.

I'm therefore marking this solved again. Backporting patches can be requested via a separate bug report.