[Bug 996454] Re: Recovery Mode starts in read-only, does not mount home folder, and hangs when trying to do something

[Steve Valliere]

/  is on /dev/sda1
/home  is on /dev/sdb1

If this happens elsewhere, it would be very important and if not, I'd
love to know what I did to cause it to happen for me.  So I posted a new
forum thread at
http://ubuntuforums.org/showthread.php?p=12129083#post12129083

The workaround is fine, but only AFTER one knows that it is needed.
When one does not expect the drives to be mounted and they do not show
as mounted, everything looks good so who would ever look for a "fix" to
the expected and [apparently] correct conditions?  That's why I agree
about starting the new thread.  I hope I wasn't too much bother here,
this seemed very related to what I saw, just inverted, as it were.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to friendly-recovery in Ubuntu.
https://bugs.launchpad.net/bugs/996454

Title:
  Recovery Mode starts in read-only, does not mount home folder, and
  hangs when trying to do something

Status in “friendly-recovery” package in Ubuntu:
  Confirmed

Bug description:
  Starting with 12.04, when I boot into Recovery Mode:

  1. The file-system is read-only.

  2. The home folder is not mounted (if on a separate partition).

  3. Choosing to check all disks or to start in low-res graphics mode
  asks to mount read-write but then appears to hang; Ctrl-C is required
  to get back to the menu.

  4. I also notice that on 11.04, Recovery Mode uses smaller text
  (taking advantage of the monitor's resolution), whereas 12.04 uses
  large text.

  What should happen:

  1. File-system read-write, or at least a *working* option to change to
  read-write.

  2. The home folder is mounted.

  3. Check all disks or start low-res graphics should do just that,
  instead of hanging.

  4. The text should use the available resolution of the monitor.

  It is as if the Recovery Mode has not been tested at all.

  (I cannot use ubuntu-bug to report the error, as it wants a specific
  package, which of course does not apply here.)

  System: Ubuntu 12.04 LTS 64-bit, fully updated.
  Related thread: http://ubuntuforums.org/showthread.php?t=1975474

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/996454/+subscriptions