Arch Linux

wideroger

Member

Registered: 2023-04-19

Posts: 21

[SOLVED] Unable to boot after crash mid update.

A couple days ago I was working on uni stuff on my laptop at a friends house, when suddenly it crashed mid update. It didn't run out of battery or anything sice it was plugged in.

After restarting it I got this message:

error: file '/boot/vmlinuz-linux' not found.
Loading initial ramdisk ...
error: you need to load the kernel first.

Following this post
https://bbs.archlinux.org/viewtopic.php?id=217104
I booted arch from a USB drive my frend lent me mounted the partitions and arch-chrooted and I ran

pacman -S linux

I had to remove the db.lck file sine it crashed mid update.
After trying to boot again it seemed like it was working until I got this error message

ERROR: device 'UUID=e2a...2d' not found. Skipping fsck.
ERROR: Failed to mount 'UUID=e2a...2d' on real root
mount: /new_root: can't find UUID=e2a...2d.
You are being dropped into an emergency shell
sh: can't access tty; job control turned off
[rootfs /]# _

I found this forum post https://bbs.archlinux.org/viewtopic.php?id=167109
arch-chrooted again and ran

mkinitcpio -p linux

but I think it didn't do much since I'm assuming mkinitcpio executed when I reinstalled the linux package

Last edited by wideroger (2024-05-07 13:12:16)

Wild Penguin

Member

Registered: 2015-03-19

Posts: 399

Re: [SOLVED] Unable to boot after crash mid update.

When you run

pacman -S linux

(or install any other linux image) or run mkinitcpio, you need to make sure you have your /boot partition (if any) mounted. From the looks of it, this could explain why tour commands "didn't work".

Post your /etc/fstab contents and outputs of lsblk and blkid(run as root) here. You can run these from a live Arch medium, in case you can not boot into the Arch installation (but make sure you post the correct /etc/fstab, not  the one on the installation medium).

FWIW at this point:

ERROR: device 'UUID=e2a...2d' not found. Skipping fsck.
ERROR: Failed to mount 'UUID=e2a...2d' on real root
mount: /new_root: can't find UUID=e2a...2d.
You are being dropped into an emergency shell
sh: can't access tty; job control turned off
[rootfs /]# _

You could mount the real root manually in /new_root, and then drop out of the emergency shell to resume the boot.

I'd recommend reading up on Linux filesystems, block devices and mounting basics from somewhere. This will make life easier later on on a very barebones, non-beginner-friendly distribution like Arch (by posting the output I've asked above, someone can walk you trough / tell the correct steps for fixing your boot).

For example, Arch boot setup is in an inconsistent state for a long time on every update if updating the Kernel is involved, which is not the case on many other less-barebones distributions. If the update is interrupted for any reason, manual fixing will be needed. Many distributions will make sure there is always a fail-safe way to boot even if an update is interrupted (but Arch is not one of them).

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

I did mount the boot partition when running

pacman -S linux

and when running mkinitcpio as well

and the keyboard doesn't work on the emergency shell.

this is the /etc/fstab file

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p3
UUID=e2af9e0f-6be7-42cc-934b-ae619973bf2d	/         	ext4      	rw,relatime,stripe=32	0 1

# /dev/nvme0n1p1
UUID=920A-8036      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p2
UUID=be75aef0-461f-4a49-bc82-ebf410563984	none      	swap      	defaults  	0 0

This is the lsblk output

NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0 788.9M  1 loop 
sda           8:0    1  28.6G  0 disk 
└─sda1        8:1    1  28.6G  0 part 
nvme0n1     259:0    0 476.9G  0 disk 
├─nvme0n1p1 259:1    0     1G  0 part /boot
├─nvme0n1p2 259:2    0     8G  0 part [SWAP]
└─nvme0n1p3 259:3    0 467.9G  0 part /

and finally this is the blkid output

/dev/nvme0n1p3: UUID="e2af9e0f-6be7-42cc-934b-ae619973bf2d" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="560d9e5e-a683-824d-ab86-15a15eb88d98"
/dev/nvme0n1p1: UUID="920A-8036" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="2b725361-84f7-c14d-a6f8-fc1d756bb295"
/dev/nvme0n1p2: UUID="be75aef0-461f-4a49-bc82-ebf410563984" TYPE="swap" PARTUUID="8ccf487e-4119-204e-8ea1-80d602fe310d"
/dev/loop0: BLOCK_SIZE="1048576" TYPE="squashfs"
/dev/sda1: LABEL="ARCH_202405" UUID="AA49-0D95" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="10c00e8d-01"

And I'll definitely read up on those topics, I started using arch because I wanted to understand how Linux works better, thanks!!

Last edited by wideroger (2024-05-06 20:29:40)

Head_on_a_Stick

Member

From: The Wirral

Registered: 2014-02-20

Posts: 9,003

Website

Re: [SOLVED] Unable to boot after crash mid update.

Check /dev/nvme0n1p3 & /dev/nvme0n1p1 for filesystem corruption.

The `file` command can be used to check the vmlinuz-linux version in the /boot/ partition, it should match the directory listed in /lib/modules/.

---

Jin, Jîyan, Azadî

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,997

Re: [SOLVED] Unable to boot after crash mid update.

Also check the package integrity

LC_ALL=C pacman --root=/mnt -Qkk | grep -v ', 0 altered files' > /tmp/howbadisit.txt
cat /tmp/howbadisit.txt | curl -F 'file=@-' 0x0.st

If you can chroot and use the pacman of the installed system, skip the "--root=/mnt" part.

Relevant ALPM hooks might simply fail if your system is sufficiently trashed.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

This is the output for fsck /dev/nvme0n1p3

fsck from util-linux 2.40
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p3 clean: 1470195/30670848 files, 53512544/122667264 blocks

fsck /dev/nvme0n1p1 gives me this prompt

fsck from util-linux 2.40
fsck.fat 4.2 (2021-01-31)
There are differences between boot sector and its backup.
This is mostly harmless. Differences: (offset:original/backup)
  65:01/00
1) Copy original to backup
2) Copy backup to original
3) No action
[123?q]?

I'm not sure how to procede and since I don't want to fuck it up i just quited.

then after mounting the partitions and chrooting this is the output for file /boot/vmlinuz-linux | grep version

/boot/vmlinuz-linux: Linux kernel x86 boot executable bzImage, version 6.8.9-arch1-1 (linux@archlinux) #1 SMP PREEMPT_DYNAMIC Thu, 02 May 2024 17:49:46 +0000, RO-rootFS, swap_dev 0XC, Normal VGA

and this is the output for ls /lib/modules/

6.8.8-arch1-1
6.8.9-arch1-1

so the vesions match

Last edited by wideroger (2024-05-06 21:19:19)

loqs

Member

Registered: 2014-03-06

Posts: 18,916

Re: [SOLVED] Unable to boot after crash mid update.

and this is the output for ls /lib/modules/

6.8.8-arch1-1
6.8.9-arch1-1

so the vesions match

What owns /usr/lib/modules/6.8.8-arch1-1? Please provide the output from the package integrity check seth requested.

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

I can chroot
Here's the howbadisit.txt output https://0x0.st/X8-3.txt/
Sorry I posted befor seeing seth's post!

Last edited by wideroger (2024-05-06 21:38:16)

loqs

Member

Registered: 2014-03-06

Posts: 18,916

Re: [SOLVED] Unable to boot after crash mid update.

Reinstall all the packages that have no mtree first with --dbonly then without

firefox: no mtree file
glslang: no mtree file
gtk-update-icon-cache: no mtree file
hwdata: no mtree file
libelf: no mtree file
libvpl: no mtree file
llvm-libs: no mtree file
mpg123: no mtree file
sdl2: no mtree file
shaderc: no mtree file
spirv-tools: no mtree file
systemd: no mtree file
tracker3: no mtree file

# pacman -S  --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3
# pacman -S  firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,997

Re: [SOLVED] Unable to boot after crash mid update.

There's the pending fsck.
Also according to

error: file '/boot/vmlinuz-linux' not found.

you're booting from the root partition, nvme0n1p3 - not nvme0n1p1
Are there files in the /mnt/boot mountpoint before mounting nvme0n1p1 there?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

What owns /usr/lib/modules/6.8.8-arch1-1?

I don't know what you mean by this, do you mean file ownership? root owns it. here's the output for ls -l  /usr/lib/modules

total 8
drwxr-xr-x 3 root root 4096 May  5 16:08 6.8.8-arch1-1
drwxr-xr-x 3 root root 4096 May  5 16:41 6.8.9-arch1-1

Here's the output for

pacman -S  --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

warning: firefox-125.0.3-2 is up to date -- reinstalling
warning: glslang-14.1.0-1 is up to date -- reinstalling
warning: gtk-update-icon-cache-1:4.14.4-1 is up to date -- reinstalling
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: libvpl-2.11.0-1 is up to date -- reinstalling
warning: llvm-libs-17.0.6-4 is up to date -- reinstalling
warning: mpg123-1.32.6-1 is up to date -- reinstalling
warning: sdl2-2.30.3-1 is up to date -- reinstalling
warning: shaderc-2024.0-1 is up to date -- reinstalling
warning: spirv-tools-2024.1-1 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
error: target not found: tracker3

and here's the output for

pacman -S firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

warning: firefox-125.0.3-2 is up to date -- reinstalling
warning: glslang-14.1.0-1 is up to date -- reinstalling
warning: gtk-update-icon-cache-1:4.14.4-1 is up to date -- reinstalling
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: libvpl-2.11.0-1 is up to date -- reinstalling
warning: llvm-libs-17.0.6-4 is up to date -- reinstalling
warning: mpg123-1.32.6-1 is up to date -- reinstalling
warning: sdl2-2.30.3-1 is up to date -- reinstalling
warning: shaderc-2024.0-1 is up to date -- reinstalling
warning: spirv-tools-2024.1-1 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
warning: tracker3-3.7.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
warning: could not fully load metadata for package firefox-125.0.3-2
error: failed to prepare transaction (invalid or corrupted package)

The error

error: file '/boot/vmlinuz-linux' not found.

doesn't happen anymore since I ran

pacman -S linux

It puts me on the emergency shell so I think vmlinuz-linux is not a problem
There are no files in /mnt/boot before mounting nvme0n1p1

There's the pending fsck.

I am not sure on what option I shoud choose or what shoud I do in general since I've never run fsck before I'd be great if you could provide some guidance.

Last edited by wideroger (2024-05-06 22:19:12)

loqs

Member

Registered: 2014-03-06

Posts: 18,916

Re: [SOLVED] Unable to boot after crash mid update.

error: could not open file /var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
warning: could not fully load metadata for package firefox-125.0.3-2
error: failed to prepare transaction (invalid or corrupted package)

So the packages with missing mtrees have not been reinstalled?

What is the output of

pacman -Qo /usr/lib/modules/6.8.8-arch1-1/
find /usr/lib/modules/6.8.8-arch1-1/

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,997

Re: [SOLVED] Unable to boot after crash mid update.

I am not sure on what option I shoud choose or what shoud I do in general since I've never run fsck before.

It proably really doesn't matter which superblock you choose. Make the original the backup and then sure there're no further errors.

The first run already failed because of

error: target not found: tracker3

Which however should be https://archlinux.org/packages/extra/x86_64/tracker3/
Assuming the extra database is broken, does

pacman -Sy  --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

work?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

This is the output for

pacman -Qo /usr/lib/modules/6.8.8-arch1-1/
find /usr/lib/modules/6.8.8-arch1-1/

error: could not open file /var/lib/pacman/local/firefox-125.0.3-2/files: No such file or directory
error: No package owns /usr/lib/modules/6.8.8-arch1-1/
/usr/lib/modules/6.8.8-arch1-1/
/usr/lib/modules/6.8.8-arch1-1/extramodules
/usr/lib/modules/6.8.8-arch1-1/extramodules/nvidia-drm.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/vboxnetflt.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/vboxdrv.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/nvidia.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/nvidia-peermem.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/vboxnetadp.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/nvidia-modeset.ko.xz
/usr/lib/modules/6.8.8-arch1-1/extramodules/nvidia-uvm.ko.xz

and this is the putput for

pacman -Sy  --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

:: Synchronizing package databases...
 core downloading...
 extra downloading...
 community downloading...
 multilib downloading...
warning: firefox-125.0.3-2 is up to date -- reinstalling
warning: glslang-14.1.0-1 is up to date -- reinstalling
warning: gtk-update-icon-cache-1:4.14.4-1 is up to date -- reinstalling
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: libvpl-2.11.0-1 is up to date -- reinstalling
warning: llvm-libs-17.0.6-4 is up to date -- reinstalling
warning: mpg123-1.32.6-1 is up to date -- reinstalling
warning: sdl2-2.30.3-1 is up to date -- reinstalling
warning: shaderc-2024.0-1 is up to date -- reinstalling
warning: spirv-tools-2024.1-1 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
error: target not found: tracker3

After exiting chroot and unmounting I made the original the backup as you said end this is the output for fsck /dev/nvme0n1p1 now

fsck from util-linux 2.40
fsck.fat 4.2 (2021-01-31)
/dev/nvme0n1p1: 368 files, 51963/261628 clusters

shoud I try booting normaly now?

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

Ok so I tried booting normally and I still get the emergency shell

loqs

Member

Registered: 2014-03-06

Posts: 18,916

Re: [SOLVED] Unable to boot after crash mid update.

What is the current error that triggers the emergency shell?  From the emergency shell what if you try:

# pacman -S tracker3

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,997

Re: [SOLVED] Unable to boot after crash mid update.

Next to the tracker situation, boot the iso, do *not* chroot, mount /dev/nvme0n1p3 into /mnt, /dev/nvme0n1p1 into /mnt/boot

pacman -Sy  --root /mnt --cachedir /mnt/var/cache/pacman/pkg --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3 # sanitize
pacman -S    --root /mnt --cachedir /mnt/var/cache/pacman/pkg firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd  tracker3 # re-install
pacman -S   --root /mnt --cachedir /mnt/var/cache/pacman/pkg linux # re-install kernel to hopefully fix the initramfs

If at any point you're getting "error: target not found: tracker3" again, just remove that from the list and run the commands w/o it - otherwise you're not updating anything and libelf and systemd are in that list. It's more important to fix those and then we can start to focus on why tracker3 cannot be resolved.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

What is the current error that triggers the emergency shell?  From the emergency shell what if you try:

# pacman -S tracker3

This is still the error

After trying to boot again it seemed like it was working until I got this error message

ERROR: device 'UUID=e2a...2d' not found. Skipping fsck.
ERROR: Failed to mount 'UUID=e2a...2d' on real root
mount: /new_root: can't find UUID=e2a...2d.
You are being dropped into an emergency shell
sh: can't access tty; job control turned off
[rootfs /]# _

And I can't type or use the keyboard at all on the emergency shell so I can't try

# pacman -S tracker3

there

And here's the output for

pacman -Sy  --root /mnt --cachedir /mnt/var/cache/pacman/pkg --dbonly firefox glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

:: Synchronizing package databases...
 core downloading...
 extra downloading...
warning: firefox-125.0.3-2 is up to date -- reinstalling
warning: glslang-14.1.0-1 is up to date -- reinstalling
warning: gtk-update-icon-cache-1:4.14.4-1 is up to date -- reinstalling
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: libvpl-2.11.0-1 is up to date -- reinstalling
warning: llvm-libs-17.0.6-4 is up to date -- reinstalling
warning: mpg123-1.32.6-1 is up to date -- reinstalling
warning: sdl2-2.30.3-1 is up to date -- reinstalling
warning: shaderc-2024.0-1 is up to date -- reinstalling
warning: spirv-tools-2024.1-1 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
warning: tracker3-3.7.3-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
error: could not open file /mnt/var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
warning: could not fully load metadata for package firefox-125.0.3-2
error: failed to prepare transaction (invalid or corrupted package)

good news (i guess) tracker3 doesn't fail but it throws another error I haven't run the other two commands since this one failed already

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

I tried without firefox just in case, so I re ran

pacman -Sy  --root /mnt --cachedir /mnt/var/cache/pacman/pkg --dbonly glslang gtk-update-icon-cache hwdata libelf libvpl llvm-libs mpg123 sdl2 shaderc spirv-tools systemd tracker3

and this is the output

:: Synchronizing package databases...
 core downloading...
 extra downloading...
error: could not parse package description file 'haskell-http-conduit-2.3.8.3-50/desc' from db 'extra'
error: target not found: glslang
error: target not found: gtk-update-icon-cache
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
error: target not found: libvpl
error: target not found: llvm-libs
error: target not found: mpg123
error: target not found: sdl2
error: target not found: shaderc
error: target not found: spirv-tools
warning: systemd-255.5-4 is up to date -- reinstalling
error: target not found: tracker3

Last edited by wideroger (2024-05-07 09:19:08)

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

I'm sorry guys but if I'm not able to fix this today I'll just reinstall arch from 0 since I need the laptop to work on uni stuff. I already made a backup of all the important files I have on the laptop

Last edited by wideroger (2024-05-07 09:37:41)

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

I tried doing only

pacman -Sy  --root /mnt --cachedir /mnt/var/cache/pacman/pkg --dbonly hwdata libelf systemd 

 :: Synchronizing package databases...
 core downloading...
 extra downloading...
warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
resolving dependencies...
error: could not open file /mnt/var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
looking for conflicting packages...

Packages (3) hwdata-0.382-1  libelf-0.191-2  systemd-255.5-4

Total Installed Size:  42.81 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] checking keyring...
checking package integrity...
loading package files...
:: Processing package changes...
reinstalling hwdata...
reinstalling libelf...
reinstalling systemd...

and then I ran

pacman -S    --root /mnt --cachedir /mnt/var/cache/pacman/pkg hwdata libelf systemd

warning: hwdata-0.382-1 is up to date -- reinstalling
warning: libelf-0.191-2 is up to date -- reinstalling
warning: systemd-255.5-4 is up to date -- reinstalling
resolving dependencies...
error: could not open file /mnt/var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
looking for conflicting packages...

Packages (3) hwdata-0.382-1  libelf-0.191-2  systemd-255.5-4

Total Installed Size:  42.81 MiB
Net Upgrade Size:       0.00 MiB

:: Proceed with installation? [Y/n] checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
reinstalling hwdata...
reinstalling libelf...
reinstalling systemd...
:: Running post-transaction hooks...
( 1/10) Creating system user accounts...
( 2/10) Updating journal message catalog...
( 3/10) Reloading system manager configuration...
  Skipped: Running in chroot.
( 4/10) Reloading user manager configuration...
  Skipped: Running in chroot.
( 5/10) Updating udev hardware database...
( 6/10) Applying kernel sysctl settings...
  Skipped: Running in chroot.
( 7/10) Creating temporary files...
/proc/ is not mounted, but required for successful operation of systemd-tmpfiles. Please mount /proc/. Alternatively, consider using the --root= or --image= switches.
error: command failed to execute correctly
( 8/10) Reloading device manager configuration...
  Skipped: Running in chroot.
( 9/10) Arming ConditionNeedsUpdate...
(10/10) Reloading system bus configuration...
  Skipped: Running in chroot.

and then

pacman -Sy  --root /mnt --cachedir /mnt/var/cache/pacman/pkg linux

warning: linux-6.8.9.arch1-1 is up to date -- reinstalling
resolving dependencies...
error: could not open file /mnt/var/lib/pacman/local/firefox-125.0.3-2/desc: No such file or directory
looking for conflicting packages...

Packages (1) linux-6.8.9.arch1-1

Total Installed Size:  132.52 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
reinstalling linux...
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Updating linux initcpios...
/usr/share/libalpm/scripts/mkinitcpio: line 47: /dev/fd/63: No such file or directory
error: command failed to execute correctly

Last edited by wideroger (2024-05-07 10:46:39)

Wild Penguin

Member

Registered: 2015-03-19

Posts: 399

Re: [SOLVED] Unable to boot after crash mid update.

I think there's still something hosed up because of the crash.

Maybe in this case you might try to run the failing upgrades with two y's, i.e. pacman -Syy... it's generally not advised but something is wrong with /var/lib/pacman from the looks of it? It should not do any harm at least (besides stress on the servers).

Unless someone has any specific ideas, a re-install might be a good idea after all. Generally, it's a good idea to figure out what has gone wrong, why, and fix it properly, bus since you got work to do...

Lessons learned: don't multitask too much while upgrading.

OT, OTOH and IMHO (and TMA-2KTO): pacman should be more resilient towards crashes (including things such as: the boot process should always have a fail-safe during Kernel upgrades, pacman should realize a package is in mid-install etc...). But I realize doing that might be against Arch Linux's Principles, and even if it wasn't, a lot of work...

Last edited by Wild Penguin (2024-05-07 11:38:13)

loqs

Member

Registered: 2014-03-06

Posts: 18,916

Re: [SOLVED] Unable to boot after crash mid update.

After chrooting in try:

# touch /var/lib/pacman/local/firefox-125.0.3-2/desc
# pacman -Syu
# mkinitcpio -p

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

don't multitask too much while upgrading.

I was using Spotify and Codelite I don't think it was that much multitasking

This is the output for

pacman -Syu

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

Packages (63) discord-0.0.53-1  docker-1:26.1.1-1  gedit-47.0-1  gegl-0.4.48-3  gnome-calculator-46.1-1  gtk4-1:4.14.4-1  harfbuzz-icu-8.4.0-2  imagemagick-7.1.1.32-1  iproute2-6.8.0-2  lib32-glib2-2.80.0-4  lib32-glibc-2.39-4  lib32-harfbuzz-8.4.0-2  lib32-libcups-2.4.8-1  lib32-libgpg-error-1.49-1  lib32-libnsl-2.0.1-1  lib32-libpciaccess-0.18.1-1  lib32-libpsl-0.21.5-1  lib32-libtasn1-4.19.0-2  lib32-libva-2.21.0-1  lib32-libx11-1.8.9-1  lib32-libxcb-1.17.0-1  lib32-libxmu-1.2.1-1  lib32-mpg123-1.32.6-1  lib32-pam-1.6.1-1  lib32-sdl2-2.30.3-1  lib32-sqlite-3.45.3-1  lib32-tdb-1.4.10-1  libdeflate-1.20-2  libdovi-3.3.0-2  libgedit-gfls-0.1.0-1  libgedit-gtksourceview-299.2.1-1  libgedit-tepl-6.10.0-2  libibus-1.5.30-1  libisl-0.26-2  libmfx-23.2.2-3  libnvme-1.9-1  libplist-2.5.0-1  libtiff-4.6.0-5  libxnvctrl-550.78-1  llvm-17.0.6-4  minizip-1:1.3.1-2  mkinitcpio-39-1  mobile-broadband-provider-info-20240407-1  nano-8.0-1  nvidia-550.78-1  nvidia-settings-550.78-1  pcsclite-2.2.0-4  pycharm-community-edition-2024.1.1-1  qt6-base-6.7.0-5  rygel-1:0.42.6-1  steam-1.0.0.79-2  systemd-sysvcompat-255.5-4  tcl-8.6.14-4  telegram-desktop-5.0.1-1  tk-8.6.14-3  tracker3-miners-3.7.3-1  virtualbox-7.0.18-1  virtualbox-guest-utils-7.0.18-1  virtualbox-host-modules-arch-7.0.18-1  vlc-3.0.20-9  wget-1.24.5-2  wxwidgets-common-3.2.4.1-1  wxwidgets-gtk3-3.2.4.1-1

Total Download Size:    130.93 MiB
Total Installed Size:  2767.24 MiB
Net Upgrade Size:         5.44 MiB

:: Retrieving packages...
 discord-0.0.53-1-x86_64 downloading...
 docker-1:26.1.1-1-x86_64 downloading...
 imagemagick-7.1.1.32-1-x86_64 downloading...
 wxwidgets-gtk3-3.2.4.1-1-x86_64 downloading...
 gegl-0.4.48-3-x86_64 downloading...
 steam-1.0.0.79-2-x86_64 downloading...
 wxwidgets-common-3.2.4.1-1-x86_64 downloading...
 gnome-calculator-46.1-1-x86_64 downloading...
 rygel-1:0.42.6-1-x86_64 downloading...
 libtiff-4.6.0-5-x86_64 downloading...
 libnvme-1.9-1-x86_64 downloading...
 libdovi-3.3.0-2-x86_64 downloading...
 pcsclite-2.2.0-4-x86_64 downloading...
 libdeflate-1.20-2-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading libtiff...
upgrading discord...
upgrading iproute2...
upgrading docker...
installing libgedit-gfls...
upgrading libgedit-gtksourceview...
installing libgedit-tepl...
upgrading gedit...
upgrading libdeflate...
upgrading gegl...
upgrading gtk4...
upgrading gnome-calculator...
upgrading harfbuzz-icu...
upgrading imagemagick...
upgrading lib32-glibc...
upgrading lib32-glib2...
upgrading lib32-harfbuzz...
upgrading lib32-libtasn1...
upgrading lib32-libcups...
upgrading lib32-libgpg-error...
upgrading lib32-libpciaccess...
upgrading lib32-libpsl...
upgrading lib32-libxcb...
upgrading lib32-libx11...
upgrading lib32-libva...
upgrading lib32-libxmu...
upgrading lib32-mpg123...
installing lib32-libnsl...
upgrading lib32-pam...
upgrading lib32-sdl2...
upgrading lib32-sqlite...
upgrading lib32-tdb...
upgrading libdovi...
upgrading libibus...
upgrading libisl...
upgrading libmfx...
upgrading libnvme...
upgrading libplist...
upgrading libxnvctrl...
upgrading llvm...
upgrading minizip...
upgrading mkinitcpio...
upgrading mobile-broadband-provider-info...
upgrading nano...
upgrading nvidia...
upgrading nvidia-settings...
upgrading pcsclite...
upgrading pycharm-community-edition...
upgrading qt6-base...
upgrading rygel...
upgrading steam...
upgrading systemd-sysvcompat...
upgrading tcl...
upgrading telegram-desktop...
upgrading tk...
upgrading tracker3-miners...
upgrading virtualbox-host-modules-arch...
upgrading virtualbox...
upgrading virtualbox-guest-utils...
upgrading vlc...
upgrading wget...
upgrading wxwidgets-common...
upgrading wxwidgets-gtk3...
New optional dependencies for wxwidgets-gtk3
    webkit2gtk-4.1: for webview support [installed]
:: Running post-transaction hooks...
( 1/16) Creating system user accounts...
( 2/16) Reloading system manager configuration...
  Skipped: Running in chroot.
( 3/16) Reloading user manager configuration...
  Skipped: Running in chroot.
( 4/16) Creating temporary files...
( 5/16) Reloading device manager configuration...
  Skipped: Running in chroot.
( 6/16) Arming ConditionNeedsUpdate...
( 7/16) Updating the MIME type database...
( 8/16) Updating module dependencies...
( 9/16) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.8.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
  -> Running build hook: [keyboard]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> 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: 'aic94xx'
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(10/16) Warn about old perl modules
(11/16) Compiling GSettings XML schema files...
(12/16) Updating icon theme caches...
(13/16) Updating GTK4 module cache...
(14/16) Updating the info directory file...
(15/16) Updating the desktop file MIME type cache...
(16/16) Updating the vlc plugin cache...

and this is the output for

mkinitcpio -p linux

(the -p option needs the preset)

==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.8.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.9-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [kms]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [consolefont]
  -> Running build hook: [block]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful

I'll try booting normally now

wideroger

Member

Registered: 2023-04-19

Posts: 21

Re: [SOLVED] Unable to boot after crash mid update.

IT WORKS! Thank you everyone!
But I'm missing the packages that didn't have the mtree file, I'll try installing them now

Last edited by wideroger (2024-05-07 12:19:09)