[Bug 868755] [NEW] Always starts ro (read-only)

komputes 868755 at bugs.launchpad.net
Wed Oct 5 22:07:59 UTC 2011


Public bug reported:

Why does friendly-recovery assume I am running it at boot time in ro? I
don't understand what prompted this change. In the rare occasion that
systems need to be mounted ro, shouldn't that be done as a kernel boot
parameter?

Running /lib/friendly-recovery/recovery-menu from gnome-terminal, I
still have to do remount. It doesn't detect that the root filesystem is
already mounted.

>From what I understand ro is mounted so that fsck can check the disk
without modifying it. AFAIK fsck should run automatically in ro if dirty
filesystems were detected and issues are not correctable (or if it had
passed a number of boots without a check, then preform a check) so why
is this being done every time?

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: friendly-recovery 0.2.18
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Wed Oct  5 17:33:22 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
PackageArchitecture: all
SourcePackage: friendly-recovery
UpgradeStatus: Upgraded to oneiric on 2011-10-04 (0 days ago)

** Affects: friendly-recovery (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: apport-bug i386 oneiric

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

Title:
  Always starts ro (read-only)

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

Bug description:
  Why does friendly-recovery assume I am running it at boot time in ro?
  I don't understand what prompted this change. In the rare occasion
  that systems need to be mounted ro, shouldn't that be done as a kernel
  boot parameter?

  Running /lib/friendly-recovery/recovery-menu from gnome-terminal, I
  still have to do remount. It doesn't detect that the root filesystem
  is already mounted.

  From what I understand ro is mounted so that fsck can check the disk
  without modifying it. AFAIK fsck should run automatically in ro if
  dirty filesystems were detected and issues are not correctable (or if
  it had passed a number of boots without a check, then preform a check)
  so why is this being done every time?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: friendly-recovery 0.2.18
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu2
  Architecture: i386
  Date: Wed Oct  5 17:33:22 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110817)
  PackageArchitecture: all
  SourcePackage: friendly-recovery
  UpgradeStatus: Upgraded to oneiric on 2011-10-04 (0 days ago)

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




More information about the foundations-bugs mailing list