Did you try reboot, cmd-S, fsck -y?

Search

From our Sponsor...

User Functions

Don't have an account yet? Sign up as a New User
Lost your password?

What's New:

Hints

No new hints

Comments last 2 days

Links last 2 weeks

No recent new links

What's New in the Forums?

The Editor's Corner...

Here are some of my (robg) other projects...

•	The Robservatory My blog - Macs, tech, etc.
•	Mac OS X Power Hound The best of Hints in print
•	Inside iWork An iWork training DVD
•	Macworld Column, features, online...

Hints by Topic

News from Macworld

The macosxhints Poll

What version of OS X are you running as your main OS?

Other polls | 11,457 votes | 42 comments

Did you try reboot, cmd-S, fsck -y? | 10 comments | Create New Account

Click here to return to the 'Did you try reboot, cmd-S, fsck -y?' hint

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Did you try reboot, cmd-S, fsck -y?
Authored by: Lectrick on Wed, Oct 10 2007 at 9:13AM PDT

This looked like a corrupted filesystem to me.

I would have rebooted, held down command-S to go into singleuser mode, then typed fsck -y, waited, if errors then repeat fsck -y until none, then "exit" to go to the mac GUI. ;)

Then run repair permissions in disk utility.

---
In /dev/null, no one can hear you scream