So, I made my bootable EndevourOS image. I installed it on my secondary SSD, while I have Win11 on my primary SSD (need it for my job).

When I installed it I booted it up and everything was ok. A bit confusing, but ok.

Wanted to get into Windows again because I needed to work on something for a design (Adobe programs), next thing I know: my computer isn’t recognizing my Windows drive…

It’s there. I can see it on the “disks” app on EndevourOS, I can mount the disk and even see my files in there. But it just won’t boot.

Read the documentation and it mentions an “os-prober”, that I needed to change GRUB_DISABLE_OS_PROBER=false in the etc/default/drub file… I don’t have that file anywhere in my system…

I installed os-prober, nothing. I searched any other folder with a similar name and checked files… The only file with a mention of os-prober is grub.d that says “if GRUB_DISABLE_OS_PROBER=xtrue then random warning”, but that is a set of instructions (i think), not the actual file.

I don’t think I should have tried EOS/Arch when I’ve been learning Linux for only 2 days, can anybody help me with this? Thank you for any answers in advance.

  • @Sentau@feddit.de
    3•1 year ago

    https://wiki.archlinux.org/title/systemd-boot#Boot_from_another_disk

    It seems that systemd-boot does not autodetect the windows boot option if the files associated with windows boot are on another drive.

    Edit : Though from your other comment reply I think there something broken in your windows install. You can try to fix it using a windows installation media or just reinstall windows as the other poster told.

    Edit 2 : A guide specifically for EndeavourOS https://forum.endeavouros.com/t/tutorial-add-a-systemd-boot-loader-menu-entry-for-a-windows-installation-using-a-separate-esp-partition/37431

    • redimkOP
      2•1 year ago

      This is what I think happened that I wrote on another comment:

      It’s weird, but I had Fedora installed on my secondary SSD. Apparently when I did a clean Windows install, it installed in the primary SSD but took a part of Fedora on the secondary SSD as a Windows EFI partition. Then, when I installed EOS I selected “erase the disk” for the secondary SSD. I think it erased that EFI partition and I couldn’t go back to windows, but since the primary SSD still had my files I could still see them. To be honest, something like that never happened before so I’m not even sure of what I’m saying.

      Tbh I’m not even sure if that’s what happened, I just didn’t find an easy solution apart from starting over.