• tomkatt@lemmy.worldEnglish
    3·
    25 days ago

    Important Edit

    The information below applies to emergency mode boot when grub is intact but OS isn’t booting. It doesn’t apply to grub rescue. Sorry about that folks, I screwed up here and don’t wanna misinform.

    —————-

    Protip: If you see this error, press”e” on grub boot to edit your commands and add the following to the end of the kernel line in grub:

    fsck.repair=yes

    Then boot.

    Fixes the issue like 90% of the time.

    • brokenlcd@feddit.it
      3·
      25 days ago

      dd would like to have a word about that… But still, another tool in the arsenal is always useful.

      Thanks for the tip.

      • tomkatt@lemmy.worldEnglish
        0·
        25 days ago

        It’s only needed is the OS isn’t booting. Running a repair every boot is not needed.

        • Moshpirit@lemmy.world
          1·
          24 days ago

          Why not adding some conditional to enable it? Like fsck.rescue = $grub-error. If grub-error = yes, then fsck.rescue = yes too and then try again. If keeps failing then show the message. Otherwise it keeps being no and boot as usual.

    • TheGreatSnacku@lemm.eeEnglish
      0·
      25 days ago

      If it’s going to grub rescue then that’s before it can even get to the grub menu (thus no kernel line at this point). It’s usually easiest to boot to live/rescue ISO and reinstall grub. Sometimes you can manually load grub modules from lib to manually boot from the grub rescue shell to the normal grub shell, but that’s more advanced.

      • tomkatt@lemmy.worldEnglish
        0·
        25 days ago

        Not true, it’s grub rescue, appears after grub if the OS can’t boot. I’ve encountered this countless times at work over the years in customer environments.

        • TheGreatSnacku@lemm.eeEnglish
          1·
          25 days ago

          This is false and there’s a simple way to show it.

          Remove the grub.cfg file and the system will boot to the grub prompt (not grub rescue). You can manually boot past this by inputting the Linux and initramfs lines.

          Then test again but leave grub.cfg intact. Remove an important module like normal.mod and test booting - system will land at grub rescue instead of the normal grub prompt.

          Once you test it would be good if you edit your posts so that you aren’t sharing bad information with others

          • tomkatt@lemmy.worldEnglish
            1·
            25 days ago

            Well shit. You’re right, I’m mixing up grub rescue and emergency mode. Yeah, you would need a USB rescue disk to fix this most likely.

            My bad, I’ll update the original comment to avoid confusion.

    • addie@feddit.uk
      1·
      25 days ago

      After having used Grub for about twenty years (eek) I was uncertain about the alternatives, but systemd-boot is absurdly better. Much better configuration, much better documentation, fixes a while pile of bugs that Grub team had as “won’t fix” for years and years. No reason to ever go back.

    • cm0002@lemmy.cafeOPEnglish
      1·
      25 days ago

      Usually anything where the BIOS can find and boot Grub itself but Grub can’t finish the boot chain for whatever reason, like /boot being on a separate partition and your main partition gets corrupted or something

  • communism@lemmy.ml
    1·
    25 days ago

    In general if your OS is intact you can just boot into a live USB and chroot and reinstall grub, worst case scenario if you can’t fix it in a less destructive way.

  • 🇰 🌀 🇱 🇦 🇳 🇦 🇰 🇮 @pawb.socialEnglish
    1·
    24 days ago

    I remember my dad telling me a joke about FSCK and the reason it looks like a censored form of “FUCK” is because if you ever had to use it, you were basically fucked.

    Personally, I had never had a problem with it. It just repaired errors on the disk or at least searched for them, IIRC. It’s been a long ass time since I even heard the joke, let alone used the tool. This just reminded me of it.