"Press Ctrl+C to cancel all filesystem checks in process" on every boot

Bug #1946192 reported by Oleg Moiseichuk
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

I installed Kubuntu 20.04 on Latitude 5591 laptop using flash drive. Installation run without any issues but now on every boot I notice a message "Press Ctrl+C to cancel all filesystem checks in process" on the Plymouth screen with Kubuntu logo. It flashes quickly and disappears. I've got fast NVMe drive so I cannot say for sure whether it runs any checks or not.

I booted from LiveCD and performed fsck checks of all my partitions:
fsck.vfat /dev/nvme0n1p1 (EFI partition)
fsck.vfat /dev/nvme0n1p2 (Dell service partition, not mounted)
e2fsck -f /dev/nvme0n1p3 (Root partition)
e2fsck -f /dev/nvme0n1p5 (Home partition)
These checks showed no problems.

I changed mount counter to set periodic checks:
sudo tune2fs -c 29 /dev/nvme0n1p3
sudo tune2fs -c 30 /dev/nvme0n1p5
But despite these settings this message still appears on every boot.

Operating System: Kubuntu 20.04.3
Kernel Version: 5.4.0-88-generic
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-8850H CPU @ 2.60GHz
Memory: 15,4 GiB of RAM

---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CurrentDesktop: KDE
DefaultPlymouth: /usr/share/plymouth/themes/kubuntu-logo/kubuntu-logo.plymouth
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-08-09 (57 days ago)
InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:568c Realtek Semiconductor Corp. Integrated_Webcam_HD
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude 5591
Package: plymouth 0.9.4git20200323-0ubuntu6.2
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-88-generic root=UUID=fc777e68-1731-4eeb-8a59-9bc45137ad80 ro video=efifb:nobgrt quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-88.99-generic 5.4.140
Tags: focal
TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth
Uname: Linux 5.4.0-88-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 06/10/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0DVVG1
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd06/10/2021:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5591
dmi.product.sku: 0819
dmi.sys.vendor: Dell Inc.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1946192/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → plymouth (Ubuntu)
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1946192

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

(It's not clear if you're talking about an installed system, or just live (with/without persistence; thus casper) where the checks would be expected.)

Revision history for this message
Oleg Moiseichuk (berroll) wrote : CurrentDmesg.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
Oleg Moiseichuk (berroll) wrote : Dependencies.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : EtcDefaultGrub.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : Lspci.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : Lspci-vt.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : Lsusb-t.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : Lsusb-v.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : ProcEnviron.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : ProcModules.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : UdevDb.txt

apport information

Revision history for this message
Oleg Moiseichuk (berroll) wrote : acpidump.txt

apport information

description: updated
Revision history for this message
Oleg Moiseichuk (berroll) wrote :

I'm talking about already installed system, not LiveCD session.

It looks like check of root partition IS run indeed as I can guess from boot.log.
I'll add it to other reports because apport collector missed it.

Revision history for this message
Oleg Moiseichuk (berroll) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I get this on my focal desktop too (Ubuntu not Kubuntu).

It's probably not a Plymouth bug though -- Plymouth needs some other process to tell it what message to display. So we need to find what that other process is after installation.

Revision history for this message
Steve Langasek (vorlon) wrote :

The message comes from systemd-fsckd. Though I'm not sure why it would be considered a bug that the message shows up briefly on the screen; we always call systemd-fsckd, even if it quickly determines there's no work to do and exits.

affects: plymouth (Ubuntu) → systemd (Ubuntu)
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The brevity of the message looks like a one-frame flicker, so it looks like a bug.

Revision history for this message
Oleg Moiseichuk (berroll) wrote :

One more reasoning: fsck is called DESPITE the settings of tune2fs. By default "Maximum mount counts" equals -1 which means that fsck shouldn't run at all. If this parameter is set to some positive value fcsk should run periodically but not on every start.
Less experienced users may think that they've got real problems with their disk because of these checks on every boot.

Revision history for this message
miguelquiros (mquiros) wrote :

I have this bug after updrading from focal to jammy. Now in every boot I can see for several seconds the message "Press Ctrl+C to cancel all filesystem checks in process".

With "journalctl -b", I follow all the booting procedure and I can see several

Starting File System Check on /dev/disk/by-uuid/...

messages (one for each partition used by my system) and several lines below the corresponding

Finished File System Check on /dev/disk/by-uuid/...

No error in the checks are reported.

If I boot with a live USB and perform e2fsck (or even e2fsck -f) in every partition, no error is reported whatsoever.

I have seen this kind of behaviour for other people in some forum (easy to find googling "checking filesystems on every boot" or something of the kind). Not sure, but it looks like it appears in people upgrading from a previous Ubuntu version.

It is not a serious bug but it is quite annoying delaying the boot process. Supposedly, filesystems should only be checked regularly from time to time.

Revision history for this message
miguelquiros (mquiros) wrote :

Addition:

This check is not made in the partition mounted as root. I can see the following in journalctl -b:

Condition check resulted in File System Check on Root Device being skipped

It is made in all other mounted partitions.

Revision history for this message
miguelquiros (mquiros) wrote :

More information:

Changing the parameter max-mount-counts (tune2fs -c) in these filesystems does not affect this behaviour, it can be set to "-1" or to a positive value, no difference.

The only way I have found to avoid this check is adding the fsck.mode=skip boot parameter at grub stage (it could be made permanent editing /etc/default/grub) but I do not think this is a wise thing to do.

Benjamin Drung (bdrung)
Changed in systemd (Ubuntu):
importance: Undecided → Low
Revision history for this message
Benjamin Drung (bdrung) wrote :

Since most reporters say that the message "Press Ctrl+C to cancel all filesystem checks in process" appears only for a short period of time, the question is: Are there filesystem checks on every boot or is this message shown despite no check were running?

Revision history for this message
Oleg Moiseichuk (berroll) wrote :

It seems that it runs after all at every boot. For example, I started my system and checked afterwards:

> journalctl | grep fsck | grep 'sep 26'
sep 26 19:20:41 L-5591 systemd[1]: Created slice system-systemd\x2dfsck.slice.
sep 26 19:20:41 L-5591 systemd[1]: Listening on fsck to fsckd communication Socket.
sep 26 19:20:42 L-5591 systemd-fsck[637]: /dev/nvme0n1p5: clean, 59131/48832512 files, 22974937/195312640 blocks
sep 26 19:20:42 L-5591 systemd-fsck[664]: fsck.fat 4.1 (2017-01-24)
sep 26 19:20:42 L-5591 systemd-fsck[664]: /dev/nvme0n1p1: 42 files, 10823/190976 clusters
sep 26 19:21:11 L-5591 systemd[1]: systemd-fsckd.service: Succeeded.

Similar entries can be found in previous days' journal.

Revision history for this message
miguelquiros (mquiros) wrote :

In my case, if I introduce the boot parameter fsck.mode=skip, then the message "Press Ctrl+C to cancel all filesystem checks in process" does not appear and the boot is faster, hence I deduce that the checks are indeed performed when the boot parameter is not present.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.