[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#827342: linux-image-4.5.0-2-amd64: luks rootfs not recognized at boot after upgrade to linux-image 4.5.5



Control: tag -1 moreinfo

On Wed, 2016-06-15 at 08:56 +0200, Sander van Grieken wrote:
> Package: src:linux
> Version: 4.5.5-1
> Severity: important
> 
> Upgrading linux kernel from 4.5.4 to 4.5.5 broke my boot.
> 
> 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?

Ben.

-- 
Ben Hutchings
Reality is just a crutch for people who can't handle science fiction.

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: