[Bug 1807537] [NEW] failure in fsck option of advanced boot

[Kevin O'Gorman]

Public bug reported:

I ran into this first on a 16.04.5 install I have.  I just retried it on
a new laptop with 18.04.1 with the same result.

When booting, I chose the advanced form, the rescue variant, and tried
to use its fsck option.  This failed almost immediately.  I'm attaching
a photo of the screen showing the error, but the text is

/lib/recovery-mode/recovery-menu: line 80: /etc/default/rcS: No such
file or directory

/dev/nvme0n1p5 is mounted.

e2fsck: Cannot continue, aborting.

--------------------------------------------------------
Thus there seems to be no point in having this fsck option because it is doomed to fail.  Well, at least in the absence of further guidance about how to use this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: grub-common 2.02-2ubuntu8.9
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Sat Dec  8 13:52:47 2018
InstallationDate: Installed on 2018-10-18 (51 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: grub2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "iPhone photo of the screen on failure."
   https://bugs.launchpad.net/bugs/1807537/+attachment/5220436/+files/20181208_214340175_iOS.jpg

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

Title:
  failure in fsck option of advanced boot

Status in grub2 package in Ubuntu:
  New

Bug description:
  I ran into this first on a 16.04.5 install I have.  I just retried it
  on a new laptop with 18.04.1 with the same result.

  When booting, I chose the advanced form, the rescue variant, and tried
  to use its fsck option.  This failed almost immediately.  I'm
  attaching a photo of the screen showing the error, but the text is

  /lib/recovery-mode/recovery-menu: line 80: /etc/default/rcS: No such
  file or directory

  /dev/nvme0n1p5 is mounted.

  e2fsck: Cannot continue, aborting.

  --------------------------------------------------------
  Thus there seems to be no point in having this fsck option because it is doomed to fail.  Well, at least in the absence of further guidance about how to use this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: grub-common 2.02-2ubuntu8.9
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Sat Dec  8 13:52:47 2018
  InstallationDate: Installed on 2018-10-18 (51 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1807537/+subscriptions