Leo: /* Disabling Filesystem Check */

2019-09-01T05:59:08Z

Disabling Filesystem Check

← Older revision		Revision as of 05:59, 1 September 2019
Line 14:		Line 14:

	Where:		Where:
	{{code\|-c}} is the maximum number of mounts before a check is required.		{{code\|-c}} is the maximum number of mounts before a check is required.

			The order of the fsck that occurs is dependent on the sixth field of {{code\|/etc/fstab}}. When setting the fs_passno field to 0, fsck will assume that the filesystem does not need to be checked.

	=== Kernel Parameter ===		=== Kernel Parameter ===

Leo: initial content

2019-09-01T05:55:51Z

initial content

New page

A filesystem check might occur when a system is brought up if any of the following conditions are true:
# The filesystem requires one (eg. number of mount counts, or number of days since last check exceeds some value)
# The filesystem was uncleanly mounted (most systems)
# A filesystem check was forced (eg. {{code|1=fsck.mode=force}} is passed as a kernel parameter)

There are a few ways to explicitly disable filesystem checks.

== Disabling Filesystem Check ==
=== Tunable System parameter ===
Use the {{code|tune2fs}} command to change the number of mounts before a check is required to {{code|0}} to disable it.
{{highlight|lang=terminal|code=
# tune2fs -c 0 /dev/sda1
}}

Where:
{{code|-c}} is the maximum number of mounts before a check is required.

=== Kernel Parameter ===
Append the {{code|1=fsck.mode=skip}} parameter to the kernel on startup. This can be done either by editing the boot menu config or by changing it in the boot menu.

Inversely, you can force a check by specifying {{code|1=fsck.mode=force}} and {{code|1=fsck.repair=yes}}.

== Legacy ==
The old tricks of using {{code|/fastboot}} or the {{code|shutdown -f}} method only worked with the old SysVinit and early versions of Upstart and do not work with systemd.

[[Category:Linux]]

Disable Filesystem Check on Startup - Revision history

Leo: /* Disabling Filesystem Check */

Leo: initial content