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

2016-06-15 Thread Sander van Grieken
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

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

2016-06-15 Thread Ben Hutchings
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 >

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

2016-06-15 Thread Sander van Grieken
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 The raid0 is not explicitly made