[Solved] Segmentation Faults and Broken Kernel after Update

rdevil · 2025-08-30 18:45:17

Hello all,

I was a bit negligent with updating my system in the last month, had to -Syu about 144 packages including the kernel and whatnot. I ended up with a segmentation fault (core dumped) during the update, performed a reboot, and now I'm struggling to get things back up. I'll list some of my attempts and error codes below:

On update: pacman.log image

On boot (grub):

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

Performed an fsck (just a bit error iirc).

After mounting my ext4 and esp partitions, arch-chroot /mnt:

free(): invalid size  
/usr/bin/arch-chroot: line 187: 2791 Segmentation fault    (core dumped) SHELL=/bin/bash $pid\_unshare chroot "${chroot\_args\[@\]}" -- "$chrootdir" "${args\[@\]}"

then running pacstrap /mnt [base/linux/etc...] :

 ...  
(1/1) checking keys in keyring ✓  
(1/1) checking package integrity ✓  
(1/1) loading package files ✓  
(1/1) checking for file conflicts ✓  
(1/1) checking available disk space ✓  
:: Running pre-transaction hooks...  
(1/2) Performing snapper pre snapshots for the following configurations...  
error: command terminated by signal 11: Segmentation fault  
error: failed to commit transaction (failed to run transaction hooks)  
Errors occurred, no packages were upgraded

I haven't been able to pin any RAM issues down with a 12h run of Memtest86+, and GoldMemory won't boot when I try using it. I haven't tried messing with my boot partition as I'm not too confident in doing that without detailed instructions. Some detailed help would be appreciated as I am relatively new. Probably not helpful --but I'm running on an HP Envy x360 Model ay0037nr.
Thanks!

Last edited by rdevil (2025-08-31 19:50:17)

seth · 2025-08-30 19:45:35

https://wiki.archlinux.org/title/Pacman … an_upgrade
You'll have to use the pacman from the install iso and do NOT chroot NOR --sysroot (chroots) but --root … --cachedir

rdevil · 2025-08-30 20:36:03

Thanks, but it looks like I'm still getting a Segmentation fault. Using the latest install iso (8.1.2025):

#   pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syu
:: Synchronizing package databases...
 core is up to date
 extra is up to date
:: starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing pcre2 (10.46-1) breaks dependency 'pcre2=10.45' required by lib32-pcre2

#   pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syud
...
(129/129) checking keys in keyring
(129/129) checking package integrity
(129/129) loading package files
(129/129) checking available disk space
warning: could not get file information for boot/amd-ucode.img
:: Running pre-transaction hooks
(1/2) Performing snapper pre snapshots for the following configurations...
error: command terminated by signal 11: Segmentation fault  
error: failed to commit transaction (failed to run transaction hooks)  
Errors occurred, no packages were upgraded
pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syud  4.21s user 2.93s system 52% cpu 13.530 total

Last edited by rdevil (2025-08-30 20:36:18)

seth · 2025-08-30 20:49:13

error: failed to prepare transaction (could not satisfy dependencies)

This is because the multilib repo isn't enabled on the install iso by default.

(1/2) Performing snapper pre snapshots for the following configurations...
error: command terminated by signal 11: Segmentation fault
error: failed to commit transaction (failed to run transaction hooks)

That's likely from https://archlinux.org/packages/extra/any/snap-pac/ ?

You could temporarily remove the package (or at least the /usr/share/libalpm/hooks/*-snap-pac*.hook )

rdevil · 2025-08-30 21:38:53

Unfortunately -- though that managed to install a bunch of things -- when I rebooted, I still got the error about the kernel that was noted at the beginning of this post. I believe I also still cannot arch-chroot.

As you said, I moved the hook files elsewhere and reran the command with -Syud. I got a single segmentation fault that aborted it, unfortunately I didn't get a picture of that.
However, when I ran it again... I got the following result.

Then I ran it again (a 3rd time)....

:: Starting full system upgrade...
there is nothing to do

So I continued with the instructions from the link you originally provided and tried to update grub, go, ruby, and python. For reference, here's the output for step 5 in those instructions (ignoring python).
Upon reboot, still getting the error. I should also note that I got a lot of Segmentation faults throughout the process but I didn't manage to capture all of them here.

Apologies for posting a bunch of images, but I can only type so much manually.

EDIT: I should note that I also ran umount -a prior to rebooting. Let me know if that's something I should NOT do.

Last edited by rdevil (2025-08-31 00:06:52)

seth · 2025-08-31 07:17:40

when I rebooted, I still got the error about the kernel that was noted at the beginning of this post

YOU either forgot to mount the /boot partition or need to explicitly re-install the kernel

I believe I also still cannot arch-chroot

Don't believe, test.

However, when I ran it again... I got the following result.

I can only type so much manually.

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

rdevil · 2025-08-31 08:19:10

Ran in the beginning: https://0x0.st/KHOL.txt

YOU either forgot to mount the /boot partition or need to explicitly re-install the kernel

Yea, I was mounting to /mnt/esp (I don't remember where I got that instruction)... I am now mounting to /boot and reran the following:

#  pacman --root ... --cachedir... -Sy base linux linux-lts
:: Processing package changes...
...
free(): invalid size
error: command terminated by signal 6: Aborted
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
error: command terminated by signal 6: Aborted
(3/3) Updating linux initcpios...
free(): invalid size
error: command terminated by signal 6: Aborted

#  pacman --root ... --cachedir... -Syu
...
there is nothing to do

#  arch-chroot /mnt
/usr/bin/arch-chroot: line 187: 3439 Segmentation fault      (core dumped) SHELL=/bin/bash $pid\_unshare chroot "${chroot\_args\[@\]}" -- "$chrootdir" "${args\[@\]}"

After all this: https://0x0.st/KHOp.txt

And still can't boot in (same error). Let me know what other data I can provide.

Last edited by rdevil (2025-08-31 08:40:33)

seth · 2025-08-31 12:15:25

amd-ucode: 17 total files, 1 altered file
glibc: 1618 total files, 13 altered files
gstreamer: 341 total files, 7 altered files
hyprland: 349 total files, 1 altered file
nodejs-nopt: 30 total files, 1 altered file
shadow: 576 total files, 1 altered file
snap-pac: 21 total files, 3 altered files
systemd: 1569 total files, 1 altered file

glibc is gonna be a problem, re-install that explicity.
gstreamer might (likely) also be broken but not necessarity fatal

rdevil · 2025-08-31 16:49:18

Done, and now I am able to arch-chroot in! I moved back the snap-pac files, reinstalled the kernel from arch-chroot, and I am now able to boot and log in as well!

That said, when I ran the command from earlier I got:

warning: amd-ucode: /mnt/boot/amd-ucode.img (Permissions mismatch)
warning: amd-ucode: /mnt/boot/amd-ucode.img (Modification time mismatch)
warning: node.js-nopt: /mnt/usr/bin/nopt (Permissions mismatch)
warning: shadow: /mnt/usr/bin/groupmems (GID mismatch)
warning: shadow: /mnt/usr/bin/groupmems (Permissions mismatch)
warning: systemd: /mnt/var/log/journal (GID mismatch)
amd-ucode: 17 total files, 1 altered file
nodejs-nopt: 30 total files, 1 altered file
shadow: 576 total files, 1 altered file
systemd: 1569 total files, 1 altered file

I've tried reinstalling all of these explicitly to no avail using the --root and --cachedir command. As well as while chrooted in.

Any steps I should take to fix these as well?

Last edited by rdevil (2025-08-31 16:49:44)

seth · 2025-08-31 17:58:30

Some deviations are perfectly normal, there's nothing to fix about this ("I assume", idk about nodejs-nopt)

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

rdevil · 2025-08-31 19:50:26

Thanks Seth!

Arch Linux

#1 2025-08-30 18:45:17

[Solved] Segmentation Faults and Broken Kernel after Update

#2 2025-08-30 19:45:35

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#3 2025-08-30 20:36:03

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#4 2025-08-30 20:49:13

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#5 2025-08-30 21:38:53

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#6 2025-08-31 07:17:40

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#7 2025-08-31 08:19:10

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#8 2025-08-31 12:15:25

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#9 2025-08-31 16:49:18

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#10 2025-08-31 17:58:30

Re: [Solved] Segmentation Faults and Broken Kernel after Update

#11 2025-08-31 19:50:26

Re: [Solved] Segmentation Faults and Broken Kernel after Update

Board footer