I now see this when i boot up. I just restarted my pc and now i get this.

  • einkorn@feddit.de
    1101·
    7 months ago

    Pretty unhelpful responses so far. Enter

    exit

    to exit the current screen and return to a selection of installed OS/Kernels. You should be able to boot normally from there on. Once logged in, try

    update-grub

    which should repair your bootloader config.

  • pastermil
    46·
    7 months ago

    Your system is fucked, that’s what happened.

    More specifically, it cannot find the config file (/boot/grub/grub.cfg) it uses to load the menu & stuff to boot.

    Usually it means one (or more) of:

    • the grub.cfg got moved/deleted
    • grub directory got moved/deleted
    • /boot directory got moved/deleted
    • boot partition failed to load
  • Count Regal Inkwell@pawb.social
    23·
    7 months ago

    Welcome, this is the Linux user equivalent of popping your cherry.

    You have a few options, but the easiest is to just use a rescue thing like Rescatux on a USB drive that automates most of the process. If you haven’t the means of flashing a USB drive (like another computer) but still have your linux installation USB drive, most distros offer a “rescue existing install” option somewhere in their installer/liveUSB. But you’ll have to search around.

  • mvirts@lemmy.world
    17·
    7 months ago

    Dont forget to play around with grub while its like this. Tab completion works great, try ‘(’ the press tab to maybe see your disks as grub sees them. I think help lists commands and most of them are harmless.

    • u/lukmly013 💾 (lemmy.sdf.org)@lemmy.sdf.orgEnglish
      184·
      7 months ago

      Dont forget to play around with grub while its like this. Tab completion works great, try ‘(’ the press tab to maybe see your disks as grub sees them.

      Is this a joke like sudo rm -rf --no-preserve-root / to speed up the PC? Because it kinda sounds that way.

      • caseyweederman@lemmy.ca
        21·
        7 months ago

        No. It’s a little shell that you can explore with commands. If needed, you can mount and boot your OS just with commands in the grub shell.

        • Atemu@lemmy.ml
          3·
          7 months ago

          The process for this is that you want to set your prefix to the /boot partition in the (hd1, gpt1) syntax (use ls) and then load the “normal” module. From then on, you should have regular GRUB again and should be able to boot your OS to properly fix GRUB.

    • Trainguyrom@reddthat.comEnglish
      2·
      7 months ago

      Sounds like you’d love configuring network hardware then! You can get a peek into that in Linux with frr since it has a mode to configure your linux machine like you’ve just SSHed into a Catalyst switch, or just hop on ebay and buy a 20 year old switch for peanuts

      • Oisteink@feddit.nl
        10·
        7 months ago

        Have you tried turning it off and back on again?

        If that doesn’t help boot with a live-cd or rescue, and check that your grub config points to a valid kernel.

        Your hdd might be the culprit but it’s very hard to say from that screen. Maybe the one previously that can show your boot command

  • MsFlammkuchen@lemmy.blahaj.zone
    9·
    7 months ago

    Can you give a little more background info? What distro are you using, are you dual booting, is it a new install, did you make changes to your kernel, your partitions or grub before that?

    While it’s clear that grub couldn’t find a kernel to boot, we need these Infos to help you find a solution.

    • joel_feila@lemmy.worldOP
      71·
      7 months ago

      Im using kde I did not even use my pc the last few days I came home it froze and when i rebooted i got this I do NOT have any duel boot

      • marcos@lemmy.world
        101·
        7 months ago

        You may want to replace the disk on that computer after you fix your boot. (As people said, with a recovery drive, probably the same one you use to install.)

        After your computer is back, get a SMART client (like smartmontools) and check your disk status.

  • callyral [he/they]@pawb.socialEnglish
    4·
    7 months ago

    Burn a live Linux system onto a USB (can be one with just a terminal, like Arch Linux). If you don’t have another computer to plug the USB into, this can be done on an Android phone using EtchDroid.

    Then, boot from that USB and mount your main filesystem. Inside of the Live system, chroot into the mounted filesystem and run sudo grub-mkconfig -o /boot/grub/grub.cfg which should fix the bootloader.

    After that, you can just exit the USB system and return back to your OS which should boot now.

    (If you don’t know how to mount a filesystem or chroot, I would explain but I forgot how to do it. If someone else could explain that would be neat)