41
Dual-booting is fine, but this kind of thing does happen.
Either "os-prober" isn't installed or /etc/default/grub has GRUB_DISABLE_OS_PROBER=false.
Fix those, then reinstall the bootloader.
os-prober was installed, but it was indeed disabled.
I went through the process of activating it and remaking the grub configuration. But it seems to not care about Windows, likely because, as stated in my post, it is on a separate physical drive. Probably some way to tell it to look there as well, but I don't know it. I might do some searching of my own later, right now I got shit to do. Booted into my laptop (which I keep with just windows because its ssd is too small for me to have any fun)
When I dual-boot it is always with a separate drive, less often does MS hose the bootloader in that situation. Normally it is findable. I dont recall havong to point it to anything.
I keep a usb boot drive with a number of images (ventoy), including "super grub boot disk" to get me out of these situations.
When I dual-boot it is always with a separate drive, less often does MS hose the bootloader in that situation. Normally it is findable. I dont recall havong to point it to anything.
I keep a usb boot drive with a number of images (ventoy), including "super grub boot disk" to get me out of these situations.
I dual booted for about two years before switching entirely over to Linux, and I found that using reFind as a bootloader instead of Grub was significantly less hassle. I'd suggest you check it out.
I have HEARD of reFind, but could not figure out how to use it. You got a good tutorial to link me up with?
I recall following the Arch wiki entry, but the official documentation is very useful too.
The easiest way I found to install it was to 1) Install refind through my distro's package manager and then 2) simply run the refind-install command in a terminal, which completely automates the process and sets reFind as the default bootloader for your machine.
If you want to tweak the appearance, icons, or the available boot entries on the reFind boot screen then just follow the official documentatuon.
The
Did you get killed mid writing the comment? That's ominous.
Anyway, I thank you for actual helpful comment instead of the others just calling me dumb for dual booting at all. :P
I'll see what I can do.
calling me dumb for dual booting at all
I keep saying this, but Linux users are probably the biggest obstacle standing in the way of Linux adoption.
One day those Linux people will learn that you’ll catch more flies with honey than you will with vinegar
🤷🏻♂️
Based on my nearly 30 years experience of using Linux (started with veeery early versions of Slackware) and interacting with Linux users on USENET, forums etc., I doubt it.
“I was harassed and bullied for being an outsider, unique, etc so now I will reflect that same sentiment and choose further fragmentation and gatekeeping because it makes me feel better”
One day we’ll recognize how valuable cooperation and staying in your own lane actually is. It can be tough
Some people in the community do get it. It's just that the "I got bullied in high school so now I like to yell at people in webforums" people are so very loud.
Oh for sure, didn’t mean to come off like I was generalizing the whole community (of which I’m a part of)
It’s just that, even if it’s a small minority of the community, they’re still yelling and screaming in the yard where people sitting on fences are getting scared off, from my perspective that is.
Nobody wants to be around assholes
Yeah, I've been at this since my dad first showed my 10 year old self Linux in the early aughts, and I don't think it's ever going to change.
I FIXED IT
Fucking hell that was a pain. And as most of the painful things in life, it was mostly self-inflicted.
I consider it the polite thing to make a report on what I did to fix things when I solve my problem in a tech support thread (in case someone is ever searching this, to avoid the xkcd scenario ) so I will do that now:
- First off, going into a Windows install media and running some commands, as described by @alphapuggle@programming.dev and @Babbiorsetto@lemmy.sdf.org did do the trick for reviving Windows.
- BUT, I am an idiot and I pointed Windows to the wrong thing, so it wiped out my Linux boot partition. O o p s i e . . .
- I was a bit stumped on what to do, and had actually flashed the USB drive (this idiot here only owns ONE USB drive) with the SUSE install media, fully intending to do a complete reinstall, but THEN,
- I realised that in the install media's menu, there is a "boot Linux system" menu, and entered it on a whim
- Sure enough, that found my existing OpenSUSE install and let me get into it.
- From there I just used YaST to re-install and re-configure grub
- Both Windows and Linux seem to be functioning now, yay
So, 85% "me being an idiot", but, the problem is solved. I thank everyone who made a comment.
Glad it's working! For the future, you might want to put ventoy on your singular USB. You can then put different ISOs on it, so you can have windows and Linux recovery on one keychain. Has saved my ass a number of times!
Oh that's cool
I will probably do that, yes.
Is the windows efi file still in your boot partition or did you format it on install or did you make a new second EFI partition? If you go into your BIOS can it find the EFI file to boot into Windows?
I did not touch the windows partitions, and that includes the microsoft reserved partition where the windows bootloader (supposedly, linux doesn't let me mount the MSR partition) is.
I only messed with the drive where Linux was installed and there, I made its own, separate /boot/efi partition.
Can you still boot into Windows without GRUB? Like through your bios menu. I've had it where a Linux installer will eat the EFI files for Windows.
If you need to fix your Windows EFI partition, and have a Windows install disk, boot it up and press Shift + F10 to open a command prompt (you may need Fn as well if youre on a laptop)
Run diskpart and list volume
You should have your Windows drive (should be labeled C, but can be mounted elsewhere in recovery. Keep in mind the letter it's mounted on) You're also going to want to look for a fat32 partition. Since windows is on a different drive, there should be two, one for Linux and one for Windows.
Pick one with select volume x where x is the volume number, and ensure you've selected the right one with list disk. There should be an asterisk next to the disk containing the selected volume.
Still in diskpart, you're going to want to mount that to a letter, I always choose N with assign letter n
Type exit to get out of diskpart
Next you're going to want to remove existing EFI files. Type N: to change to the N disk, and rmdir EFI\ /s (I'm doing this from memory, I believe this is the correct command to do so)
To regenerate the files, you're going to want to run
bcdboot C:\Windows /s N: /f ALL where C:\Windows is your Windows folder, N: is your efi partition, and ALL is the boot type (this installs both legacy and EFI files, you can set this to just EFI and be fine)
Windows should be good to boot, I'd boot it once to test. Then go into Linux & grub-install and update-grub. It should be able to find it on any installed drive, even unmounted. Check the output and you should see if it found it.
I cannot get into Windows in any way. I CAN get into Linux with no problem though. Anyway.
(as I said in my post--) My intention is to not use grub at all and to choose windows through my bios menu when I do need it. Which is what I had been doing for the past year.
It's just that its entry in the bios menu has disappeared.
In that case, these steps should work, but you can safely ignore the grub steps at the end. (I totally misread the NOT wanting to use grub part lol)
I managed to revive windows but now Linux doesn't show up, lmao
But I think I know what to do about that. Give me like 10 and I'll report back.
Your Linux install may be using the same EFI partition as your Windows disk, even though the filesystem is on another drive. Most installers prefer existing EFI partitions. You may have to modify your fstab file to use an EFI partition on your Linux drive instead, in which case they should remain separate and not mess with each other again.
Windows and linux are known to cause issues for each other. At minimum keep them seperaited on there on encrypted drives (I've found that drive encryption seems to conflict less for some odd reason).
But generaly do not dual boot unless you have to.
Edit, you can use chroot for this but if that doesn't work for you I hope you have backups.
But generaly do not dual boot unless you have to.
Thanks that doesn't help in the slightest :3
this post was submitted on 05 Apr 2024
41 points (97.7% liked)
techsupport
2475 readers
59 users here now
The Lemmy community will help you with your tech problems and questions about anything here. Do not be shy, we will try to help you.
If something works or if you find a solution to your problem let us know it will be greatly apreciated.
Rules: instance rules + stay on topic
Partnered communities:
founded 1 year ago
MODERATORS