Bug#923400: initramfs-tools: failure inside chroot: W: Couldn't identify type of root file system for fsck hook

2019-02-27 Thread Jonas Smedegaard
Quoting Ben Hutchings (2019-02-27 19:37:41) > Control: severity -1 wishlist > Control: retitle -1 Add option to override filesystem type detection > > On Wed, 2019-02-27 at 18:38 +0100, Jonas Smedegaard wrote: > > Quoting Jonas Smedegaard (2019-02-27 17:45:33) > > > Building a system image using

Bug#923400: initramfs-tools: failure inside chroot: W: Couldn't identify type of root file system for fsck hook

2019-02-27 Thread Ben Hutchings
Control: severity -1 wishlist Control: retitle -1 Add option to override filesystem type detection On Wed, 2019-02-27 at 18:38 +0100, Jonas Smedegaard wrote: > Quoting Jonas Smedegaard (2019-02-27 17:45:33) > > Building a system image using multistrap, > > including generating an initial ramdisk,

Bug#923400: initramfs-tools: failure inside chroot: W: Couldn't identify type of root file system for fsck hook

2019-02-27 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2019-02-27 17:45:33) > Building a system image using multistrap, > including generating an initial ramdisk, > worked fine recently. > > Now it fails with this error message: > > W: Couldn't identify type of root file system for fsck hook > > It seems to me that git

Bug#923400: initramfs-tools: failure inside chroot: W: Couldn't identify type of root file system for fsck hook

2019-02-27 Thread Jonas Smedegaard
Package: initramfs-tools Version: 0.133 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Building a system image using multistrap, including generating an initial ramdisk, worked fine recently. Now it fails with this error message: W: Couldn't identify type of root file