[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check

Jay Michael 1875548 at bugs.launchpad.net
Sun Feb 7 06:55:14 UTC 2021


Forget "quiet", it's whether "fsck.mode=skip" is the last thing on
the kernel command line.

     There is no disk check if there is something after
"fsck.mode=skip".  I tried "quiet".  Then I tried "nomodeset" instead.

     I tried putting a blank at the end of the line.  That was *not*
enough to make the "fsck" stop the disk check.  I was using the GRUB2
editor, so maybe it would have worked if I really added a blank at the
end of the line in the grub.cfg file.

     Also, Ctrl-C does *not* abort the disk check.  Given the way the
display crawled through a flock of files before saying it was on
squashfs, I'm pretty sure I hit the Ctrl-C before it had started on
squashfs -- It just did not pay attention.

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

Title:
  Its not easy to determine how to skip the filesystem check

Status in casper package in Ubuntu:
  Fix Released

Bug description:
  I see that Live Ubuntu 20.04 is plagued by disk checking on boot.

  Not just with Live USB but with Persistent USB also.

  If not fast enough to cancel with ctl-c it starts on
  filesystem.squashfs and runs until over 90% complete.

  Very irritating. There have been quite a few complaints on Ask Ubuntu
  already.

  If it was just a run once it would not be so bad.

  Is there some way to get rid of this or is it a bug we have to live
  with?

  Perusing Ask Ubuntu everyday for many years I have never seen anybody
  ask for such a feature.

  A run once filesystem check might have its uses on a Live installer
  drive but is not needed on a Persistent utility drive.

  The only alternative I see is to use a Full install USB drive were
  automatic disk checking is not run.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CasperVersion: 1.445
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 28 06:07:32 2020
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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



More information about the foundations-bugs mailing list