provide emergency path for when entire initscripts are broken

Bug #549682 reported by Joshua
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
grub2 (Ubuntu)
Expired
Undecided
Unassigned

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.

Tags: patch
Revision history for this message
Joshua (joshudson) wrote :
Philip Muškovac (yofel)
tags: added: patch
Revision history for this message
Marcus Tomlinson (marcustomlinson) wrote :

This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue on a maintained version of Ubuntu please let us know.

Changed in grub2 (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for grub2 (Ubuntu) because there has been no activity for 60 days.]

Changed in grub2 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.