Bug#827342: linux-image-4.5.0-2-amd64: luks rootfs not recognized at boot after upgrade to linux-image 4.5.5
On Wednesday 15 June 2016 12:21:56 Ben Hutchings wrote:
> > I have a LUKS rootfs on top of a mdadm managed raid0. Starting from 4.5.5 it
> > doesn't recognize the luks volume at boot. The same happens with 4.6.1
>
> LUKS volumes are recognised and set uo by userland, so are you sure
> this is due to the kernel upgrade?
>
> > The raid0 is not explicitly made with mdadm, it was previously handled by
> > dmraid I believe (fakeraid?)
>
> I'm assuming that after a delay you see an '(initramfs)' shell prompt.
> Do you see any error messages before that? If you then enter 'cat
> /proc/partitions', which devices does it show?
Downgrading to kernel 4.5.4 doesn't solve the issue, so it's probably not a kernel bug.
The only other upgrades in that timespan were e2fsprogs and e2fslibs, which I've also
downgraded. That also didn't fix the problem, although I'm not sure if I correctly
regenerated the initrd, since I'm not fluent with dracut..
I'll investigate further. This bug can be closed.
-Sander
Reply to: