Checking file system at startup

PRSoftware · 2023-08-11 14:59

Hello

Every time I start my computer with the new version 5.2 Aquarius, I can see just after the message "Loading initial ramdisk" a full check of the file system on /dev/sda1.

This operation takes a long time on my computer.

Is it really necessary to do such check on every startup ?

Is it a way to disable it ?

Rademes · 2023-08-11 21:39

Can you please post here the contents of your /etc/fstab file? You can do this by typing in terminal command
cat /etc/fstab, and post here the output.

Last edited by Rademes (2023-08-11 21:39)

PRSoftware · 2023-08-13 08:48

Here is the content of /etc/fstab (I replaced the IP address of the SSHFS mount)

# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=020c5311-7007-47b4-817e-1071d19e54fe / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=a3461572-5e9c-4c89-b6f0-07a1c8fa468b none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
# Mount SSHFS Public
public@AAA.BBB.CCC.DDD:/home/Public/ /home/Public fuse.sshfs _netdev,x-systemd.automount,allow_other,uid=1000,gid=1000,noatime,port=22 0 0

Rademes · 2023-08-13 17:47

In the string UUID=020c5311-7007-47b4-817e-1071d19e54fe / ext4 errors=remount-ro 0 1, try to replace the digit 1 to 0 at the end of that string. It should disable filesystem check on boot.
You can read about it here: https://linuxconfig.org/how-fstab-works … e-on-linux
Do not change another values, because this can make your PC unbootable.

Strange, I also have Q4OS Aquarius 5.2 installed, but I have completely different /etc/fstab:

valentina@latitudee5450:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=68bead01-846f-44d3-a1be-3217886fb3e7 swap           swap    defaults 0 0
UUID=2c6e1994-5b32-43a5-93a6-603d5740769d /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,mode=1777 0 0
valentina@latitudee5450:~$

Last edited by Rademes (2023-08-13 17:50)

PRSoftware · 2023-08-13 18:04

Unfortunately, the modification of the last field in the fstab for the main disk has no effect on the check at startup.

bin · 2023-08-14 06:50

You might just have a look at /etc/default/grub and see if it contains

GRUB_CMDLINE_LINUX_DEFAULT="quiet fsck.mode=force"

or any other line contains the fsck.mode=force argument.

Alternatively consider that you have a bad disk and/or a problem on shutdown which means the system is self checking as it is supposed to do.

Install and run gsmartcontrol and that will help determine if the disk is bad.

PRSoftware · 2023-08-14 09:45

There is not any line containing "fsck" in /etc/default/grub.

Here is the export of the gsmartcontrol command :

smartctl 8.3 2022-02-28 r5338 [i686-linux-6.1.0-10-686-pae] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     SH00M256GB
Serial Number:    YMA2106300148
Firmware Version: V1103A4P
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      mSATA
TRIM Command:     Available
Device is:        Not in smartctl database 7.3/5319
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 3.0 Gb/s
Local Time is:    Mon Aug 14 10:34:14 2023 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM level is:     254 (maximum performance)
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(  120) seconds.
Offline data collection
capabilities: 			 (0x11) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					No Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
					entering power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  10) minutes.
SCT capabilities: 	       (0x0001)	SCT Status supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  1 Raw_Read_Error_Rate     -O--CK   100   100   050    -    0
  5 Reallocated_Sector_Ct   -O--CK   100   100   050    -    0
  9 Power_On_Hours          -O--CK   100   100   050    -    1
 12 Power_Cycle_Count       -O--CK   100   100   050    -    16
160 Unknown_Attribute       -O--CK   100   100   050    -    0
161 Unknown_Attribute       PO--CK   100   100   050    -    100
163 Unknown_Attribute       -O--CK   100   100   050    -    6
164 Unknown_Attribute       -O--CK   100   100   050    -    0
165 Unknown_Attribute       -O--CK   100   100   050    -    0
166 Unknown_Attribute       -O--CK   100   100   050    -    0
167 Unknown_Attribute       -O--CK   100   100   050    -    0
168 Unknown_Attribute       -O--CK   100   100   050    -    5050
169 Unknown_Attribute       -O--CK   100   100   050    -    100
175 Program_Fail_Count_Chip -O--CK   100   100   050    -    0
176 Erase_Fail_Count_Chip   -O--CK   100   100   050    -    0
177 Wear_Leveling_Count     -O--CK   100   100   050    -    0
178 Used_Rsvd_Blk_Cnt_Chip  -O--CK   100   100   050    -    0
181 Program_Fail_Cnt_Total  -O--CK   100   100   050    -    0
182 Erase_Fail_Count_Total  -O--CK   100   100   050    -    0
192 Power-Off_Retract_Count -O--CK   100   100   050    -    15
194 Temperature_Celsius     -O---K   100   100   050    -    40
195 Hardware_ECC_Recovered  -O--CK   100   100   050    -    0
196 Reallocated_Event_Count -O--CK   100   100   050    -    0
197 Current_Pending_Sector  -O--CK   100   100   050    -    0
198 Offline_Uncorrectable   -O--CK   100   100   050    -    0
199 UDMA_CRC_Error_Count    -O--CK   100   100   050    -    0
232 Available_Reservd_Space -O--CK   100   100   050    -    100
241 Total_LBAs_Written      ----CK   100   100   050    -    784
242 Total_LBAs_Read         ----CK   100   100   050    -    913
245 Unknown_Attribute       -O--CK   100   100   050    -    0
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      1  Comprehensive SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      8  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x24       GPL     R/O     88  Current Device Internal Status Data log
0x25       GPL     R/O     32  Saved Device Internal Status Data log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

Selective Self-tests/Logging not supported

SCT Status Version:                  3
SCT Version (vendor specific):       0 (0x0000)
Device State:                        Active (0)
Current Temperature:                    40 Celsius
Power Cycle Min/Max Temperature:     40/40 Celsius
Lifetime    Min/Max Temperature:     26/40 Celsius
Specified Max Operating Temperature:   100 Celsius
Under/Over Temperature Limit Count:   0/0

SCT Data Table command not supported

SCT Error Recovery Control command not supported

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4              16  ---  Lifetime Power-On Resets
0x01  0x010  4               1  ---  Power-on Hours
0x01  0x018  6        51422808  ---  Logical Sectors Written
0x01  0x020  6          130601  ---  Number of Write Commands
0x01  0x028  6        59857707  ---  Logical Sectors Read
0x01  0x030  6          270643  ---  Number of Read Commands
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1               0  ---  Percentage Used Endurance Indicator
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description
0x0001  4            1  Command failed due to ICRC error
0x0002  4            0  R_ERR response for data FIS
0x0005  4            1  R_ERR response for non-data FIS
0x000a  4            1  Device-to-host register FISes sent due to a COMRESET

For information, it is a new SSD disk I installed recently because of the failure of the previous HDD after 18 years of work.

Do you see something wrong for this disk ?

Rademes · 2023-08-14 10:08

If the SSD disk is new, than it should be OK. You have not purchased a cheap noname SSD, right? They can be faulty from factory.
Not sure, will it help, but please run cat /proc/mounts and post the content here.

Last edited by Rademes (2023-08-14 10:09)

PRSoftware · 2023-08-14 11:06

Here is the content of /proc/mounts :

sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=1004056k,nr_inodes=205114,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,noexec,relatime,size=205148k,mode=755 0 0
/dev/sda1 / ext4 rw,noatime,errors=remount-ro 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
cgroup2 /sys/fs/cgroup cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
bpf /sys/fs/bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 0 0
systemd-1 /proc/sys/fs/binfmt_misc autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=14470 0 0
hugetlbfs /dev/hugepages hugetlbfs rw,relatime,pagesize=2M 0 0
mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,nosuid,nodev,noexec,relatime 0 0
tracefs /sys/kernel/tracing tracefs rw,nosuid,nodev,noexec,relatime 0 0
fusectl /sys/fs/fuse/connections fusectl rw,nosuid,nodev,noexec,relatime 0 0
configfs /sys/kernel/config configfs rw,nosuid,nodev,noexec,relatime 0 0
ramfs /run/credentials/systemd-sysusers.service ramfs ro,nosuid,nodev,noexec,relatime,mode=700 0 0
ramfs /run/credentials/systemd-sysctl.service ramfs ro,nosuid,nodev,noexec,relatime,mode=700 0 0
ramfs /run/credentials/systemd-tmpfiles-setup-dev.service ramfs ro,nosuid,nodev,noexec,relatime,mode=700 0 0
systemd-1 /home/Public autofs rw,relatime,fd=54,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15156 0 0
systemd-1 /home/patrick/Maison autofs rw,relatime,fd=55,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15161 0 0
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime 0 0
ramfs /run/credentials/systemd-tmpfiles-setup.service ramfs ro,nosuid,nodev,noexec,relatime,mode=700 0 0
sunrpc /run/rpc_pipefs rpc_pipefs rw,relatime 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=205148k,nr_inodes=51287,mode=700,uid=1000,gid=1000 0 0

Rademes · 2023-08-16 15:36

Everything looks good there. Sorry, I have no more ideas how to disable this system check...

PRSoftware · 2023-08-16 16:30

Ok, thank you for the time you spent on my problem.

Senas Komunistas · 2023-08-16 16:47

Hello.

The command line option

fsck.mode=skip

can be used to skip the disk check when booting. 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 to 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

PRSoftware · 2023-08-16 17:23

Well done, guy: the "fsck.mode=skip" disables totally the file system checking at startup.

Q4OS Forum

#1 2023-08-11 14:59

Checking file system at startup

#2 2023-08-11 21:39

Re: Checking file system at startup

#3 2023-08-13 08:48

Re: Checking file system at startup

#4 2023-08-13 17:47

Re: Checking file system at startup

#5 2023-08-13 18:04

Re: Checking file system at startup

#6 2023-08-14 06:50

Re: Checking file system at startup

#7 2023-08-14 09:45

Re: Checking file system at startup

#8 2023-08-14 10:08

Re: Checking file system at startup

#9 2023-08-14 11:06

Re: Checking file system at startup

#10 2023-08-16 15:36

Re: Checking file system at startup

#11 2023-08-16 16:30

Re: Checking file system at startup

#12 2023-08-16 16:47

Re: Checking file system at startup

#13 2023-08-16 17:23

Re: Checking file system at startup

Board footer