man > fsck.minix(8)

📛 NAME

fsck.minix - check consistency of Minix filesystem

🚀 Quick Reference

Use CaseCommandDescription
Check filesystem (read-only)fsck.minix /dev/sda1🔍 Perform a consistency check without repairs
Interactive repairfsck.minix -r /dev/sda1đŸ› ī¸ Repair interactively, prompting for each fix
Automatic repairfsck.minix -a /dev/sda1⚡ Repair automatically (dangerous on damaged filesystems)
Force checkfsck.minix -f /dev/sda1âš ī¸ Force check even if marked valid
List all filenamesfsck.minix -l /dev/sda1📋 List all files on the filesystem
Show superblock infofsck.minix -s /dev/sda1📄 Display superblock details

📋 SYNOPSIS

fsck.minix [options] device

📝 DESCRIPTION

fsck.minix performs a consistency check for the Linux MINIX filesystem.

The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writing to it. Remember that the kernel can write to device when it searches for files.

The device name will usually have the following form:

DeviceDescription
/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 CHANGED" and will sync(2) three times before exiting. There is no need to reboot after check.

âš ī¸ 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.

âš™ī¸ OPTIONS

đŸ”Ŧ DIAGNOSTICS

There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.

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".

đŸšĒ Exit Codes

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

👤 AUTHORS

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

📚 SEE ALSO

fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)

🐛 REPORTING BUGS

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

đŸ“Ļ AVAILABILITY

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

fsck.minix(8)
📛 NAME 🚀 Quick Reference 📋 SYNOPSIS 📝 DESCRIPTION âš ī¸ WARNING âš™ī¸ OPTIONS đŸ”Ŧ DIAGNOSTICS đŸšĒ Exit Codes 👤 AUTHORS 📚 SEE ALSO 🐛 REPORTING BUGS đŸ“Ļ AVAILABILITY

Generated by phpman v4.10.0-7-g98e9fd5 · Markdown · JSON · MCP Author: Che Dong Under GNU General Public License
2026-09-15 20:30 @216.73.217.178
CrawledBy Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Valid XHTML 1.0 Transitional!Valid CSS!

^_top_^