Hi everyone, I REALLY screwed something up.
After doing a full system update a couple days ago, Manjaro was no longer appearing in my boot list in GRUB. GRUB had a shiny new look, which I’m guessing means a new GRUB update messed things up. I realize this is a common issue popping up here in the last few months, and I should have checked those threads before trusting random Google results.
After trying random things suggested around the internet, I cannot boot into GRUB at all. My Manjaro partition has the highest boot priority. When I power my computer on, instead of booting into GRUB, I instead get a black screen. After a few seconds, my computer switches itself off and reboots into the BIOS. From there, I’m still able to boot into Windows (I am dual-booting). I’m guessing my BIOS is smart enough to reboot into the BIOS when I am unable to load GRUB.
Because of my (very) limited understanding of BIOS/EFI, mounting, bootloaders, I am unsure what to do now. I am afraid of messing my system up even further.
If it is useful, here is the output of fdisk -l after I manjaro-chroot from a live USB (only showing the output including the “Device”, “Start”, etc. columns):
Device Start End Sectors Size Type /dev/sda1 2048 1085439 1083392 529M Windows recovery environm /dev/sda2 1085440 1288191 202752 99M EFI System /dev/sda3 1288192 1320959 32768 16M Microsoft reserved /dev/sda4 1320960 1426877101 1425556142 679.8G Microsoft basic data /dev/sda5 1426877103 1953523711 526646609 251.1G Linux filesystem Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT /dev/sdb2 206848 3906105343 3905898496 1.8T 7 HPFS/NTFS/exFAT /dev/sdb3 3906105344 3907026943 921600 450M 27 Hidden NTFS WinRE
Additionally, here is the output of lsblk -f after I manjaro-chroot from a live USB:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT loop0 loop1 loop2 loop3 sda |-sda1 |-sda2 117.9G 47% /boot/efi |-sda3 |-sda4 `-sda5 117.9G 47% /boot/efi sdb |-sdb1 |-sdb2 `-sdb3 sdc |-sdc1 `-sdc2