this post was submitted on 28 Oct 2025
502 points (98.5% liked)

Linux Memes

996 readers
1 users here now

A community for posting memes relating to linux!

Also check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP



founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] InnerScientist@lemmy.world 33 points 1 week ago* (last edited 1 week ago) (2 children)

I once redid the whole bootloader remotely.

I had a remote server that wasn't luks encrypted because I didn't do that some 3 years ago when setting it up.

So naturally I did the sane thing and kexec a live environment with ssh and a wireguard client, did an in-place encryption of the software raid disks, set up remote unlocking with VPN and rebooted.

And I still can't believe that it actually reconnected after that.

[–] b_tr3e@feddit.org 1 points 5 days ago

Hehehe, that's what I call the "Diving Bell Approach". Either remote via serial console over IP or local when greeted by the dreaded

GRUB:>

prompt. Which means you really fucked up your boot sequence. Ususally happens with multi-disk machines and complex LVM/RAID setups. Which escalates the plain "fuck up" to "real fuck up" state. You'd better have a second machine or a printout of GRUB's excessive documentation with the hard to find but essential parts highlighted. There are ways to find the partition to boot and even ways to "manually" boot the right kernel, initrd-image and get the latter to mount the right root partition - even if it's on encrypted LVM, but be sure to have enough oxygen, keep your decompression times and have enough batteries for your flashlight...