Hello, I’ve switched recently to Arch and installed EOS two days ago, but unfortunately I had a problem today when booting, stating “A start job is running for dracut-initqueue-hook”, the boot slows down because it waits for “dracut-initqueue-hook” to do what it needs to do and so my boot takes like 2+ minutes more than it should. Any help?
Things I tried:
Rebuilding dracut with the terminal
Reinstalling dracut
Welcome to the forum!
Usually that is caused by some device being unresponsive at boot.
Can you share inxi -Fxxxz
Yes, and thank you for the welcome!
**System:**
**Kernel:** 6.17.5-arch1-1 **arch:** x86_64 **bits:** 64 **compiler:** gcc **v:** 15.2.1
**clocksource:** tsc
**Desktop:** KDE Plasma **v:** 6.5.1 **tk:** Qt **v:** N/A **wm:** kwin_wayland **vt:** 1 **dm:** SDDM
**Distro:** EndeavourOS **base:** Arch Linux
**Machine:**
**Type:** Desktop **Mobo:** ASUSTeK **model:** PRIME Z270-A **v:** Rev 1.xx
**serial:** <superuser required> **part-nu:** SKU **uuid:** <superuser required>
**UEFI:** American Megatrends **v:** 1302 **date:** 03/15/2018
**CPU:**
**Info:** quad core **model:** Intel Core i7-6700K **bits:** 64 **type:** MT MCP
**smt:** enabled **arch:** Skylake-S **rev:** 3 **cache:** **L1:** 256 KiB **L2:** 1024 KiB
**L3:** 8 MiB
**Speed (MHz):** **avg:** 800 **min/max:** 800/4200 **cores:** **1:** 800 **2:** 800 **3:** 800 **4:** 800
**5:** 800 **6:** 800 **7:** 800 **8:** 800 **bogomips:** 63999
**Flags-basic:** avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
**Graphics:**
**Device-1:** NVIDIA GP107 \[GeForce GTX 1050 Ti\] **vendor:** ASUSTeK **driver:** nvidia
**v:** 580.95.05 **arch:** Pascal **pcie:** **speed:** 8 GT/s **lanes:** 16 **ports:**
**active:** HDMI-A-1 **empty:** DP-1,DVI-D-1 **bus-ID:** 01:00.0 **chip-ID:** 10de:1c82
**class-ID:** 0300
**Display:** wayland **server:** X.org **v:** 1.21.1.20 **with:** Xwayland **v:** 24.1.9
**compositor:** kwin_wayland **driver:** **X:** **loaded:** nvidia **unloaded:** modesetting
**alternate:** fbdev,nouveau,nv,vesa **gpu:** nvidia,nvidia-nvswitch **display-ID:** 0
**Monitor-1:** HDMI-A-1 **model:** LG (GoldStar) IPS234 **res:** **mode:** 1920x1080
**hz:** 60 **scale:** 100% (1) **dpi:** 96 **size:** 510x290mm (20.08x11.42")
**diag:** 587mm (23.1") **modes:** **max:** 1920x1080 **min:** 640x480
**API:** EGL **v:** 1.5 **hw:** **drv:** nvidia **platforms:** **device:** 0 **drv:** nvidia **device:** 2
**drv:** swrast **gbm:** **drv:** nvidia **surfaceless:** **drv:** nvidia **wayland:** **drv:** nvidia
**x11:** **drv:** nvidia **inactive:** device-1
**API:** OpenGL **v:** 4.6.0 **compat-v:** 4.5 **vendor:** nvidia mesa **v:** 580.95.05
**glx-v:** 1.4 **direct-render:** yes **renderer:** NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2
**display-ID:** :1.0
**API:** Vulkan **v:** 1.4.328 **layers:** 6 **surfaces:** N/A **device:** 0
**type:** discrete-gpu **driver:** nvidia **device-ID:** 10de:1c82
**Info:** **Tools:** **api:** clinfo, eglinfo, glxinfo, vulkaninfo
**de:** kscreen-console,kscreen-doctor **gpu:** nvidia-settings,nvidia-smi
**wl:** wayland-info **x11:** xdpyinfo, xprop, xrandr
**Audio:**
**Device-1:** Intel 200 Series PCH HD Audio **vendor:** ASUSTeK
**driver:** snd_hda_intel **v:** kernel **bus-ID:** 00:1f.3 **chip-ID:** 8086:a2f0
**class-ID:** 0403
**Device-2:** NVIDIA GP107GL High Definition Audio **vendor:** ASUSTeK
**driver:** snd_hda_intel **v:** kernel **pcie:** **speed:** 8 GT/s **lanes:** 16
**bus-ID:** 01:00.1 **chip-ID:** 10de:0fb9 **class-ID:** 0403
**API:** ALSA **v:** k6.17.5-arch1-1 **status:** kernel-api
**Server-1:** PipeWire **v:** 1.4.9 **status:** active **with:** **1:** pipewire-pulse
**status:** active **2:** wireplumber **status:** active **3:** pipewire-alsa **type:** plugin
**4:** pw-jack **type:** plugin
**Network:**
**Device-1:** Intel Ethernet I219-V **vendor:** ASUSTeK **driver:** e1000e **v:** kernel
**port:** N/A **bus-ID:** 00:1f.6 **chip-ID:** 8086:15b8 **class-ID:** 0200
**IF:** enp0s31f6 **state:** up **speed:** 1000 Mbps **duplex:** full **mac:** <filter>
**Drives:**
**Local Storage:** **total:** 927.43 GiB **used:** 96.39 GiB (10.4%)
**ID-1:** /dev/sda **vendor:** Kingston **model:** SA400S37480G **size:** 447.13 GiB
**speed:** 6.0 Gb/s **tech:** SSD **serial:** <filter> **fw-rev:** 1103 **scheme:** GPT
**ID-2:** /dev/sdb **vendor:** Seagate **model:** ST500DM002-1BD142 **size:** 465.76 GiB
**speed:** 6.0 Gb/s **tech:** HDD **rpm:** 7200 **serial:** <filter> **fw-rev:** KC65
**scheme:** MBR
**ID-3:** /dev/sdc **vendor:** Kingston **model:** DataTraveler 2.0 **size:** 14.54 GiB
**type:** USB **rev:** 2.0 **spd:** 480 Mb/s **lanes:** 1 **tech:** N/A **serial:** <filter>
**fw-rev:** PMAP **scheme:** MBR
**Partition:**
**ID-1:** / **size:** 428.41 GiB **used:** 95.93 GiB (22.4%) **fs:** ext4 **dev:** /dev/sda2
**Swap:**
**ID-1:** swap-1 **type:** partition **size:** 8.8 GiB **used:** 0 KiB (0.0%) **priority:** -2
**dev:** /dev/sda3
**Sensors:**
**System Temperatures:** **cpu:** 32.0 C **mobo:** N/A
**Fan Speeds (rpm):** N/A
**Info:**
**Memory:** **total:** 16 GiB **available:** 15.55 GiB **used:** 3.06 GiB (19.7%)
**Processes:** 252 **Power:** **uptime:** 55m **states:** freeze,mem,disk **suspend:** deep
**wakeups:** 0 **hibernate:** platform **Init:** systemd **v:** 258 **default:** graphical
**Packages:** 1203 **pm:** pacman **pkgs:** 1184 **pm:** flatpak **pkgs:** 19 **Compilers:**
**gcc:** 15.2.1 **Shell:** Bash **v:** 5.3.3 **running-in:** konsole **inxi:** 3.3.39
Is it faster if you boot without the thumb drive connected?
No, unfortunately nothing changes, still happens, also forgot to take it out when printing inxi, I usually never have it on when booting
I’m having the same issue. Running systemd-analyze blame showed it took more than a minute to finish running dracut-initqueue:
1min 5.754s dracut-initqueue.service
running dmesg showed:
[ 6.794576] usb 1-11: new high-speed USB device number 16 using xhci_hcd
[ 12.033614] usb 1-11: device descriptor read/64, error -110
[ 27.905658] usb 1-11: device descriptor read/64, error -110
[ 28.195602] usb 1-11: new high-speed USB device number 17 using xhci_hcd
[ 33.537625] usb 1-11: device descriptor read/64, error -110
[ 49.410759] usb 1-11: device descriptor read/64, error -110
[ 49.526383] usb usb1-port11: attempt power cycle
[ 49.967683] usb 1-11: new high-speed USB device number 18 using xhci_hcd
[ 54.767898] usb 1-11: Device not responding to setup address.
[ 59.780791] usb 1-11: Device not responding to setup address.
[ 59.996528] usb 1-11: device not accepting address 18, error -71
[ 60.179568] usb 1-11: new high-speed USB device number 19 using xhci_hcd
[ 64.979778] usb 1-11: Device not responding to setup address.
[ 69.996763] usb 1-11: Device not responding to setup address.
[ 70.212569] usb 1-11: device not accepting address 19, error -71
[ 70.222300] usb usb1-port11: unable to enumerate USB device
Same result here for systemd-analyze blame, which shows:
1min 3.536s dracut-initqueue.service
And same result also for dmesg, which shows:
[ 6.827386] usb 1-10: device descriptor read/64, error -110
[ 22.699498] usb 1-10: device descriptor read/64, error -110
[ 22.915358] usb 1-10: new high-speed USB device number 5 using xhci_hcd
[ 28.331473] usb 1-10: device descriptor read/64, error -110
[ 44.203434] usb 1-10: device descriptor read/64, error -110
[ 44.307532] usb usb1-port10: attempt power cycle
[ 44.686331] usb 1-10: new high-speed USB device number 6 using xhci_hcd
[ 49.723456] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 55.355458] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 55.563342] usb 1-10: device not accepting address 6, error -62
[ 55.675363] usb 1-10: new high-speed USB device number 7 using xhci_hcd
[ 60.987391] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 66.619473] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 66.827349] usb 1-10: device not accepting address 7, error -62
[ 66.827542] usb usb1-port10: unable to enumerate USB device
I unplugged everything, hoping I could identify “bad” USB devices, but surprisingly, I had the same error. This might be related to USB controllers themselves or the motherboard; I have no clue.
It looks like downgrading the kernel worked for this user: