11

I have upgraded the system from 19.10 to 20.04. The installation is dual boot. When I turn on the system every time it checks the filesystem using 80/90 seconds since it starts running Ubuntu from the Grub. Also compare the writing "press Ctrl-c to cancel the checks in progress on the filesystem" which lasts 45/50 seconds (of the 80/90 mentioned above). The Ctrl-c command has no effect, during the update there is no progress information and in the end no results. Tune2fs tells me that Ubuntu's 2 filesystems (/ and / home on two different partitions) are "clean". With 19.10 and even earlier with 18.04 this did not happen, there is no success with the other PCs to which I have yet to make progress. Anyone have any ideas? thank you all

mario_user28404
  • 485

8 Answers8

10

Removing Disk Check From 20.04 Boot

The command line option fsck.mode=skip can be used to skip the disk check when booting Ubuntu 20.04.

The line Checking disks: 0% complete may still come up but fsck will not be run, nor will boot time be increased.

Add fsck.mode=skip to the linux line in grub.cfg just before quiet splash

It is recommended that we add the command to grub.cfg by editing /etc/default/grub thus: GRUB_CMDLINE_LINUX_DEFAULT="fsck.mode=skip quiet splash" and then run sudo update-grub.

I have had this problem with a Live USB but not with an installed system.

C.S.Cameron
  • 20,530
  • 12
  • 78
  • 125
4

Checking /etc/fstab worked for me in 22.04.2 LTS. Turns out there was a swap listed there that was no longer connected or needed. Commented it out and the boot-up filesystem check went away.

Mike S
  • 41
3

It's fscking for a reason. Your / or /home may have problems. Perform a manual fsck on both.

  • boot to a Ubuntu Live DVD/USB in “Try Ubuntu” mode
  • open a terminal window by pressing Ctrl+Alt+T
  • type sudo fdisk -l
  • identify the /dev/sdXX device name for your "Linux Filesystem"(s)
  • type sudo fsck -f /dev/sdXX, replacing sdXX with the number(s) you found earlier
  • repeat the fsck command if there were errors
  • type reboot
heynnema
  • 73,649
3

For any poor souls that ran into this issue and none of the above worked - make sure that no old hard drives are listed in your /etc/fstab.

Run the tune2fs -l /dev/sdX command to check if the UID of the sdX matches the one in your /etc/fstab

If it does not, the long filesystem check will be triggered.

Stan Smulders
  • 131
  • 2
2

I've been having this same problem in the last releases of Ubuntu. Right now, I have Ubuntu 21.10 installed and it still has it. But I managed to find some sort of solution. I have dual boot with Windows 10, and apparently Ubuntu does not like that. The partition it is always checking at boot is the ESP one. To fix that, I changed its 'pass' argument in fstab from 1 to 0. I would recommend keeping the other partitions with their original pass values, as it will make it possible for errors to be detected. I would also not recommend adding fsck.mode=skip in the command line for the same reason. Hope this helps.

Natan Junges
  • 36
0

It should say which filesystem it's waiting for, listing its UUID. Make sure that your swap partition wasn't reformatted or changed as part of the upgrade, because this changes its UUID. If it was, update /etc/fstab and change the UUID to match the new one, or use mkswap -U {uuid} to update the UUID on the swap partition to match /etc/fstab.

Shawn Mulligan
  • 1
0

Also make sure that the GRUB_CMDLINE_LINUX_DEFAULT settings in /etc/default/grub does not force fsck on every boot. Remove that and run update-grub in that case.

Lars Berntzon
  • 101
0

On my Ubuntu 22.04.5, in /etc/fstab there were two swap entries bound by UUID. One of them was invalid just like Mike S pointed out.

You may use the following command to get all valid UUIDs (if any) of available swap partitions:

sudo lsblk -o FSTYPE,UUID | grep swap

Then feel free to replace (or just remove/comment out) entries in /etc/fstab.

Віталій Крутько
  • 1