Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #91755 > unrolled thread

Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory

Back to article view | Back to linux.debian.kernel

Contents

  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

#91755 — Bug#1131416: dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory

Package: dracut
Version: 110-6
Severity: important

Dear Maintainer,

Building the initramfs fails after updating dracut from 110-5 to 110-6 version
or after trying to force rebuild the initramfs (sudo dracut -H --force)
I obtain the following error message:
/usr/lib/dracut/modules.d/80base/dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory
And the boot also fails with the generated initramfs

110-5 version is ok.

Best regards 
Pascal D

-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.19.8+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dracut depends on:
ii  dracut-core  110-6
ii  linux-base   4.15

dracut recommends no packages.

Versions of packages dracut suggests:
pn  dracut-network  <none>

-- no debconf information

[toc] | [next] | [standalone]

#91757

Hi Pascal,

thanks for the report.

On Sat, 2026-03-21 at 07:18 +0100, pdormeau@free.fr wrote:
> Package: dracut
> Version: 110-6
> Severity: important
> 
> Dear Maintainer,
> 
> Building the initramfs fails after updating dracut from 110-5 to 110-6 version
> or after trying to force rebuild the initramfs (sudo dracut -H --force)
> I obtain the following error message:
> /usr/lib/dracut/modules.d/80base/dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory

This is a warning and I know which patch caused this: the first version
of https://github.com/dracut-ng/dracut-ng/pull/2310 which should be
fixed by the second version of it.

> And the boot also fails with the generated initramfs

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?


-- 
Benjamin Drung
Debian & Ubuntu Developer

[toc] | [prev] | [next] | [standalone]

#91759

Hi Benjamin,

On 21/03/2026 10:44, Benjamin Drung wrote:
> Hi Pascal, > > thanks for the report. > > On Sat, 2026-03-21 at 07:18 +0100, pdormeau@free.fr wrote: >> Package: dracut Version: 110-6 Severity: important >> >> Dear Maintainer, >> >> Building the initramfs fails after updating dracut from 110-5 to >> 110-6 version or after trying to force rebuild the initramfs (sudo >> dracut -H --force) I obtain the following error message: /usr/lib/ >> dracut/modules.d/80base/dracut-dev-lib.sh: line 128: /sbin/ >> initqueue: No such file or directory > > This is a warning and I know which patch caused this: the first > version of https://github.com/dracut-ng/dracut-ng/pull/2310 which > should be fixed by the second version of it. > >> And the boot also fails with the generated initramfs > > 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?
I can reproduce this as described by Pascal in a test VM that I use before
installing new kernels or dracut on my host. The boot doesn't fail but it
hangs on a systemd .device node in the initramfs. Once this times out boot
succeeds. Perhaps this is why tests didn't catch it.

Like Pascal said, 110-5 is good, 110-6 bad.

> > Regards, Simon

[toc] | [prev] | [next] | [standalone]

#91761

Le Sat, 21 Mar 2026 11:26:41 +0100,
Simon Pilkington <simonp.git@mailbox.org> a écrit :

Hi Simon

>before installing new kernels or dracut on my host. The boot doesn't
>fail but it hangs on a systemd .device node in the initramfs. Once
>this times out boot succeeds. 
not by itself here. I got the emergency prompt :
"enter the root password for maintenance mode or ctrl-D to continue"
But I did not try ctrl-D because I believed it would not go further
given that the error message was related to some file system stuff. 

[toc] | [prev] | [next] | [standalone]

#91762

Hi Pascal,

On 21/03/2026 13:54, pdormeau@free.fr wrote:
> Le Sat, 21 Mar 2026 11:26:41 +0100,
> Simon Pilkington <simonp.git@mailbox.org> a écrit :
> 
> Hi Simon
> 
>> before installing new kernels or dracut on my host. The boot doesn't
>> fail but it hangs on a systemd .device node in the initramfs. Once
>> this times out boot succeeds. 
> not by itself here. I got the emergency prompt :
> "enter the root password for maintenance mode or ctrl-D to continue"
> But I did not try ctrl-D because I believed it would not go further
> given that the error message was related to some file system stuff. 

It seems like something else fails in your case then but for me reverting
fix-base-move-initrd.target.wants-symlink-creation-to-wai.patch which was
added in 110-6 produces working initramfses again. You can test this if
you're comfortable.

Regards,
Simon

PS Sorry about the garbage formatting in my previous message.

[toc] | [prev] | [next] | [standalone]

#91763

Le Sat, 21 Mar 2026 14:27:49 +0100,
Simon Pilkington <simonp.git@mailbox.org> a écrit :

Hi Simon 

>reverting
>fix-base-move-initrd.target.wants-symlink-creation-to-wai.patch which
>was added in 110-6 produces working initramfses again. You can test
>this if you're comfortable.

I confirm that after reverting the mentioned patch I can boot as
expected. Thanks
Best regards,
Pascal D

[toc] | [prev] | [next] | [standalone]

#91760

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

[toc] | [prev] | [next] | [standalone]

#91764

Hi,

On Sat, 2026-03-21 at 11:28 +0100, pdormeau@free.fr wrote:
> 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)

Thanks. That explanation should allow me to write a test case for it (to
catch those issue next time).

I just uploaded 110-7 with the updated patch from
https://github.com/dracut-ng/dracut-ng/pull/2310
I assume that this will fix the issues you saw. If not, let me know.

-- 
Benjamin Drung
Debian & Ubuntu Developer

[toc] | [prev] | [next] | [standalone]

#91768

Hi Benjamin,

On 21/03/2026 22:34, Benjamin Drung wrote:
> I just uploaded 110-7 with the updated patch from
> https://github.com/dracut-ng/dracut-ng/pull/2310
> I assume that this will fix the issues you saw. If not, let me know.
 
110-7 seems good here. (boots fine, no more /sbin/initqueue error)

Thanks,
Simon

[toc] | [prev] | [next] | [standalone]

#91767 — Bug#1131416: marked as done (dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 21 Mar 2026 21:48:44 +0000
with message-id <E1w44BY-00000004a3H-0R7n@fasolo.debian.org>
and subject line Bug#1131416: fixed in dracut 110-7
has caused the Debian Bug report #1131416,
regarding dracut-dev-lib.sh: line 128: /sbin/initqueue: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1131416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1131416
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web