Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #91760
| From | <pdormeau@free.fr> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory |
| Date | 2026-03-21 11:40 +0100 |
| Message-ID | <MB1Ul-9aHU-9@gated-at.bofh.it> (permalink) |
| References | <MAY0q-97ZG-5@gated-at.bofh.it> <MB17X-9a6K-1@gated-at.bofh.it> <MAY0q-97ZG-5@gated-at.bofh.it> <MB17X-9a6K-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
Le Sat, 21 Mar 2026 10:44:46 +0100, Benjamin Drung <bdrung@debian.org> a écrit : >Hi Pascal, > Hi Benjamin >Maybe the patch causes this failure as well. I am surprised that the >autopkgtest did not catch it. To ensure that there is no other reason >for the failure: Can you provide debug logs and describe your setup? > > The boot failure occurred before the root fs was mounted. Therefore no logs were saved. At the moment, I am quite reluctant booting again with an initramfs generated by dracut 110-6 because yesterday I spent a lot of time retrieving a functional boot. However, I quite convinced it is related to the systemd-gpt-auto-generator since I pass 'root=gpt-auto' as booting parameter and all fs partitions are discoverable (/, /boot as efi partition, encryted /home) I remember that the boot process stalled with something related to the some systemd generator process (sorry I do not remember exactly). To retrieve a functional boot, I had to : - boot in SystemRescueCd, - run Debian in a chroot, - reinstall dracut-* pakage in 110-5 version, but it was not enough: - change the boot parameters 'root=UUID=....', - recreate the fstab file, - rebuild the initramfs with 110-5 version Without cancelling the discoverable part I could not boot again. Once I could boot again into Debian, I could revert back to 'root=gpt-auto' and the system can now boot normally with dracut 110-5 and systemd-gpt-auto-generator with discoverable partitions. If I did not provide enough clues, I can still try to boot with dracut 110-6 to get some logs if you insist (now that I know the recipe to retrieve a functional boot). Best regards Pascal D
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory pdormeau@free.fr - 2026-03-21 07:30 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory Benjamin Drung <bdrung@debian.org> - 2026-03-21 10:50 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory Simon Pilkington <simonp.git@mailbox.org> - 2026-03-21 11:40 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory <pdormeau@free.fr> - 2026-03-21 14:00 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory Simon Pilkington <simonp.git@mailbox.org> - 2026-03-21 14:30 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory <pdormeau@free.fr> - 2026-03-21 15:20 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory <pdormeau@free.fr> - 2026-03-21 11:40 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory Benjamin Drung <bdrung@debian.org> - 2026-03-21 22:40 +0100
Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory Simon Pilkington <simonp.git@mailbox.org> - 2026-03-22 05:20 +0100
Bug#1131416: marked as done (dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-21 23:00 +0100
csiph-web