this post was submitted on 15 Oct 2024
597 points (98.9% liked)

Technology

59116 readers
3845 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] thermal_shock@lemmy.world 22 points 3 weeks ago (3 children)

might be better to separate drives, windows has been known to fuck up Linux partitions recently.

[–] MangoPenguin@lemmy.blahaj.zone 5 points 3 weeks ago (1 children)

Just keep regular full system images (as you should be anyways, as part of your 3-2-1 backup plan), and you'll be fine as you can just restore an image if everything gets broken.

[–] bollybing@lemmynsfw.com 4 points 3 weeks ago
[–] Katana314@lemmy.world 5 points 3 weeks ago (4 children)

This sounds like something I should be wary of, but it's the first I'm hearing of it. Any other info?

[–] rippersnapper@lemm.ee 9 points 3 weeks ago

It typically happens during updates. People have reported their grub screwing up. If you’re able I would honestly suggest separate drives

[–] PM_Your_Nudes_Please@lemmy.world 7 points 3 weeks ago* (last edited 3 weeks ago)

Microsoft took a big bite out of GRUB, which is the utility that your motherboard uses to dual boot OSes. A Windows update basically borked it and set Windows as the mandatory default OS. It basically makes it so your motherboard can’t properly identify your Linux install(s).

Luckily, you can fix it directly in Windows Command Prompt. But still, it’s a dirty trick that Microsoft has been using recently. Windows has historically been a bad neighbor for other OSes, (for instance, the Secure Boot Module is basically an attempt to make booting other OSes difficult,) but this was the first time in recent history that they have outright prevented another existing OS from booting.

[–] thermal_shock@lemmy.world -2 points 3 weeks ago

only anecdotes unfortunately.

[–] Mwa@lemm.ee 1 points 2 weeks ago

True once the day comes you can possibly do a raid config