#grub broken again help
92 messages · Page 1 of 1 (latest)
What part of the boot?
Mobo boot? Bios boot? Does it launches UEFI? Does it reaches fsck?
Does it reaches GRUB?
Can you roll back to the old kernel and check if it works again?
Have you checked journalctl for log messages?
can you attach a picture
Have you tried/considered rolling back to the previous kernel that was working before your change?
have you mounted your boot disk as well?
uh
when did you do that
i think its best if you reformat and reinstall grub if you did any changes
sda2 is the root and not important
del is mentioning that you shouldnt format sda2. Just sda1
A clean install, just like you did before
you might be able to do it without formatting
Something went wrong and you dont know what. We also dont know what you have done.
Why not repeating from scratch
mount /dev/sda2 /mnt
mount --mkdir /dev/sda1 /mnt/boot
arch-chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg
mkinitcpio -p linux-lts
Sorry, I believe me talking here mght make things more confusing. Ill let del take it
@vast rune did you format the boot partition already
i am not that familliar with btrfs sorry
ok that is good
notify me when you have chrooted into the system
okay
you have to mount that too
what is inside of it
that is what is supposed to happen
great
i assume you have a x86 cpu?
it is not?
can you remove the /boot folder rm -rf /boot
and chroot out exit and mount --mkdir /dev/sda1 /mnt/boot
then chroot back in
mkfs.fat -F 32 /dev/sda1 and try again
@river coral Might be a typo on boot instead of /boot, isnt it?
you are right
@vast rune make sure it is /mnt/boot instead of just boot
can you run lsblk and send a screenshot of the output?
alright that seems good
chroot back in
is the boot folder in there?
great now please grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
make sure there are no typos
what?
what cpu architecture do you have?
modprobe efivarfs
cat /sys/firmware/efi/fw_platform_size
you are not booted in UEFI mode
why?
the archiso usb stick?
try booting into the usb using UEFI and make sure secure boot is disabled
if booted in, before mounting everything again do cat /sys/firmware/efi/fw_platform_size again
great
can you remount everything like in this picture?
correct
dont forget to chroot back in
good
now grub-mkconfig -o /boot/grub/grub.cfg
if this is done can you show ls in /boot
try grub-mkdevicemap then try again
oh you are not chrooted in
lsblk send output
yes, chroot in and do it again
wait
nvm
are you sure?
because it says root@archiso in the shell
they must have updated it then
again grub-mkconfig -o /boot/grub/grub.cfg
exit chroot
and use arch-chroot instead
ss please
can you lsblk again
cat /etc/fstab
that might be the case
though unlikely
hmm
i think its best if we go from the intalling stage again
please grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
alright that is not the problem then
i am not sure
it should
no
kernels are packages installed in the root drive
what is in the /boot is GRUB itself, and the initramfs, which is essentially a small operating system that launches the bigger kernel
i assume you are headed to work
i will likely sleep soon, to any further readers:
reinstall GRUB,
regenerate config,
regenerate initramfs.
it is better to do them again just in case, and the config regeneration reported errors
yes
either disable it or find a fix
did you do it without error after?
no
when you get back:
- mount everything again like in previous pic, chroot with
arch-chroot - disable os prober
- install grub (to be sure):
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB - regenerate config:
grub-mkconfig -o /boot/grub/grub.cfg - reinstall the kernel with
pacman -S linux-ltsit will auto-generate the initramfs
if reinstalling the kernel fails, trymkinitcpio -p linux-lts
I am online again