this post was submitted on 24 Jan 2025
491 points (96.2% liked)
Actually Infuriating
348 readers
134 users here now
Community Rules:
Be Civil
Please treat others with decency. No bigotry (disparaging comments about any race, ethnicity, religion, gender, sexuality, nationality, ability, age, ). Personal attacks and bad-faith argumentation are not allowed.
Content should be actually infuriating
Politics and news are allowed, as well as everyday life. However, please consider posting in partner communities below if it is a better fit.
Mark NSFW/NSFL posts
Please mark anything distressing (death, gore, etc.) as NSFW and clearly label it in the title.
Keep it Legal and Moral
No promoting violence, DOXXing, brigading, harassment, misinformation, spam, etc.
Partner Communities
- Mildly Infuriating
- Furiously Infuriating
- Memes
- Political Memes
- Lemmy Shitpost
- Not The Onion
- You Should Know
- Lemmy Be Wholesome
founded 1 week ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
FWIW dual booting from the same physical drive is never a good idea in my experience. Even Linux-Linux dual booting is just asking for problems when one of them updates the grub configs and messes it up for the other.
Save yourself some sanity and move your Windows install to a new drive.
and when one drive fails you can boot from the other drive and repair your system
I tried to do a dual boot from 2 hard drives (windows main), had to restore the Linux side early on, using its built in restore tool, and the computer would not boot after beyond a black screen without pulling the battery for the BIOS off the motherboard. No boot menus or firmware or bios menus were accessible until I did that.
That's the worst oh shit did I fully break my computer moment ever.
One if my laptops only has 1 bay for a drive unfortunately. Currently going through the motion OP describes. Updating Windows and repairing the bootloader. It's still MBR, not uefi, too.
Does it have an optical disk drive? You could replace that with an HDD caddy if you really want an extra disk
That's actually why i don't auto-mount ~~
/bin
~~/boot
in linux. It only messes things up when it updates the kernel.As someone who just started using Linux regularly, this seems bonkers to me.
Unless you're building your own kernel and compiling apps from scratch, why would anything in /bin break?
Sorry i meant
/boot
, on some systems it seems to link to the EFI partition, so when you have a dual-boot setup, updating the kernel breaks the other system's kernel or something.. I just checked and it seems to not be an issue on my current setup, as they aren't links to the EFI partition.Oh, that makes more sense.
Still, from my tests with Mint, it looks like it probes other disks and partitions when updating grub, and reinstalls it correctly. But I suppose there are cases where the probe could fail and you'd have to boot from the grub prompt.
yeah it's more of a hypothetical worry, i guess. since every system seems to handle boot a bit differently (unfortunately), it's difficult to get a definite answer to that.
I personally love the UEFI boot system, but it's not typically directly used. Instead, some complicated grub setup is often in place. That makes it a bit of a complicated question.
This is really the advice to take. I tried dual boot and went back to Windows due to it nuking grub.
Tried again after buying a new SSD and haven't had an issues since
this - there needs to be a standard for all installers to get behind