FSCK.MINIX(8)

๐Ÿ’พ FSCK.MINIX(8) โ€” the check-consistency-of-Minix-filesystem girlies' manual ๐Ÿ’…

okay bestie sit DOWN because we're talking about fsck.minix, aka the System Administration page you pull up when your MINIX filesystem is acting up and you need a vibe check. this is section 8 of the manual, so yes it's a big-girl sysadmin situation. ๐ŸŽ€


โœจ SYNOPSIS โœจ

fsck.minix [options] device

that's it. that's the whole thing. options and a device. we love a simple girl. ๐Ÿฆ‹


๐ŸŒธ DESCRIPTION ๐ŸŒธ

so like, fsck.minix does a consistency check for the Linux MINIX filesystem. it's the friend who shows up, looks around, and goes "girl... this is a mess" (or "you're fine, slay"). ๐Ÿ”ฅ

the program assumes the filesystem is quiescent. and fsck.minix should not be used on a mounted device unless you can be sure nobody is writing to it. remember bestie โ€” the kernel can write to the device when it searches for files. so it's giving "don't touch my stuff while i'm still in it". ๐Ÿ˜ญ

the device name will usually have the following form:

  • /dev/hda[1-63] โ€” IDE disk 1
  • /dev/hdb[1-63] โ€” IDE disk 2
  • /dev/sda[1-15] โ€” SCSI disk 1
  • /dev/sdb[1-15] โ€” SCSI disk 2

if the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS BEEN CHANGED" and will sync(2) three times before exiting. there is no need to reboot after check. iconic. no restart era. ๐Ÿ‘‘


๐Ÿšจ WARNING ๐Ÿšจ

fsck.minix should not be used on a mounted filesystem. using fsck.minix on a mounted filesystem is very dangerous, due to the possibility that deleted files are still in use, and can seriously damage a perfectly good filesystem! if you absolutely have to run fsck.minix on a mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for deletion.

like bestie i am BEGGING you. ๐Ÿ’€ do not. unless you literally must. and then be so so careful.


โœจ OPTIONS โœจ

  • -l, --list โ€” list all filenames. show me everyone. ๐Ÿซถ
  • -r, --repair โ€” perform interactive repairs. it asks, you answer, y'all chat. ๐Ÿ’ฌ
  • -a, --auto โ€” perform automatic repairs. this option implies --repair and serves to answer all of the questions asked with the default. note that this can be extremely dangerous in the case of extensive filesystem damage. ๐Ÿšฉ so like... auto-mode is not always the moment.
  • -v, --verbose โ€” be verbose. spill the tea. โ˜•
  • -s, --super โ€” output super-block information. the super-block! main character energy honestly. ๐Ÿ‘‘
  • -m, --uncleared โ€” activate MINIX-like "mode not cleared" warnings.
  • -f, --force โ€” force a filesystem check even if the filesystem was marked as valid. marking is done by the kernel when the filesystem is unmounted. so basically "i don't care that it says it's fine, check it anyway". ๐Ÿ’…
  • -h, --help โ€” display help text and exit. ๐Ÿ†˜
  • -V, --version โ€” display version and exit. ๐Ÿท๏ธ

๐Ÿฉบ DIAGNOSTICS ๐Ÿฉบ

there are numerous diagnostic messages. the ones mentioned here are the most commonly seen in normal usage. ngl there's a lot of yapping potential here but we're keeping it to the hits. โœจ

  • if the device does not exist, fsck.minix will print "unable to read super block".
  • if the device exists, but is not a MINIX filesystem, fsck.minix will print "bad magic number in super-block".

both of these are giving "sweetie that's not a filesystem". ๐Ÿ™ˆ


๐Ÿ”ข EXIT STATUS ๐Ÿ”ข

the exit status returned by fsck.minix is the sum of the following:

  1. 0 โ€” No errors. clean girl. โœจ
  2. 3 โ€” Filesystem errors corrected, system should be rebooted if filesystem was mounted.
  3. 4 โ€” Filesystem errors left uncorrected. ๐Ÿ˜ญ
  4. 7 โ€” Combination of exit statuses 3 and 4.
  5. 8 โ€” Operational error.
  6. 16 โ€” Usage or syntax error.

and yes bestie, it's a SUM. so read it like math class. ๐Ÿงฎ


๐Ÿ‘‘ AUTHORS ๐Ÿ‘‘

  • Linus Torvalds <torvalds@cs.helsinki.fi>.
  • Exit status values by Rik Faith <faith@cs.unc.edu>
  • Added support for filesystem valid flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>.
  • Check to prevent fsck of mounted filesystem added by Daniel Quinlan <quinlan@yggdrasil.com>.
  • Minix v2 fs support by Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai Langfeldt <janl@math.uio.no>.
  • Portability patch by Russell King <rmk@ecs.soton.ac.uk>.

look at this roster. legends only. ๐Ÿ’œ


๐ŸŒˆ SEE ALSO ๐ŸŒˆ

iykyk. go read your siblings' manuals too, they're all part of the same family. ๐Ÿฆ‹


๐Ÿ› REPORTING BUGS ๐Ÿ›

for bug reports, use the issue tracker at https://github.com/util-linux/util-linux/issues.

found a bug? tell the girlies. do NOT just suffer in silence. ๐Ÿซถ


๐Ÿ“ฆ AVAILABILITY ๐Ÿ“ฆ

the fsck.minix command is part of the util-linux package which can be downloaded from the Linux Kernel Archive at https://www.kernel.org/pub/linux/utils/util-linux/.


and that's the whole page bestie!! ๐ŸŽ€โœจ this was util-linux version 2.42.4, dated 2026-09-21 โ€” so you know exactly which era of the manual you just read. now go unmount that filesystem before you touch it. periodt. ๐Ÿ’…๐Ÿ‘‘๐ŸŒธ

๐Ÿ“ฆ where this page comes from
  • arch rolling: util-linux 2.42.4-1 ยท BSD-2-Clause AND BSD-3-Clause AND BSD-4-Clause-UC AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND ISC AND LGPL-2.1-or-later AND LicenseRef-PublicDomain
  • ๐Ÿ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms