• Nisaea@lemmy.sdf.org
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        8 months ago

        I was among one of the grub fiasco victims. Thank goodness they rolled it back pretty fast and I knew how to chroot.

      • ulterno@lemmy.kde.social
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        8 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.
      • I have not experienced it but half of the arch users on reddit seem to have experienced it. Also it’s not a continuous problem but rather a problem with a certain arch and grub version. However the fact it happened once (to many people) means it can happen a second time

      • Skye@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 months ago

        Arch breaking grub has happened to me twice. Second time I couldn’t even recover the install.

        You learn a lot of good practices by using arch, eg a separate home partitjon, git repositories for your config files, maintaining a clean package tree etc. Installing Arch is also really useful for noobs like me to learn some Linux basics.

        I use Fedora, btw.