[Bug 575469] Re: recovery mode mounts filesystems read-write rather than read-only

[Dave Vasilevsky]

A workaround to boot with the root mounted read-only is to edit the grub
command line so it includes "init=/bin/bash". Obviously non-ideal, but
it lets me run zerofree at least.

-- 
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/575469

Title:
  recovery mode mounts filesystems read-write rather than read-only

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

Bug description:
  Binary package hint: friendly-recovery

  In recovery mode, filesystems should probably be mounted read-only,
  since pending any problems they can safely be remounted read-write,
  while the reverse is not necessarily true.  This means that operations
  such as fsck, badblocks, zerofree, etc. are not possible without
  having to use a boot CD, and ensuring that any additional binaries are
  compatible.  One should assume that booting into recovery mode is
  either deliberate or has come about because of a problem.

  f-r 0.2.10 on lucid/2.6.32-21-generic