this post was submitted on 07 Mar 2024
381 points (95.7% liked)

linuxmemes

20761 readers
1771 users here now

I use Arch btw

Sister communities:

Community rules

  1. Follow the site-wide rules and code of conduct
  2. Be civil
  3. Post Linux-related content
  4. No recent reposts

Please report posts and comments that break these rules!

founded 1 year ago
MODERATORS
poopsmith@lemmy.world
zephyr@lemmy.world
381
I know that it's rolling release, but 4 times this year seems a bit much (lemmy.world)
submitted 6 months ago by bali10050@lemmy.world to c/linuxmemes@lemmy.world
102 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] ulterno@lemmy.kde.social 4 points 6 months ago* (last edited 6 months ago)

A grub breaking thingy happened to me too.
I was saved by having multiboot, with every OS having their own GRUB version installed. (just selected one using the motherboard's interface)

The problem occurred when, after pacman -Syu, I read notes in the output, one of which hinted I would want to update GRUB and went - "Sure, I'll try the new GRUB update" and ran GRUB update.

When it didn't startup after a restart, I just used the debian's GRUB to login to the OS in question, downgraded GRUB, reinstalled GRUB and then ran pacman -Syu again.

I feel like mine wasn't the problem instance that goes on around the web, mostly because:

  1. None of the mentioned fixes worked in my case.
  2. I feel like people won't go out of their way to update GRUB most of the time.