# Boot failure after upgrade

**URL:** <https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [April 2, 2023, 9:21pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221 "2023-04-02T21:21:26Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 2, 2023, 9:21pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/1 "2023-04-02T21:21:26Z")

</div>

Since a few weeks boot sometimes fails after system upgrade with the output:

mount: /new\_root: no filesystem type specified.  
Your are now being dropped into an emergency shell.  
sh: can’t access tty; job control turned off  
[rootfs]#

Steps to reproduce:

1. Upgrade via pacman -Syu (see upgrade.jpeg)
2. Boot failure (see boot\_failure.jpeg)
3. Reboot in recovery mode
4. Reinstall linux via pacman -S linux (see fix.jpeg)
5. Regular reboot succeeds

 ![upgrade](https://forum.endeavouros.com/uploads/default/original/3X/e/c/ecc6d599602f78e0328f4b428796a8ff9fd1097c.jpeg)  
 ![boot_failure](https://forum.endeavouros.com/uploads/default/original/3X/1/1/1131191ae76c49febf64df0694fe1f50fb298102.jpeg)  
 ![fix](https://forum.endeavouros.com/uploads/default/original/3X/1/1/111debee661e67afa00b7478c5ddad815643dfbc.jpeg)

---

<div class="post-metadata">

**Author:** ![dalto](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/dalto/32/5577_2.png) [@dalto](https://forum.endeavouros.com/u/dalto)\
**Post date:** [April 2, 2023, 9:48pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/2 "2023-04-02T21:48:50Z")

</div>

To determine what went wrong, we would need to see the full output for the initial upgrade.

Ultimately, it sounds like something went wrong when rebuilding your initramfs.

By reinstalling `linux`, you are triggering the initramfs to be rebuilt.

---

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 2, 2023, 10:06pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/3 "2023-04-02T22:06:04Z")

</div>

Okay, I’ll save the stdout in the future and post it here in case anything goes wrong during reboot.

---

<div class="post-metadata">

**Author:** ![thefrog](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/thefrog/32/114250_2.png) [@thefrog](https://forum.endeavouros.com/u/thefrog)\
**Post date:** [April 2, 2023, 10:12pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/4 "2023-04-02T22:12:12Z")

</div>

I would try installing the kernel again your picture shows kernel 6.2.8 My update today gave me 6.2.9

 ![kernel](https://forum.endeavouros.com/uploads/default/original/3X/f/b/fb1c9173c913111071a563dbde034c121c9f74eb.jpeg)

---

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 2, 2023, 10:57pm UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/5 "2023-04-02T22:57:43Z")

</div>

I just upgraded successfully by entering _sudo pacman -Syu | tee pacman\_Syu.log_.

stdout:

```auto
:: Synchronizing package databases...
 endeavouros downloading...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (7) Old Version New Version Net Change Download Size

extra/fuse-common 3.14.0-1 3.14.1-1 0,00 MiB 0,00 MiB
extra/fuse3 3.14.0-1 3.14.1-1 0,00 MiB 0,12 MiB
core/gettext 0.21.1-4 0.21.1-5 0,00 MiB 1,78 MiB
core/linux-headers 6.2.8.arch1-1 6.2.9.arch1-1 0,00 MiB 29,22 MiB
extra/ndctl 76-1 76.1-1 0,00 MiB 0,35 MiB
core/texinfo 7.0.2-2 7.0.3-1 0,01 MiB 1,57 MiB
core/linux 6.2.8.arch1-1 6.2.9.arch1-1 -0,10 MiB 173,86 MiB

Total Download Size: 206,92 MiB
Total Installed Size: 350,19 MiB
Net Upgrade Size: -0,09 MiB

:: Retrieving packages...
 linux-6.2.9.arch1-1-x86_64 downloading...
 linux-headers-6.2.9.arch1-1-x86_64 downloading...
 gettext-0.21.1-5-x86_64 downloading...
 texinfo-7.0.3-1-x86_64 downloading...
 ndctl-76.1-1-x86_64 downloading...
 fuse3-3.14.1-1-x86_64 downloading...
 fuse-common-3.14.1-1-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Running pre-transaction hooks...
(1/2) Removing linux initcpios...
(2/2) Remove DKMS modules
==> dkms remove --no-depmod tuxedo-keyboard/3.2.1 -k 6.2.8-arch1-1
==> depmod 6.2.8-arch1-1
:: Processing package changes...
upgrading linux...
upgrading fuse-common...
upgrading fuse3...
upgrading gettext...
upgrading linux-headers...
upgrading ndctl...
upgrading texinfo...
New optional dependencies for texinfo
    perl-archive-zip: EPUB file output via texi2any
:: Running post-transaction hooks...
(1/9) Reloading system manager configuration...
(2/9) Reloading device manager configuration...
(3/9) Arming ConditionNeedsUpdate...
(4/9) Updating module dependencies...
(5/9) Install DKMS modules
==> dkms install --no-depmod tuxedo-keyboard/3.2.1 -k 6.2.9-arch1-1
==> depmod 6.2.9-arch1-1
(6/9) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img --microcode /boot/amd-ucode.img
==> Starting build: '6.2.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.2.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful
(7/9) Check if user should be informed about rebooting after certain system package upgrades.
==> INFO: Reboot is recommended due to the upgrade of core system package(s).
(8/9) Checking which packages need to be rebuilt
(9/9) Updating the info directory file...

```

I’ll keep you posted if the problem arises once more.

---

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 26, 2023, 6:46am UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/6 "2023-04-26T06:46:14Z")

</div>

Hi already thought the problem was fixed magically because it didn’t happen anymore in a while. But unfortunately it hit me again.

I updated my system using _pacman -Syu_:

```auto
:: Synchronizing package databases...
 endeavouros downloading...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Package (12) Old Version New Version Net Change Download Size

community/audacity 1:3.2.5-2 1:3.3.0-1 2,00 MiB 8,25 MiB
extra/babl 0.1.102-1 0.1.104-1 0,00 MiB 0,46 MiB
core/cracklib 2.9.8-1 2.9.11-1 0,01 MiB 0,27 MiB
core/device-mapper 2.03.20-1 2.03.21-1 0,00 MiB 0,27 MiB
extra/firefox 112.0.1-1 112.0.2-1 0,04 MiB 64,99 MiB
extra/git 2.40.0-1 2.40.1-1 0,26 MiB 6,65 MiB
extra/libadwaita 1:1.3.1-1 1:1.3.2-1 0,01 MiB 0,46 MiB
core/libpcap 1.10.3-1 1.10.4-1 0,00 MiB 0,28 MiB
core/lvm2 2.03.20-1 2.03.21-1 0,00 MiB 1,79 MiB
community/telegram-desktop 4.8.0-1 4.8.1-1 0,00 MiB 30,23 MiB
community/twolame 0.4.0-2 0.4.0-3 0,00 MiB 0,08 MiB
community/vamp-plugin-sdk 2.10.0-1 2.10.0-2 -0,17 MiB 0,24 MiB

Total Download Size: 113,96 MiB
Total Installed Size: 414,35 MiB
Net Upgrade Size: 2,15 MiB

:: Retrieving packages...
 firefox-112.0.2-1-x86_64 downloading...
 telegram-desktop-4.8.1-1-x86_64 downloading...
 audacity-1:3.3.0-1-x86_64 downloading...
 git-2.40.1-1-x86_64 downloading...
 lvm2-2.03.21-1-x86_64 downloading...
 babl-0.1.104-1-x86_64 downloading...
 libadwaita-1:1.3.2-1-x86_64 downloading...
 libpcap-1.10.4-1-x86_64 downloading...
 device-mapper-2.03.21-1-x86_64 downloading...
 cracklib-2.9.11-1-x86_64 downloading...
 vamp-plugin-sdk-2.10.0-2-x86_64 downloading...
 twolame-0.4.0-3-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
:: Processing package changes...
upgrading twolame...
upgrading vamp-plugin-sdk...
upgrading device-mapper...
upgrading libpcap...
upgrading audacity...
upgrading babl...
upgrading cracklib...
upgrading firefox...
upgrading git...
upgrading libadwaita...
upgrading lvm2...
upgrading telegram-desktop...
:: Running post-transaction hooks...
(1/9) Creating system user accounts...
(2/9) Reloading system manager configuration...
(3/9) Reloading device manager configuration...
(4/9) Arming ConditionNeedsUpdate...
(5/9) Updating the MIME type database...
(6/9) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
sort: cannot read: '/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.3/ep_84/uevent': No such file or directory
modprobe: ERROR: missing parameters. See -h.
  -> Running build hook: [modconf]
  -> Running build hook: [block]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful
(7/9) Updating icon theme caches...
(8/9) Checking which packages need to be rebuilt
(9/9) Updating the desktop file MIME type cache...

```

After the restart I saw the mount error stated in my first post again. It was something like this:

```auto
mount: /new_root: no filesystem type specified.
Your are now being dropped into an emergency shell.
sh: can’t access tty; job control turned off
[rootfs]#

```

So I restarted using old initramfs and reinstalled the kernel using _pacman -S linux_:

```auto
$ sudo pacman -S linux
warning: linux-6.2.12.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Package (1) Old Version New Version Net Change

core/linux 6.2.12.arch1-1 6.2.12.arch1-1 0,00 MiB

Total Installed Size: 174,24 MiB
Net Upgrade Size: 0,00 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring [------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) checking package integrity [------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) loading package files [------------------------------------------------------------------------------------------------------------------------------------------------] 100%
(1/1) checking for file conflicts [------------------------------------------------------------------------------------------------------------------------------------------------] 100%
:: Processing package changes...
(1/1) reinstalling linux [------------------------------------------------------------------------------------------------------------------------------------------------] 100%
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
  -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect --microcode /boot/amd-ucode.img
==> Starting build: '6.2.12-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_4xxx'
  -> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
==> Image generation successful
(4/5) Check if user should be informed about rebooting after certain system package upgrades.
(5/5) Checking which packages need to be rebuilt

```

This fixed the problem once again.

There is an error in the first log which might be the root of the problem:

```auto
sort: cannot read: '/sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-1/3-1.2/3-1.2.2/3-1.2.2:1.3/ep_84/uevent': No such file or directory
modprobe: ERROR: missing parameters. See -h.

```

---

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 26, 2023, 8:27am UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/7 "2023-04-26T08:27:23Z")

</div>

I found a similar [bug report](https://bugs.archlinux.org/task/77780). I’m using a docking station as well.

---

<div class="post-metadata">

**Author:** ![nevermind](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/n/53a042/32.png) [@nevermind](https://forum.endeavouros.com/u/nevermind)\
**Post date:** [April 26, 2023, 8:50am UTC](https://forum.endeavouros.com/t/boot-failure-after-upgrade/39221/8 "2023-04-26T08:50:22Z")

</div>

I commented the issue in the [archlinux forum](https://gitlab.archlinux.org/archlinux/mkinitcpio/mkinitcpio/-/issues/177) in the mkinitcpio section.
