#after windows 11 install, grub refuses to start
139 messages · Page 1 of 1 (latest)
Windows prolly destroyed your bootloader
i register it manually
Huh, are you sure you have registered it correctly via chroot?
Boot into your Live USB, mount your partitons and re-initialize your grub
okay
GRUB is in /dev/sdb1
Windows is in /dev/sda1
You know how, tho?
wdym
how I did the install was:
Linux on /dev/sdb
Windows on /dev/sda
thats just it
im waiting for the live environment to be ready
i have to burn the iso for the 3rd time
windows on an SSD
[Reply to:](#1236648276196069478 message) Wait you installed Windows, on a ssd?
Huh why?
Yk you could have removed the linux one b4?
wdym
Like the Linux ssd, so that windows doesnt get to know there are several ssds
what should I do now
uninstall the second SSD?
(it's gonna be as easy as removing 3 screws and uninstalling a CD-ROM)
before Windows install I had RAID0 on two SSDs
Lmao, no.
and Linux
Oh okay, thats smart. So If youd reinstall linux youd be able to, without dataloss?
I have no valuable data to preserve between installs
But Reinstalling it would be the last thing Id do
except the huge archive of pride flags but I don't want to talk about this
[Reply to:](#1236648276196069478 message) I have no valuable data to preserve between installs
L - M - A -O
Anyways
Idk if I am right, but Is it possible that your Grubbtl got destroyed, cuz you isntalled windows after Linux?
wdym grubbtl
Grubbootloader, sorry
also I installed Linux again after installing Windows
Again? So Windows didnt destroy your Bootloader, its more a setup issue?
Sorry im just confused rn
My firmware normally doesn't recognise GRUB2
it does recognise GRUB
so I normally enter the UEFI Shell
and create a boot entry that points at GRUB2
and it normally works
but now it does not
I can also start GRUB through external means like via the chainloader command on a GRUB on an USB
and UEFI Shell,
but it won't start on its own
Cant you just add the GRUB2 bootloader to the GRUB(1?) bootloader via osprober and setting the bootpartitoins of the other distros to that one?
wdym
I am assuming you have multiple Linux distros Installed because of GRUB and GRUB2
Why are then 2 GRUBS?
and there's just GRUB2
but before that I used GRUB as well and GRUB requires no additional handling,
while GRUB2 does
Wait is there an existing EFI partition with another bootloader?
What does GRUB(1) show?
nothing?
there's GRUB on /dev/sdb1
there's WBM on /dev/sda1
Yes? Isnt that what you want?
if I somewhat get to fire the GRUB on /dev/sdb1
it would show Windows 11 on /dev/sda
but I can't get the firmware to recognize GRUB on /dev/sdb
But you are still able to boot into it?
if I plug in an USB
That doesnt make sense to me 😭
the GRUB on the USB starts
then I can run
chainloader (hd1,1)/EFI/opensuse/grubx64.efi
but the GRUB on (hd1,1) cannot start
im sorry i explained it too messy
okay so this is the disk layout
Disk 1: (has Windows 11)
Partition 1: EFI System Partition (1GB)
Partition 2: Microsoft Reserved
Partition 3: NTFS (Windows Root)
Disk 2: (has openSUSE Tumbleweed)
Partition 1: EFI System Partition
Partition 2: BTRFS (Linux Root)
and I can't load the bootloader by its own
but from external means it boots up
You could use the Partition 1 of Disk 2 as your main Menu and add WBM of Disk 1 Partiton 1 via Os-Prober
Sorry, I just took a break
Hah? Sounds spooky
Okay I'm in the UEFI Shell now
[Reply to:](#1236648276196069478 message) Hah? Sounds spooky
I did
huh, what did it show?
she's sad that she can't explain
so basically
What we do is
- install Linux
- open UEFI shell from the install USB
- type in
bcfg boot add 9 FS1:\EFI\BOOT\BOOTX64.EFI "Linux Boot Manager" - Exit UEFI shell with
reset -w - Observe (Linux disappears)
One question? Are you both facing that issue?
Why would you add the bootmgr via UEFI shell?
Isnt it easier if you just add it via os-prober?
Yes
[Reply to:](#1236648276196069478 message) One question? Are you both facing that issue?
Cause this one simply doesn't work
[Reply to:](#1236648276196069478 message) Isnt it easier if you just add it via os-prober?
HAH? Okay
Why not? Are there any errors?
no
[Reply to:](#1236648276196069478 message) Why not? Are there any errors?
Yk you gotta edit the grub.cfg and edit it?
hmm didn't try that one
Oh lmao
So you gotta install Os-prober
Then you have to edit the grub file in /etc/default/grub
uncomment the last line
After that one, update grub (grub-mkconfig -o /boot/grub/grub.cfg
and vuala, you added your bootloader
i have os-prober ig
or I don't have GRUB installed at all
it's either
I don't remember which one
I'm sorry
Uncomment: GRUB_DISABLE_OS_PROBER=false
in /etc/default/grub
Make sure grub is installed b4.
After that run:
lmk if that worked
The system doesn't use GRUB
[Reply to:](#1236648276196069478 message) lmk if that worked
That's what I see
Systemd-boot
[Reply to:](#1236648276196069478 message) What else is it using then?
And Valiant?
we use the same computer
Oh okay
Makes sense
Umm, I have never used systemd bootloader 😭
Sorry for wasting y'alls time
Let's reinstall for GRUB
it's okay
[Reply to:](#1236648276196069478 message) Sorry for wasting y'alls timr
I have never used OpenSusA nor systemd bootl.
But I can help you setting up grub (on arch)
But I think the cmd are pretty much the same
just reinstall grub
I did and it didn't work
[Reply to:](#1236648276196069478 message) just reinstall grub