What bootloader have you choosen during install?
Which option did you select from the options in the picture (keep in mind that systemd-boot is the default in case you did not change this setting)?
this post was submitted on 18 Oct 2023
36 points (92.9% liked)
Linux
48069 readers
772 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
I chose sysremd, I didn't have time to fix the issue as I needed my laptop for work so I just did a clean install of everything once again. I think I will keep trying Fedora but I will read the documentation of EOS first so I can understand what I'm doing, I can't afford to make the same mistake again lol. I think what happened is that I accidentally erased the Windows EFI partition somehow and that's why it was not going in.
Is there an actual difference between those? Is one better than the other or it's just the OS giving options?
Is there an actual difference between those? Is one better than the other or it's just the OS giving options?
I am not a power user so I dont know much. From what I gather l, grub is more configurable and also easier to configure but is also more likely to break. Systemd-boot on other hand is more robust from what I read but less configurable and harder to configure. You can do things like set booting into btrfs snapshot using grub that I think you can't with systemd-boot. Again i am no expert so parts of this might be outdated or wrong. Better to ask a more experienced user
So wait, what happens if you (obviously) turn off the computer, unplug the second ssd, then turn on the computer? Try that and report back.
Yes OP try this and report back. Might tell us if something in the windows install is broken
While I was trying to fix the issue all day, this comment is one of the things I tried, but when my laptop started, it just said "checking media........ fail", then getting reset into an endless loop. I said it in other comments but I think I erased an EFI partition that I shouldn't have, I think Windows took part of my secondary SSD somehow.
This is a feature, not a bug. You have been freed from Windows!
I wish, I still need to use Adobe products for my job, not even sure if I can install Adobe products in Linux yet, I'm still learning haha!
hi, I think EOS uses systemd-boot as a default bootloader. so grub may not matter. I don’t have much experience with systemd-boot, but for now, you could just try and boot from the primary windows drive by pressing the BIOS key and changing the boot order (or using your motherboards‘ external drive boot button)this key is different for many motherboards, so you should check google for yours. As for systemd-boot, I don’t have much experience so I’d either google (specifying the two drives) or ask gpt. Good luck!
After reading all these comments I just decided to format all my drives and start over. I made the mistake of installing EndevourOS at 12am when the next day I had to use Windows for my job! I did enter BIOS and changed the order but not even my BIOS recognized the OS, it just said "checking media........ fail" and it fell into a permanent loop. What I said in another comment was that I thought this had happened:
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.
I'm not even sure if that's what happened, as I'm still not an expert in these things, but when I erased the secondary SSD there was a "EFI partition" I had not seen before.
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
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.
Consider boosting up from a live Linux(for example Ubuntu) and using boot-repair. I have had similar problems and managed to at least get the Windows boot going again.
Also are you using UEFI or MBR?
I was using UEFI I think? I used Rufus to make the bootable flash drive and it just gave me either MBR or GPT, when I selected GPT it showed me the UEFI option to the right (iirc). I spent all day seeing these comments and at the end of the day I had to delete everything in my hard drives and start over again...
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.
Oof. Sounds really stressful. I hope you figure this out. Try installing refind and running “refind-install”. It searches your system for bootable disks and gives you a big menu to choose from.
At the end I just erased all my disks and started all over again :( figured it was the easiest and quickest way to deal with it because I urgently needed W11 for my job, I'll just be more ready for next time and read more about the OS before making a move so sudden like that
Shit, it'd take me days if not weeks to get my windows install set back to how I have it. Well, I'm guessing you have a better system than I for reseting your OS from scratch.
USE. SYSTEMD-BOOT. ALREADY.