You are not logged in.
Hi guys,
The other day, I did a fresh install of Arch, and installed SDDM and KDE Plasma for my desktop. I use GRUB for my bootloader.
This morning when I booted my machine, it was telling me it couldn't mount /boot. checking uname -r and pacman -Q linux, uname reported 5.18.13, and pacman reported 5.18.14. I looked into it, and another forum post said to run pacman -U /var/cache/pacman/pkg/linux-5.18.13.arch1-1-x86_64.pkg.tar.zst. Doing that takes me back to a bootable 5.18.13, but hangs indefinitely on
Starting version 251.3-1-arch
/dev/sdd3: clean, xxx/xxx files, xxx/xxx blocks
I can get to tty2 from here and try a bunch of things, killing sddm, whatnot, but I can't get it to boot past those initial two lines.
Looking into it, it seemed like potentially an entropy problem, but I've tried adding both haveged and the boot parameter (I think it's something like cpu.rand_on) to no avail. entropy_avail still returns 256 and I cannot get into a graphical desktop, or past those two lines at all.
I'll also mention I tried pacman -Syu while in tty on 5.18.13 to get back to 5.18.14, but that just gave me the same "unable to mount /boot" issue as last time and I had to downgrade to 5.18.13 again.
Any suggestions are very welcome, as is probably obvious I'm somewhat in over my head here. Let me know if I can provide any more info to help as well.
Last edited by shawnsg (2022-07-25 23:06:02)
Offline
Was able to fix my issue, I'll leave my solution in case anyone else is having a similar issue.
Seems I had my boot partition persistently mounted to /boot. Turns out, that's not what I want.
umount /boot && pacman -Syu
seemed to be the fix I needed.
Offline
No, you need to fix your bootloader.
Offline