Bug#918322: initramfs-tools: kernel fails to boot with "Gave up waiting for root file system device"

Axel Ludszuweit axel.ludszuweit at icloud.com
Sat Jan 5 21:09:22 GMT 2019


On Sat, 5 Jan 2019 21:41:35 +0100 Michael Biebl wrote:
> Hi Axel!
> 
> Am 05.01.19 um 21:33 schrieb Axel Ludszuweit:
> > I have read bug 
> > 
> > #917607: udev240 makes system unbootable; rootfs not found
> > 
> > Because my working and failing initrd files contain different udev versions, the failing one udev240, it may be possible, that this is the cause of failed boot.
> > Bug #917607 description sounds very similar to behaviour of this bug.
> 
> Are you willing to test the packages from
> 
> https://people.debian.org/~biebl/systemd/buster/
> 
> and report back with the results?
> 
> If the 240-3 packages do not help and you are dropped into the initramfs
> rescue shell can you run
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
> 
> and then check if any modules are loaded
> 
> Regards,
> Michael
> 

Hello Michael,

yes, I am willing to try your package tomorrow, but I have the following questions:
- in the initramfs rescue shell the keyboard doesn‘t work, therefore I can run your suggested commands
- I must boot with the 4.18 initrd version. Installation of  your package via apt triggers creation of new 4.18 initrd image and could make my system complete unbootable. Can I do the following steps to keep a bootable system:
- boot into 4.18
- save bootable 4.18 initrd image
- install your package
- create initrd image for 4.19 via update-initram command
- replaced modified 4.18 initrd image by the saved one
- try to boot into 4.19

Does installation of  your package via dpkg trigger also creation of new initrd image?
What is the syntax, to reinstall udev 240-2, if your package does not work?



More information about the Pkg-systemd-maintainers mailing list