[Bug 549682] Re: provide emergency path for when entire initscripts are broken
Launchpad Bug Tracker
549682 at bugs.launchpad.net
Tue May 5 05:33:19 UTC 2020
[Expired for grub2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/549682
Title:
provide emergency path for when entire initscripts are broken
Status in grub2 package in Ubuntu:
Expired
Bug description:
Binary package hint: grub-common
A couple of times I've taken a bad update that rendered the screen
unusable before the recovery prompt comes up.
Really fun to start sshd blind so I can remote in from another
computer and fix it.
The only other generally working option is to keep a third boot path
from a known-good kernel that touches no bootscripts.
My particular solution was to modify /etc/grub.d/10_linux to generate
the third option. As you can see, it only functions if /etc/init.d
/emergency-shell exists and is executable. So, to enable, ln -s
/bin/sh /etc/init.d/emergency-shell and run update-grub.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/549682/+subscriptions
More information about the foundations-bugs
mailing list