Hi all,

I’m having a bad day and did something colossally stupid, deleting everything from /boot/.

The system is still running. What do you think my best course of action is?

My current idea is to create a timeshift backup, reinstall debian from USB, then restore from backup in timeshift

If this won’t work or you have a better idea I would really appreciate your advice.

Thanks in advance

  • pastermil@sh.itjust.worksEnglish
    29·
    3 months ago

    Your system would continue to work as long as you don’t turn it off. So no matter what you do, keep it on until you restored your /boot

    Recovering it should be straightforward, assuming you didn’t put custom files directly to /boot.

    Just reinstall the linux kernels using apt. Then manually run grub-install with appropriate parameters. Finally, run update-grub or grub-mkconfig to recreate the grub config.

    If the system is turned off, you can use live USB and chroot to it to properly install the kernel packages.

      • far_university190@feddit.orgEnglish
        10·
        3 months ago

        probably something like apt reinstall linux-image-...

        To find …, run apt list --installed | grep linux-image and pick one

        Edit: also if need current kernel, can see booted kernel name using uname -a

      • pastermil@sh.itjust.worksEnglish
        5·
        3 months ago

        Can’t find an article for it at the moment, but I can tell you real quick how I would’ve done it.

        Use aptitude and look for linux-image-amd64 or something under Installed -> kernel. The exact name might be a bit different.

        View the package and look under the Version and check out the one that’s marked ‘i’ (for installed). Select that package and mark it to reinstall (shortcut ‘L’).

        Then finally execute it (shortcut ‘g’ and then ‘g’ again).

        • Negligent_Embassy@links.hackliberty.orgOPEnglish
          2·
          3 months ago

          Ok thanks again for all the help.

          1. I used aptitude to reinstall the kernel, L, g, g

          2. Ran Grub-install /dev/nvme1n1

          3. Ran update-grub

          4. I installed grub-emu to test and am greeted with this error

          https://dump.li/image/get/16c4f87164d630a5.png

          Brand new to this tool so apologies if I’m interpreting it wrong.

          Still waiting on data to backup but I’m scared to reboot now. Any thoughts?

          The boot drive has LUKS FDE if that could be what’s confusing it

          • pastermil@sh.itjust.worksEnglish
            3·
            3 months ago

            Not sure if this is a good way to test as it cannot seem to recognize even the most basic command like linux & initrd.

            If I were you, I’d just restart, with a liveUSB ready in case it turns out to be unbootable.

            Perhaps just a bit to make sure before rebooting:

            • you can see the linux kernel you just installed in the /boot directory
            • /boot/grub/ directory exist
            • you’re using the correct grub-install command, depending on whether you’re using legacy BIOS or UEFI
    • masterofn001@lemmy.caEnglish
      1·
      3 months ago

      I’ve only ever used grub with bios/mbr or a BIOS/gpt (with grub bios partition).

      No clue about efi/uefi.

      This is the simplest method I can think of.

      The arch wiki, however, is, as always, a great source of info:

      https://wiki.archlinux.org/title/GRUB

      **Linux is amazing in it’s ability to keep working even when you accidentally all the things.

      I once sudo apt removed mint-x-icons or something which, for whatever reason, also needed to remove cinnamon. As in cinnamon the entire DE.

      I realised what I had done as I watched the terminal.
      #%&@! panic.
      …
      reinstalled.
      joy.

      • dis_honestfamiliar@lemmy.worldEnglish
        5·
        3 months ago

        Linux is amazing in it’s ability to keep working even when you accidentally all the things.

        Annoyingly so. I once made a backup. Then to confirm it would restore the system, I deleted everything on root path. as in /

        It did as told.

        OK let’s reboot and verify system.

        Sudo reboot

        Command not found

        sudo shutdown

        Command not found

        But it sat there with a blinking cursor on the terminal

        • Plopp@lemmy.worldEnglish
          5·
          3 months ago

          Then to confirm it would restore the system, I deleted everything on root path. as in /

          I’m a noob, so forgive me if I’m being very ignorant here, but how on earth could that be a good idea? It sounds like “in order to see if I’ve installed these airbags correctly I shall now crash head first into this concrete bridge foundation at max speed”?

          • SteveTech@programming.devEnglish
            4·
            3 months ago

            I’m assuming it’s a fresh install, so nothing of value was lost if the restore failed. But also I’ve heard attempting to delete things in /sys and /dev can brick your computer. So it’s not a great idea.

          • dis_honestfamiliar@lemmy.worldEnglish
            1·
            3 months ago

            I’m not so sure your analogy works. Unless you are testing to see how fast you can bring a new test dummy into production. Or you are testing to see how fast you can install new airbags with blemishes and all.

            It gave me a reason to finally run the command that <insert something amazing here> by recursively deleting everything.

            • Plopp@lemmy.worldEnglish
              1·
              3 months ago

              It sounded like you were testing the (one and only) backup in a live environment is all.

        • nexussapphire@lemm.eeEnglish
          1·
          3 months ago

          Not to victim blame but you did put in --no-preserve-root. You had to read those instructions.😄