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

[Jay Michael]

I craft my boot device by hand.  I'm using files filched from some
Ubuntu distribution (so, GRUB2), lately booting with the ISO file.  I've
booted from an external (USB) hard disk, and from thumb drives.

     On my external hard drive, I copied vmlinuz and initrd to the ESP
(because on another machine, with Secure Boot enabled, the version of
GRUB2 I filched does not support NTFS filesystems, and I cannot insert
the appropriate module).  The ISO file is in a subdirectory of an NTFS
partition.  The GRUB2 item is:

set bdir=(${root})/boot
set fsd=/os/boot
menuentry "Ubuntu 20.04.2 64-bit via ISO" {
  set gfxpayload=keep
  set ubdir=${bdir}/ubuntu200402-64
  set isopath=${fsd}/ubuntu-20.04.2-desktop-amd64.iso
  linux	${ubdir}/vmlinuz  boot=casper  iso-scan/filename=${isopath} ignore_uuid fsck.mode=skip
  initrd ${ubdir}/initrd
}

     So, GRUB is told to load the kernel and initrd from the FAT-
formatted ESP, while the kernel is told to find the ISO file.

     I observed the same behavior with 20.04.1 as with 20.04.2.
     I observed the same behavior when booting from a thumb drive as when booting from a hard drive.

     I haven't tried to find a copy of "20.04".  Was there such a thing?
Or was 20.04.1 the first released version, the one referred to in all
those posts complaining about the automatic disk check?

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