Linux

48234 readers

619 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

I need help on EndevourOS, it's not recognizing the Windows boot and I don't understand how to solve it. (lemmy.dbzer0.com)

submitted 1 year ago by [email protected] to c/[email protected]

31 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 19 points 1 year ago (12 children)

The issue is that grub, the bootloader, doesn't know about windows and can't boot it. You can go into BIOS and change the boot order to boot windows without figuring this out as a stopgap.

I had to create /etc/default/grub as well on arch, so do that and rerun grub-mkconfig.

As usual, the arch wiki has a great but short guide on that: https://wiki.archlinux.org/title/GRUB#Detecting_other_operating_systems Read the entire article to get an idea of how to work with grub, then follow the windows section exactly.

[–] [email protected] 4 points 1 year ago (11 children)

That's the problem not even the bios is reading windows after the EOS installation. I keep changing the order of things but when I boot from the other SSD it just says "checking media" and then "failed" and it gets looped over and over again.

But I can still see the windows drives and partitions from EOS... It's the weirdest ting that I've seen... Would you recommend just doing a clean install of everything in that case?

[–] [email protected] 1 points 1 year ago (2 children)

The checking media message is your bios trying to boot from some external network drive. I had that issue for the longest, and I realized that I misunderstood how the boot order actually worked.

Try swapping your boot order around to opposite how it is currently? That's what I did and it solved my problem

[–] [email protected] 1 points 1 year ago (1 children)

I tried all orders, there were 2 Samsung SSDs (primary and secondary), and another one called "EFI" something... When I changed the order to SSD #1 it opened EndevourOS, when I changed to SSD #2 it said "checking media........ failed", and when I put the "EFI" as the first in the order, it just restarted and went again to EndevourOS. At the end, I had to do the easiest and fastest thing: start over.

I think that when I installed Win11, it took part of my Fedora partition somehow, I'm not even sure if that's what happened and if that is what actually happened I have no clue how it happened, but right before erasing my secondary SSD to install EOS, there was a mention of a Windows "EFI" partition there, even though I could still get into Fedora. So when I erased that, I think I erased something related to Windows that I shouldn't have erased

load more comments (8 replies)