Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[SOLVED] Debian 11: fsckd-cancel-msg Freeze

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
Ged296123
Posts: 6
Joined: 2021-08-11 17:52
Has thanked: 1 time

[SOLVED] Debian 11: fsckd-cancel-msg Freeze

#1 Post by Ged296123 »

New to GNU/Linux and Debian, so apologies beforehand if I haven't provided enough information in regard to my problem.
If you can direct me to obtaining more details, will gladly do so.

I have installed Debian 11 from the free Debian Live image. I have obtained my network and graphics drivers from the non-free repos.
I have a root, swap and home partition. My /etc/fstab is as follow:

Code: Select all

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=22D9-CF83                            /boot/efi      vfat    defaults,noatime 0 2
UUID=a7281653-a4af-458b-b4b4-90334c4be7cc /              ext4    defaults,noatime,discard 0 1
UUID=31e10b17-fce8-4338-943c-6c9e3d2539ad swap           swap    defaults,noatime,discard 0 0
UUID=82b6a41f-b2e2-4cff-baf4-0457200c3221 /home          ext4    defaults,noatime,discard 0 2
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
My laptop is a Lenovo T460p. Inxi -Fxz output as follows:

Code: Select all

System:
  Kernel: 5.10.0-9-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1 
  Desktop: GNOME 3.38.6 Distro: Debian GNU/Linux 11 (bullseye) 
Machine:
  Type: Laptop System: LENOVO product: 20FXS14S00 v: ThinkPad T460p 
  serial: <filter> 
  Mobo: LENOVO model: 20FXS14S00 v: SDK0J40697 WIN serial: <filter> 
  UEFI: LENOVO v: R07ET92W (2.32 ) date: 07/28/2019 
Battery:
  Device-1: hidpp_battery_0 model: Logitech Wireless Keyboard K360 
  charge: 100% (should be ignored) status: Discharging 
CPU:
  Info: Quad Core model: Intel Core i7-6820HQ bits: 64 type: MT MCP 
  arch: Skylake-S rev: 3 L2 cache: 8 MiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 43198 
  Speed: 3268 MHz min/max: 800/3600 MHz Core speeds (MHz): 1: 3268 2: 3318 
  3: 3294 4: 3201 5: 3299 6: 3303 7: 3322 8: 3201 
Graphics:
  Device-1: Intel HD Graphics 530 vendor: Lenovo driver: i915 v: kernel 
  bus ID: 00:02.0 
  Device-2: NVIDIA GM108M [GeForce 940MX] vendor: Lenovo driver: nvidia 
  v: 460.91.03 bus ID: 02:00.0 
  Device-3: Chicony Integrated Camera type: USB driver: uvcvideo 
  bus ID: 1-8:7 
  Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting,nvidia 
  unloaded: fbdev,nouveau,vesa resolution: 1: 1920x1080 2: 1920x1080~60Hz 
  OpenGL: renderer: Mesa Intel HD Graphics 530 (SKL GT2) v: 4.6 Mesa 20.3.5 
  direct render: Yes 
Audio:
  Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Lenovo 
  driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
  Device-2: Kingston HyperX SoloCast type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-3.3:6 
  Sound Server: ALSA v: k5.10.0-9-amd64 
Network:
  Device-1: Intel Ethernet I219-LM vendor: Lenovo driver: e1000e v: kernel 
  port: efa0 bus ID: 00:1f.6 
  IF: enp0s31f6 state: down mac: <filter> 
  Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel port: d000 
  bus ID: 03:00.0 
  IF: wlp3s0 state: up mac: <filter> 
  IF-ID-1: tun0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
  IF-ID-2: virbr0 state: down mac: <filter> 
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb 
  v: 0.8 bus ID: 1-7:5 
  Report: ID: hci0 state: up running pscan bt-v: 2.1 lmp-v: 4.2 
  address: <filter> 
Drives:
  Local Storage: total: 1.38 TiB used: -500767328 
  ID-1: /dev/sda vendor: Samsung model: MZ7LN512HMJP-000L7 size: 476.94 GiB 
  temp: 45 C 
  ID-2: /dev/sdb type: USB vendor: Western Digital model: WD10EADS-00M2B0 
  size: 931.51 GiB 
Partition:
  ID-1: / size: 100.37 GiB used: 21.39 GiB (21.3%) fs: ext4 dev: /dev/sda2 
  ID-2: /boot/efi size: 300.4 MiB used: 3.4 MiB (1.1%) fs: vfat 
  dev: /dev/sda1 
  ID-3: /home size: 350.83 GiB used: 75.04 GiB (21.4%) fs: ext4 
  dev: /dev/sda4 
Swap:
  ID-1: swap-1 type: partition size: 16.6 GiB used: 1.8 MiB (0.0%) 
  dev: /dev/sda3 
Sensors:
  System Temperatures: cpu: 65.0 C mobo: 56.0 C 
  Fan Speeds (RPM): cpu: 2529 
Info:
  Processes: 304 Uptime: 1h 54m Memory: 15.37 GiB used: 2.84 GiB (18.5%) 
  Init: systemd runlevel: 5 Compilers: gcc: 10.2.1 Packages: 2450 
  Shell: Bash v: 5.1.4 inxi: 3.3.01 
My system operates with no problems except once in a while the boot process freezes with a fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress message.

After waiting for an hour or so, (Ctrl+C does not work), I have to force shutdown my laptop.
On the next boot, everything works perfectly (and does so until I face the same problem a couple of boots later).

I have tried booting with my live image to do a fsck and e2fsck -cfy on my root and home partitions and seem to have no errors on my disk.
For root and home partitions, e2fsck output are respectively:

Code: Select all

user@debian:~$ sudo e2fsck -fcy /dev/sda2
e2fsck 1.46.2 (28-Feb-2021)
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 errdone                                                 
/dev/sda2: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda2: 461099/6725632 files (0.3% non-contiguous), 6088739/26880000 blocks
user@debian:~$ sudo e2fsck -fcy /dev/sda4
e2fsck 1.46.2 (28-Feb-2021)
Checking for bad blocks (read-only test):   0.00% done, 0:00 elapsed. (0/0/0 errdone                                                 
/dev/sda4: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/sda4: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda4: 64231/23437312 files (1.6% non-contiguous), 21413801/93717841 blocks
systemd-analyze blame output is as follows:

Code: Select all

6.627s NetworkManager-wait-online.service
4.370s plymouth-quit-wait.service
2.920s fwupd.service
1.085s ufw.service
 621ms systemd-modules-load.service
 390ms nvidia-persistenced.service
 367ms exim4.service
 363ms upower.service
 355ms dev-sda2.device
 186ms systemd-fsck@dev-disk-by\x2duuid-82b6a41f\x2db2e2\x2d4cff\x2dbaf4\x2d0457200c3221.service
 175ms boot-efi.mount
 159ms systemd-udevd.service
 152ms apparmor.service
 135ms dev-disk-by\x2duuid-31e10b17\x2dfce8\x2d4338\x2d943c\x2d6c9e3d2539ad.swap
 113ms user@1000.service
 113ms systemd-fsck@dev-disk-by\x2duuid-22D9\x2dCF83.service
 112ms udisks2.service
 106ms systemd-journald.service
  97ms systemd-journal-flush.service
  95ms systemd-timesyncd.service
  95ms libvirtd.service
  90ms systemd-udev-trigger.service
  89ms lvm2-monitor.service
  88ms accounts-daemon.service
  70ms NetworkManager.service
  65ms polkit.service
  65ms avahi-daemon.service
  59ms ssh.service
  59ms ModemManager.service
  56ms switcheroo-control.service
  55ms networking.service
  52ms gdm.service
  51ms systemd-logind.service
  49ms wpa_supplicant.service
  49ms systemd-machined.service
  44ms cups.service
  41ms plymouth-start.service
  39ms packagekit.service
  36ms libvirt-guests.service
  36ms systemd-backlight@leds:tpacpi::kbd_backlight.service
  30ms tmp.mount
  28ms console-setup.service
  28ms systemd-tmpfiles-setup.service
  27ms systemd-rfkill.service
  27ms plymouth-read-write.service
  26ms colord.service
  25ms e2scrub_reap.service
  21ms systemd-sysusers.service
  21ms systemd-random-seed.service
  21ms ifupdown-pre.service
  20ms systemd-update-utmp-runlevel.service
  19ms systemd-tmpfiles-clean.service
  19ms rsyslog.service
  17ms lm-sensors.service
  15ms rtkit-daemon.service
  14ms bluetooth.service
  14ms dev-hugepages.mount
  13ms modprobe@fuse.service
  13ms dev-mqueue.mount
  13ms sys-kernel-debug.mount
  12ms systemd-remount-fs.service
  12ms sys-kernel-tracing.mount
  12ms systemd-sysctl.service
  11ms keyboard-setup.service
  11ms kmod-static-nodes.service
  11ms systemd-tmpfiles-setup-dev.service
  11ms user-runtime-dir@1000.service
  10ms home.mount
  10ms modprobe@configfs.service
  10ms systemd-backlight@backlight:intel_backlight.service
  10ms modprobe@drm.service
   9ms alsa-restore.service
   6ms systemd-update-utmp.service
   5ms openvpn.service
   5ms systemd-user-sessions.service
   3ms sys-kernel-config.mount
   2ms sys-fs-fuse-connections.mount
  33us blk-availability.service
Any help to get me out of this boot problem will be greatly appreciated.

Thanks in advance.
Last edited by Ged296123 on 2021-10-26 13:48, edited 1 time in total.

arzgi
Posts: 1185
Joined: 2008-02-21 17:03
Location: Finland
Been thanked: 31 times

Re: Debian 11: fsckd-cancel-msg Freeze

#2 Post by arzgi »

Those numbers in the line ends of /etc/fstab dictate how often file system check is run.

From man fstab:

Code: Select all

The sixth field (fs_passno).
              This  field  is  used by fsck(8) to determine the order in which
              filesystem checks are done at boot time.   The  root  filesystem
              should  be  specified  with a fs_passno of 1.  Other filesystems
              should have a fs_passno of 2.  Filesystems within a  drive  will
              be  checked  sequentially,  but  filesystems on different drives
              will be checked at the same time to utilize  parallelism  avail‐
              able  in  the  hardware.   Defaults  to zero (don't fsck) if not
              present.
I think it is good to check the file system once in a while, but it can be disabled.

Ged296123
Posts: 6
Joined: 2021-08-11 17:52
Has thanked: 1 time

Re: Debian 11: fsckd-cancel-msg Freeze

#3 Post by Ged296123 »

@arzgi
Thank you.
I did find some resources on completely cancelling fsck through /etc/fstab and/or tune2fs but wasn't sure if it was a good idea.
If possible, would you have any idea why this problem is occurring in the first place? Would there maybe be a root cause?
If I can't find the root cause, I think I will go with your recommendation.

Again, thank you kindly for taking the time to respond.

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Debian 11: fsckd-cancel-msg Freeze

#4 Post by p.H »

Ged296123 wrote: 2021-10-21 12:23 My system operates with no problems except once in a while the boot process freezes with a fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress message.
This message is (usually briefly) displayed at every boot and has nothing to do with the freeze.
Ged296123 wrote: 2021-10-21 12:23 After waiting for an hour or so, (Ctrl+C does not work)
Of course it does not work. The filesystem check is already done and the freeze is caused by another step.
You can remove the "quiet" (and "splash" if present) parameter from the kernel command line in GRUB menu to display more messages at boot time, it may give a hint about the operation which freezes.

Ged296123
Posts: 6
Joined: 2021-08-11 17:52
Has thanked: 1 time

Re: Debian 11: fsckd-cancel-msg Freeze

#5 Post by Ged296123 »

Hi @p.H
Thanks for your response.
I removed the "quite" and "splash" from the kernel command and interestingly the problem disappeared (tested re-booting ~10 times)
I can't understand how this is associated, so I will continue using the system for a couple of more days.
If the problem doesn't re-appear, or if you and anyone else won't have anything to add, I'll be closing this post as solved.

User avatar
sunrat
Administrator
Administrator
Posts: 6412
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 116 times
Been thanked: 462 times

Re: Debian 11: fsckd-cancel-msg Freeze

#6 Post by sunrat »

Ged296123 wrote: 2021-10-21 20:56I removed the "quite" and "splash" from the kernel command and interestingly the problem disappeared (tested re-booting ~10 times)
Did you have both parameters active? It would be interesting if you could put them back one at a time to see which one is the culprit. I would suspect "splash" as I never have had an issue with just "quiet".
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

p.H
Global Moderator
Global Moderator
Posts: 3049
Joined: 2017-09-17 07:12
Has thanked: 5 times
Been thanked: 132 times

Re: Debian 11: fsckd-cancel-msg Freeze

#7 Post by p.H »

AFAICS,
"splash" enables the graphical splash screen.
"nosplash" disables the splash screen.
The default (neither splash nor nosplash) enables the splash screen in text mode.

Ged296123
Posts: 6
Joined: 2021-08-11 17:52
Has thanked: 1 time

Re: Debian 11: fsckd-cancel-msg Freeze

#8 Post by Ged296123 »

With both "quiet" and/or "splash," boot eventually hangs.
Right now, I'm going with removing both of them from the kernel command.
At least I can boot into the system without having to da a force shutdown.

Nevertheless, there is something else going on and the root problem doesn't seem grub.
When I was trying to experiment booting with splash and quite on and off, I once came across the below:

Code: Select all

(1 of 2) A start job is running for Hostname service (xxs/ amins bbs)
I can't seem to find anything related in the journal (or I don't properly know where to look), but I believe there is some problem with the network services (i.e. NetworkManager-wait-online.service) properly starting (as you will notice below, the service isn't there).

Code: Select all

3.609s plymouth-quit-wait.service
2.740s fwupd.service
2.504s apt-daily.service
 683ms ufw.service
 423ms systemd-rfkill.service
 379ms dev-sda2.device
 356ms upower.service
 266ms libvirtd.service
 188ms rtkit-daemon.service
 164ms systemd-udev-trigger.service
 164ms sys-kernel-tracing.mount
 161ms dev-hugepages.mount
 158ms dev-mqueue.mount
 158ms sys-kernel-debug.mount
 151ms systemd-fsck@dev-disk-by\x2duuid-22D9\x2dCF83.service
 149ms keyboard-setup.service
 146ms systemd-fsck@dev-disk-by\x2duuid-82b6a41f\x2db2e2\x2d4cff\x2dbaf4\x2d0457200c3221.service
 145ms kmod-static-nodes.service
 141ms lvm2-monitor.service
 140ms boot-efi.mount
 137ms modprobe@configfs.service
 135ms systemd-timesyncd.service
 132ms modprobe@drm.service
 131ms apparmor.service
 128ms modprobe@fuse.service
 118ms accounts-daemon.service
 117ms systemd-logind.service
 115ms dev-disk-by\x2duuid-31e10b17\x2dfce8\x2d4338\x2d943c\x2d6c9e3d2539ad.swap
 114ms systemd-remount-fs.service
 113ms user@1000.service
 111ms udisks2.service
 105ms systemd-modules-load.service
  94ms systemd-journal-flush.service
  92ms systemd-journald.service
  89ms polkit.service
  87ms ModemManager.service
  79ms NetworkManager.service
  70ms avahi-daemon.service
  60ms systemd-udevd.service
  56ms switcheroo-control.service
  54ms smartmontools.service
  50ms ssh.service
  49ms systemd-machined.service
  43ms cups.service
  40ms lm-sensors.service
  40ms wpa_supplicant.service
  38ms gdm.service
  35ms packagekit.service
  33ms networking.service
  30ms e2scrub_reap.service
  27ms sys-kernel-config.mount
  27ms sys-fs-fuse-connections.mount
  21ms systemd-random-seed.service
  20ms bluetooth.service
  20ms libvirt-guests.service
  19ms plymouth-start.service
  19ms systemd-tmpfiles-setup-dev.service
  18ms systemd-tmpfiles-setup.service
  17ms systemd-sysusers.service
  17ms systemd-sysctl.service
  17ms rsyslog.service
  17ms alsa-restore.service
  16ms plymouth-read-write.service
  16ms home.mount
  16ms colord.service
  15ms systemd-tmpfiles-clean.service
  13ms console-setup.service
  12ms systemd-backlight@leds:tpacpi::kbd_backlight.service
  11ms openvpn.service
  11ms user-runtime-dir@1000.service
   9ms systemd-user-sessions.service
   9ms systemd-update-utmp.service
   7ms systemd-update-utmp-runlevel.service
   6ms systemd-backlight@backlight:intel_backlight.service
   6ms ifupdown-pre.service
   3ms tmp.mount
  21us blk-availability.service
Although I'm practically free of my initial problem, I'm open to any help to further identify what's going on.

Ged296123
Posts: 6
Joined: 2021-08-11 17:52
Has thanked: 1 time

Re: Debian 11: fsckd-cancel-msg Freeze

#9 Post by Ged296123 »

I believe the issued has been cleared on my part.
Just to share my experience with anyone else who may encounter the same problem:

- The issue rises with boot freezing with a "fsckd-cancel-msg"
- Should you wait long enough, you'll be seeing a scrolling

Code: Select all

(1 of 2) A start job is running for Hostname service (xxs/ amins bbs)
(2 of 2) A start job is running for Uncomplicated firewall (xxs / no limit) 
I initially thought the problem rose from the Hostname service and masked it with

Code: Select all

sudo systemctl mask systemd-hostnamed
I learnt that I could easily configure my hostname from /etc/hosts and /etc/hostname
However, the problem didn't stop and after some boots, freezing re-occured with

Code: Select all

(1 of 1) A start job is running for Uncomplicated firewall (xxs / no limit)
After some "googleing", I noticed there may be some bugs related to ufw (uncomplicated firewall)
https://unix.stackexchange.com/question ... -debian-11

So, deciding to replace ufw with firewalld, I went back and unmasked Hostname services with

Code: Select all

sudo systemctl unmask systemd-hostnamed
My quiet and splash in the kernel command work just fine, so far I have had no freezes and things seem to run pretty much OK.

User avatar
Francewhoa
Posts: 32
Joined: 2013-04-12 17:59
Location: Sept-Iles, Quebec, Canada
Has thanked: 6 times

Re: [SOLVED] Debian 11: fsckd-cancel-msg Freeze

#10 Post by Francewhoa »

Hello @Ged296123 :)

I suggest checking that the volume hosting Debian has enough available space. If it is somehow full or almost full, you need to increase its available space then restart. Debian will boot. Voilà.

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---


Below is the same suggestion as above. But with details for those not familiar with how to check available space and increase it.

We are facing the same challenge with one of our devices. Removing both quiet" and "splash" sometime solve this challenge. But sometimes it does. Weird. In our case, the cause of this challenge was that somehow, the device volume which stores Debian was full. Zero available space. In turn, during boot, fsck was automatically started. fsck needs a small amount of space to be able to complete its automation. In turn, fsck was stuck. As it was not able to complete its automation. Unfortunately, fsck does not check the available space before starting its automation. This would be a nice new feature.

We were able to reproduce this challenge on 3 other devices. Simply by filling their storage.

Steps to resolve this challenge:

1. Using Terminal, execute this command to find if the volume(s) are full

Code: Select all

sudo df -h
2. Alternatively, if you have access to GNOME, using Terminal, execute this command to open Baobab

Code: Select all

sudo baobab
Wait a few seconds or minutes for Baobab to analyze the volume. It will show which folder(s) use the most space. The interface is self explained.

4. If needed, increase the available storage. To do so, for example, if appropriate, run those commands to clear temporary cached installation packages:

Code: Select all

sudo apt-get clean

Code: Select all

sudo aptitude clean
5. Reboot

6. fsck will automatically complete its automation. Sometime this is very fast. It won't even display. This is normal.

7. Debian will boot. Voilà.
- - -
Loving back your Debian community result in multiple benefits for you. https://www.debian.org/intro/help

Post Reply