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
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-installwith appropriate parameters. Finally, runupdate-gruborgrub-mkconfigto 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.
Can you link me to the commands to reinstall the kernel? Thank you for very much your help[
probably something like
apt reinstall linux-image-...To find …, run
apt list --installed | grep linux-imageand pick oneEdit: also if need current kernel, can see booted kernel name using
uname -aCan’t find an article for it at the moment, but I can tell you real quick how I would’ve done it.
Use
aptitudeand 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).
Ok thanks again for all the help.
I used aptitude to reinstall the kernel, L, g, g
Ran Grub-install /dev/nvme1n1
Ran update-grub
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
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:
Just rebooted and it worked flawlessly!!
You are fucking awesome thank you again. Really made my weekend.
Glad to hear that! You’re welcome!
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.
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 rebootCommand not found
sudo shutdownCommand not found
But it sat there with a blinking cursor on the terminal
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”?
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
/sysand/devcan brick your computer. So it’s not a great idea.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.
It sounded like you were testing the (one and only) backup in a live environment is all.
Not to victim blame but you did put in --no-preserve-root. You had to read those instructions.😄