Bug#827438: systemd: boot fails with rootfs on luks after systemd upgrade

[Michael Biebl]

Control: tags -1 + moreinfo

On Thu, 16 Jun 2016 08:39:53 +0200 Sander van Grieken
<sander at outrightsolutions.nl> wrote:
> Package: systemd
> Version: 229-6
> Severity: important
> 
> Upgrading systemd from 229-6 to 230-2 broke my boot.
> 
> I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 230-2 it
> doesn't recognize the luks volume at boot.
> 
> The raid0 is not explicitly made with mdadm, it was previously handled by
> dmraid I believe (fakeraid?)
> 
> I'm using dracut-40 instead of initramfs
> (yes there's a newer dracut, but that has troubles with booting this setup too,
> so I've pinned on 040)
> 

So, does it already fail during initramfs or actually later, during
regular boot? Failing to find the rootfs sounds like an initramfs
problem, so in this case it should probably be reassigned to dracut.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20161216/09af7f4b/attachment.sig>