You are not logged in.
I broke my system as I rebooted while pacman was doing a full system upgrade. When I tried to boot Arch, it said something about vmlinuz not being found. I arch-chrooted into my system and did a full system upgrade. That didn't work, so I reinstalled Grub. Now, when I start my PC, only W*ndows 10 shows up. There is no other bootloader. I followed the Arch wiki's instructions. What can I do?
Edit: frens, I'm gonna reinstall grub and linux. I'm nuking the EFI partition and moving W*ndows partition rn. Wish me luck and no data loss
Last edited by average_scout (2024-06-14 16:16:26)
Offline
from within arch-chroot:
- use efibootmgr to check current entries in the firmware's boot list
- check if you have the ESP mounted before installibg the bootloader - common failure: the ESP was not mounted so the bootloader was not installed on the ESP but rather in its mountpoint
- check if the bootloader's config is in the expected location - grub by default always uses /boot/grub/grub.cfg - however this can be changed with the install-parameter --boot-directory=
- check the content of the config - otherwise regenerate a fresh one with grub-mkconfig and check the new content afterwards
- if the new config doesn't contain an entry use pacman to reinstall the kernel - or it manually and run mkinitcpio -> run mkconfig again
if this still doesn't help report back
Offline
from within arch-chroot:
- use efibootmgr to check current entries in the firmware's boot list
- check if you have the ESP mounted before installibg the bootloader - common failure: the ESP was not mounted so the bootloader was not installed on the ESP but rather in its mountpoint
- check if the bootloader's config is in the expected location - grub by default always uses /boot/grub/grub.cfg - however this can be changed with the install-parameter --boot-directory=
- check the content of the config - otherwise regenerate a fresh one with grub-mkconfig and check the new content afterwards
- if the new config doesn't contain an entry use pacman to reinstall the kernel - or it manually and run mkinitcpio -> run mkconfig againif this still doesn't help report back
efibootmgr only shows W*ndows Boot Manager and Ventoy USB. ESP is mounted, and /boot/grub/grub.cfg is not empty. However, for some reason, my ESP is full. I try to remove files and folders but they just appear again. I cannot free up space on my boot partition. I can't format it because then I'd have to reinstall the other OS, which is a pain in the ass. Online forum posts don't have any solutions. How do I free up space on the ESP?
Offline
from within arch-chroot:
- use efibootmgr to check current entries in the firmware's boot list
- check if you have the ESP mounted before installibg the bootloader - common failure: the ESP was not mounted so the bootloader was not installed on the ESP but rather in its mountpoint
- check if the bootloader's config is in the expected location - grub by default always uses /boot/grub/grub.cfg - however this can be changed with the install-parameter --boot-directory=
- check the content of the config - otherwise regenerate a fresh one with grub-mkconfig and check the new content afterwards
- if the new config doesn't contain an entry use pacman to reinstall the kernel - or it manually and run mkinitcpio -> run mkconfig againif this still doesn't help report back
Scratch the previous reply, doing 'pacman -S linux' fills up the boot partition fully. Then, when it tries to install Grub, it says there isn't enough free space.
Offline
there we go
the ESP like was created by windows with just about 100mb or so - which is enough for the about 25-30 mb required for windows uefi boot stuff - but linux with both initrd and fallback easily fills up couple 100mbs (on my esp currently about 400mb are used due to multiple kernels and initrd)
unfortunately "moving" the windows system ntfs artition is a BAD idea
ainother option: uefi doesn't require the esp to be the first partition - so shrinking the win os partition by about 1g, delete the existing esp and create a new bigger one at the end is a safer way to get space on a too small esp
my preferred option: clean the disk - create a esp about 1g+ and start from scratch
Offline
there we go
the ESP like was created by windows with just about 100mb or so - which is enough for the about 25-30 mb required for windows uefi boot stuff - but linux with both initrd and fallback easily fills up couple 100mbs (on my esp currently about 400mb are used due to multiple kernels and initrd)
unfortunately "moving" the windows system ntfs artition is a BAD idea
ainother option: uefi doesn't require the esp to be the first partition - so shrinking the win os partition by about 1g, delete the existing esp and create a new bigger one at the end is a safer way to get space on a too small esp
my preferred option: clean the disk - create a esp about 1g+ and start from scratch
Already moved NTFS. W*ndows doesn't seem to have any issues or data loss. Now I'm stuck on installing Grub
Offline
cryptearth wrote:there we go
the ESP like was created by windows with just about 100mb or so - which is enough for the about 25-30 mb required for windows uefi boot stuff - but linux with both initrd and fallback easily fills up couple 100mbs (on my esp currently about 400mb are used due to multiple kernels and initrd)
unfortunately "moving" the windows system ntfs artition is a BAD idea
ainother option: uefi doesn't require the esp to be the first partition - so shrinking the win os partition by about 1g, delete the existing esp and create a new bigger one at the end is a safer way to get space on a too small esp
my preferred option: clean the disk - create a esp about 1g+ and start from scratchAlready moved NTFS. W*ndows doesn't seem to have any issues or data loss. Now I'm stuck on installing Grub
Fuck it, I'm reinstalling. Also, how do I force W*ndows installer to make the boot partition big?
Offline
Never found a solution. Mods, please close
Offline
average_scout wrote:cryptearth wrote:there we go
the ESP like was created by windows with just about 100mb or so - which is enough for the about 25-30 mb required for windows uefi boot stuff - but linux with both initrd and fallback easily fills up couple 100mbs (on my esp currently about 400mb are used due to multiple kernels and initrd)
unfortunately "moving" the windows system ntfs artition is a BAD idea
ainother option: uefi doesn't require the esp to be the first partition - so shrinking the win os partition by about 1g, delete the existing esp and create a new bigger one at the end is a safer way to get space on a too small esp
my preferred option: clean the disk - create a esp about 1g+ and start from scratchAlready moved NTFS. W*ndows doesn't seem to have any issues or data loss. Now I'm stuck on installing Grub
Fuck it, I'm reinstalling. Also, how do I force W*ndows installer to make the boot partition big?
You don't! Either you partition the drive yourself and do some manual work like Chris Titus' "Windows the Arch way" - or you rely on what the Windows Installer does.
I personally do it "the Arch way": partition the drive myself and use DISM to unpack install.wim and BCDBOOT to install the windows bootloader - then override it with GRUB with os-prober to chain windows' bootmgfw from grub and use grub as boot manager instead of the uefi bootorder.
Last edited by cryptearth (2024-06-14 22:58:18)
Offline