Sponsored Content
Operating Systems OS X (Apple) OS X Support RSS Resolve startup issues and perform disk maintenance with Disk Utility and fsck Post 302256070 by Linux Bot on Friday 7th of November 2008 08:50:03 PM
Old 11-07-2008
Resolve startup issues and perform disk maintenance with Disk Utility and fsck

If your computer won't start up normally, you may need to use a disk repair utility to fix the issue. Mac OS X includes two utilities for this—Disk Utility and fsck. You can also use these even when your computer starts just fine but you want to check the disk for possible file system issues. For Mac OS X 10.4.3 or later, check out "About live verification in Mac OS X 10.4.3 or later," below. Note: If you're using Mac OS X 10.4 or later, you should use Disk Utility instead of fsck, whenever possible. In some situations, file system errors may prevent your computer from starting up. This can occur after an improper shutdown, forced restart, or power interruption. If your computer shows any of the following symptoms on startup, use a disk repair utility: Your computer partially starts but then displays a command line in a text-only environment. You may see the message, "file system dirty, run fsck." Below it, you'll see what's called a command-line prompt, indicated by a number sign (#), that allows you to type a command. If you see this, you'll need to run fsck from the command line (see "Use fsck," below). Your computer starts but either it won't reach the login screen, or it may reach the login screen but not load the Desktop after you log in. However, you can start up in single-user mode. If your computer exhibits either of the above issues, here are some things to try to get your computer back to starting up properly again. If you can't find the system discs that came with your computer, see "Use fsck," below.

More from Apple OS X Support ...
 

5 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

FSCK on veritas managed disk

I've had a VXFS filesystem get corrupted and now it won't mount. Can I run a fsck -y on the raw disk device or should something be done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Discussion started by: ozzmosiz
2 Replies

2. Solaris

Disk needs maintenance

Hi there, It's my first time here. I have an hard drive need a maintenance. here the result of metastat : Sun Microsystems Inc. SunOS 5.9 Generic May 2002 host2{11}: metastat d1: RAID State: Needs Maintenance Invoke: metareplace d1 c2t2d0s1 <new device> Interlace:... (3 Replies)
Discussion started by: Juterassee
3 Replies

3. UNIX for Dummies Questions & Answers

NEED MAINTENANCE ON DISK

hELLO PEOPLE I AM DETECTING IN THE MIRROR ON MY SPARC THAT IS A DISK ASKING FOR MAINTENANCE. d0: Mirror Submirror 0: d10 State: Needs maintenance Submirror 1: d20 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel... (0 Replies)
Discussion started by: enkei17
0 Replies

4. Solaris

Can't perform metattach with new disk, need advise.

Hi Guys, I m not ble to perform metattaach with new disk. Getting below Error:- -bash-3.00$ sudo /usr/sbin/metattach d0 d10 metattach: server03: /dev/md/rdsk/d10: No such device or address This is wht my metastat -p shows:- -bash-3.00$ sudo /usr/sbin/metastat -p Password: d4 -m... (4 Replies)
Discussion started by: manalisharmabe
4 Replies

5. Solaris

Disk corruption? Cant run fsck....

NOTICE: /: unexpected free inode 45262, run fsck(1M) fsck: cannot open vfstab Looks like /etc/vfstab (and a few other files has gone) Any ideas? Boot from cd, mount disk and recreate vfstab so that I can run fsck? (1 Reply)
Discussion started by: psychocandy
1 Replies
FSCK_EXFAT(8)						    BSD System Manager's Manual 					     FSCK_EXFAT(8)

NAME
fsck_exfat -- Verify and repair ExFAT file systems. SYNOPSIS
fsck_exfat -q device ... fsck_exfat [-f] [-p] [-y | -n] [-g | -x] [-d] device ... DESCRIPTION
The fsck_exfat utility verifies and repairs ExFAT file systems. The first form of fsck_exfat quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck_exfat checks the specified file systems and tries to repair all detected problems, requesting confirmation before making any changes. The default behavior is to always ask for confirmation of each change. Use the -n or -y options to override this default behavior. The device parameter(s) should be a path to a "raw" disk device (a character special device), such as /dev/rdisk1s1. If you specify a "non- raw" path (a block special device) such as /dev/disk1s1, or just the disk name such as disk1s1, they will automatically be converted to the corresponding raw disk device (/dev/rdisk1s1). The options are as follows: -q Causes fsck_exfat to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -f This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -p Preen the specified file systems. This option is ignored by fsck_exfat and is present only for compatibility with programs that check other file system types for consistency. -y Causes fsck_exfat to assume yes as the answer to all questions. It will attempt to repair all problems that are found. -n Causes fsck_exfat to assume no as the answer to all questions. The device will be opened read-only, and no repairs will be made. -g Causes fsck_exfat to produce its output in GUI-compatible form. Each message is printed as a tuple containing the kind of mes- sage, the message string, and number of parameters to the message string. Any parameters to the message string are printed on subsequent lines. The message string uses NSLog-like substitutions. This output format is used by applications such as Disk Utility. -x Causes fsck_exfat to produce its output in an XML-like form. Each message is printed as a plist(5) containing a message type, verbosity, message number, and message string. The message string uses NSLog-like substitutions. For message strings that contain parameters, an array of dictionaries is output. This output format is used by applications such as Disk Utility. It may be used by other kinds of applications which wish to parse the output of fsck_exfat. -d Causes fsck_exfat to produce extra debugging output. This generally contains additional details about problems found. When writing bug reports for fsck_exfat, it is usually helpful to include the output generated from this option. SEE ALSO
mount_exfat(8), fsck(8) HISTORY
The fsck_exfat utility first appeared in Mac OS X 10.6.3. Darwin January 19, 2010 Darwin
All times are GMT -4. The time now is 02:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy