failure in fsck option of advanced boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
friendly-recovery (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
grub2 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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-
/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
ProcVersionSign
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)
Changed in grub2 (Ubuntu): | |
assignee: | Marcos Nascimento (wstlmn) → nobody |
I had exactly the same problem. I'm running 18.10, grub2-common 2.02+dfsg1-5ubuntu8
If I go to root from the recovery menu, my root disk is already mounted, and umount says it is busy, so I can't fsck from there either.