You are not logged in.
Hi,
I upgraded the system this morning and something unusual happened. While the system was upgrading (including the linux kernel, coreutils and systemd) in a console inside KDE, I was doing other things and then I suddenly got logged out of KDE into the login screen. I didn't think too much about why that happened and just went on to reboot the laptop. But since then it won't boot. I'm getting an early error during the boot process, something like:
Warning: /lib/modules/6.2.9-arch1-1/modules.devname not found - ignoringThen a few lines when it start systemd-udevd, running hook [udev], triggering uevents..., performing fsck on ..., LINUX: clean, mounting 'UUID=....' And then it comes the final error:
mount: /new_root: unknown filesystem type 'ext4'.After that I' dropped into an emergency shell, but it freezes and doesn't let me do anything else.
What I've done so far:
- I used an install media in a USB stick to boot a system and chroot into my instalation.
- I checked /var/log/pacman-log, where I found errors when running several hooks saying that XXX module was not found (or similar, from memory now)
- I went on and reinstalled linux (the kernel), this time without seeing any errors on the screen. Rebooted, but again the same problem and error message.
- Reinstalled systemd, systemd-libs and systemd-vcompat. Rebooted, but again the same problem and message.
- Downgraded the kernel to the previous one (6.2.8), and after rebooting still the same error, including the same line: "Warning: /lib/modules/6.2.9-arch1-1/modules.devname not found - ignoring", which would be normal since that file didn't exist anymore and instead a new one on the path "6.2.8 is what existed in the filesystem.
- Downgraded systemd, systemd-libs and systemd-vcompat to the prevous versions from the cache too. But still the same error, still referring to kernel 6.2.9 in the error message.
- Upgraded all the packages again, and run mkinitcpio manually on a subsequent boot into chroot. No luck, same error, same message.
- Reinstalled coreutils, run "mkinitcpio -P" again. Same results.
So I really don't know what's going on and what else to try. The boot images get updated correctly in the /boot directory every time I reinstall the kernel (both old and new versions), but when I boot it seems to be repeating that error regardless as if it was not reading the new images?
If anyone has any idea of what could be happening of wants more info, please let me know. Thanks!
Last edited by Bogart (2023-04-05 11:02:30)
Offline
Ok, I solved it. Stupid me I was not mounting correctly the boot partition before "arch-chroot"-ing into my installation. Once I realized I had my boot directory in a different partition and mounted it correctly, I updated the kernel and now everything works fine again.
Offline