[Bug 1878449] [NEW] 20.04's desktop installer always fsck's when starting

[shemgp]

Public bug reported:

I used the Ubuntu 20.04 desktop amd64 installer in a USB to fix the
booting of my server, and it took time since it fsck'ed the USB thumb
drive that I flashed it into.

So I thought, maybe I just unplugged the thing to quickly and didn't
unmount it that's why. So I reflashed/recreated the boot disk and this
time I unmounted it properly but it still did the fsck.

So then I installed a VM with it, and it did fsck again. So now I
realized that it's a bug. That's why I filed this.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu May 14 00:27:01 2020
EcryptfsInUse: Yes
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
InstallationDate: Installed on 2015-09-28 (1689 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: ubiquity
UpgradeStatus: Upgraded to focal on 2020-03-03 (71 days ago)

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


** Tags: amd64 apport-bug focal ubiquity-2.21.25

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

Title:
  20.04's desktop installer always fsck's when starting

Status in ubiquity package in Ubuntu:
  New

Bug description:
  I used the Ubuntu 20.04 desktop amd64 installer in a USB to fix the
  booting of my server, and it took time since it fsck'ed the USB thumb
  drive that I flashed it into.

  So I thought, maybe I just unplugged the thing to quickly and didn't
  unmount it that's why. So I reflashed/recreated the boot disk and this
  time I unmounted it properly but it still did the fsck.

  So then I installed a VM with it, and it did fsck again. So now I
  realized that it's a bug. That's why I filed this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 00:27:01 2020
  EcryptfsInUse: Yes
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
  InstallationDate: Installed on 2015-09-28 (1689 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to focal on 2020-03-03 (71 days ago)

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