You are not logged in.
Pages: 1
I have grub installed in MBR at `/dev/sda`. There are 2 partitions in `/dev/sda`, one of them `/boot`, unencrypted. The other one LUKS on LVM with the root of the filesystem in one of the LVMs.
I upgraded the system on September 02 and followed the instructions in the news (https://archlinux.org/news/grub-bootloa … ibilities/). In my case I did
# grub-install --target=i386-pc /dev/sda
# grub-mkconfig -o /boot/grub/grub.cfg
No errors were printed. The next time I restarted the machine I got stuck in the grub console (normal one, not rescue).
I booted the live system, mounted my discs and chrooted. Ran the grub-install and grub-imkconfig again. No errors. Rebooted but the issue remained.
Next time in the chroot I diffed the `/etc/default/grub` and `/etc/default/grub.pacnew`, because I have some changes in `GRUB_CMDLINE_LINUX_DEFAULT`. I ported my changes to the `grub.pacnew` file and made it the new default `grub`. grub-mkconfig was ran again. System rebooted, issue persisted.
What's the next step for me to debug and get the system booting? I'm not getting any further with the grub wiki.
Edit:
In the grub console I've done the following
- set root=hd0, chainloader +1, boot. Loops back into grub, I don't see any error printed.
- same as above but with `set debug=all`. I don't see any particularly useful information after running boot and landing in grub again.
Last edited by zupzup7 (2022-10-04 16:19:21)
Offline
Is anything being added to grub.cfg?
Offline
So it seems. I add a line manually in the grub.cfg, run grub-mkconfig and the line is gone.
Offline
Looks like I don't have any kernel in `/boot`. Attempting to run `mkinitcpio` from the chrooted system fails
# mkinitcpio -P
==> ERROR: No presets found in /etc/mkinitcpio.d
# pacman -Q linux
linux 5.19.7.arch1-1Looking at the pacman log, I see that the session with the linux upgrade got interrupted. That's when I broke the system.
I'm in the arch-chroot'ed system, with all my partitions mounted. Is `pacman -U` the right thing to do at this point? I don't find any definitive info in the wiki or forums about this being the safest thing to do.
Offline
pacman -U won't do anything, try a normal update including the linux package explicitly to be sure
sudo pacman -Syu linuxmaybe also check whether anything else got corrupted
pacman -Qkk 2>&1 > /dev/nullLast edited by V1del (2022-10-04 13:54:54)
Offline
After upgrading with pacman + grub-install + grub-mkconfig the system runs again. Many thanks for your time V1del and Scimmia!
Offline
Pages: 1