Jun 19, 2020 The FSCK method needs to be performed in single-user mode. Start the Mac computer, press and hold Command+R as the computer starts; After entering the Single User Mode, you will see a white text which will appear on the screen; To start the file system check, type the fsck –fy and hit enter. Fsck is a actually a 'front-end' for a number of file system specific checkers like fsck.vfat, fsck.ext2, etc. These do not need to be specified, but you may be able to find more advanced options in the man pages of these more precise commands. Introduction to the fsck command The fsck command follows a pattern similar to most Linux commands.
Question
My Macintosh computer doesn't boot into Mac OS X. What can I do?
Answer
Start up your computer in single-user mode to reach the command line.
Note: If necessary, perform a forced restart as described in the Emergency Troubleshooting Handbook that came with your computer. On desktop computers, you can do this by pressing the reset/interrupt button (if there is one) or holding down the power button for several seconds. On portable computers, simultaneously press the Command-Control-power keys. If your portable computer doesn't restart with this method, you may need to reset the Power Manager.
At the command-line prompt type:
/sbin/fsck -fy
Press Return. fsck will go through five 'phases' and then return information about your disk's use and fragmentation. Once it finishes, it'll display this message if no issue is found:
- The volume (name_of_volume) appears to be OK
If fsck found issues and has altered, repaired, or fixed anything, it will display this message:
***** FILE SYSTEM WAS MODIFIED *****
Important: If this message appears, repeat the fsck command you typed in step 2 until fsck tells you that your volume appears to be OK (first-pass repairs may uncover additional issues, so this is a normal thing to do).
When fsck reports that your volume is OK, type reboot at the prompt and then press Return.
Your computer should start up normally and allow you to log in.
| Operating system | Unix and Unix-like |
|---|---|
| Type | Command |
The system utility fsck (file system consistency check) is a tool for checking the consistency of a file system in Unix and Unix-like operating systems, such as Linux, macOS, and FreeBSD.[1] A similar command, CHKDSK, exists in Microsoft Windows and (its ancestor) MS-DOS.
Pronunciation[edit]
There is no agreed pronunciation. It can be pronounced 'F-S-C-K', 'F-S-check', 'fizz-check', 'F-sack', 'fisk', 'fishcake', 'fizik', 'F-sick', 'F-sock', 'F-sek', 'feshk' the sibilant 'fsk', 'fix', 'farsk' or 'fusk'.[2]
Use[edit]
Generally, fsck is run either automatically at boot time, or manually by the system administrator. The command works directly on data structures stored on disk, which are internal and specific to the particular file system in use - so an fsck command tailored to the file system is generally required. The exact behaviors of various fsck implementations vary, but they typically follow a common order of internal operations and provide a common command-line interface to the user.
Most fsck utilities provide options for either interactively repairing damaged file systems (the user must decide how to fix specific problems), automatically deciding how to fix specific problems (so the user does not have to answer any questions), or reviewing the problems that need to be resolved on a file system without actually fixing them. Partially recovered files where the original file name cannot be reconstructed are typically recovered to a 'lost+found' directory that is stored at the root of the file system.
A system administrator can also run fsck manually if they believe there is a problem with the file system. The file system is normally checked while unmounted, mounted read-only, or with the system in a special maintenance mode.
Modern journaling file systems are designed such that tools such as fsck do not need to be run after unclean shutdown (i.e. crash). The UFS2 file system in FreeBSD has a background fsck, so it is usually not necessary to wait for fsck to finish before accessing the disk. Full copy-on-write file systems such as ZFS and Btrfs are designed to avoid most causes of corruption and have no traditional 'fsck' repair tool. Both have a 'scrub' utility which examines and repairs any problems; in the background and on a mounted file system.
Mac Single User Mode Repair
The equivalent programs on Microsoft Windows and MS-DOS are CHKDSK and SCANDISK.
As an expletive[edit]
The severity of file system corruption led to the terms 'fsck' and 'fscked' becoming used among Unix system administrators as a minced oath for 'fuck' and 'fucked'.[3] It is unclear whether this usage was cause or effect, as a report from a question and answer session at USENIX 1998 claims that 'fsck' originally had a different name:
- Dennis Ritchie: “So fsck was originally called something else”
- Question: “What was it called?”
- Dennis Ritchie: 'Well, the second letter was different'[4][5]
'Go fsck yourself', is occasionally used online as an injunction to a person to go and correct their issue (attitude, ignorance of the subject matter, etc.) - in the same way that running fsck involves fixing fundamental errors.
Fsck For Mac Mojave
Examples[edit]
The following example checks the file system configured to be mounted on /usr partition; the file system needs to be unmounted first:
The following example checks the Linux JFS file system on a mdadm software RAID device:
See also[edit]
- e2fsprogs, which includes the e2fsck utility, standard on many Linux distributions
- scrub, Oracle Solaris ZFS file system checking utility
References[edit]
- ^'fsck(8) - Linux man page'. die.net. Retrieved 7 May 2013.
- ^'running 'fuck' twice almost gave me a heartattack · Issue #1 · nvbn/thefuck'. GitHub.
- ^Raymond, Eric S (September 24, 1999). 'fscking'. The Jargon File. Archived from the original on 2009-01-03.
fcking: /fus'-king/ or /eff'-seek-ing/ adj. [Usenet; common] Fucking, in the expletive sense (it refers to the Unix filesystem-repair command fsck(1), of which it can be said that if you have to use it at all you are having a bad day). Originated on {scary devil monastery} and the bofh.net newsgroups, but became much more widespread following the passage of {CDA}. Also occasionally seen in the variant ‘What the fsck?’
- ^Crosby, Matthew. 'Report from Usenix'. alt.sysadmin.recovery. Usenet. Retrieved 2016-02-20.
- ^'Mind Fsck'. WikiWikiWeb. C2.
Fsck For Mac Catalina
External links[edit]