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…
Hehehe, that’s what I call the “Diving Bell Approach”. Either remote via serial console over IP or local when greeted by the dreaded
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…