File System ChecK - standard Un*x/BSD utility for checking the integrity of your file system and repairing errors. Dates back to the days when a single bit of memory cost over $1000 and programmers had to economize on expensive characters (see also vi, chmod, chown, grep).
Used as a substitute profanity due to the frequency with which a failed fsck necessitated a lengthy and painful reformatting of the harddrive and reinstallation of everything from the (lost) original installation media and the (corrupted) tape backups.
If fsck won’t do it, or you don’t want to dink around with the UNIX underpinnings, you can try to get a copy of DiskWarrior and run that. It totally rebuilds your directory trees from the ground up, which should theoretically solve all your troubles. If DW can’t save your hash, I’d just as well write it off.
Still scratching my head over what could have caused this, though…
Other boards I participate in (the apple discussion boards, natch) recommended Disk Warrior too, since I have some allocation extent errors-- have since 2003, actually-- and I can’t repair permissions or anything.
And have apparently lost BSD.
So after backing up everything I can think of backing up, I’m about to launch DiskWarrior this afternoon.
What error message are you getting when you try to repair permissions?
Also note that repairing permissions is hardly a cure-all, so I wouldn’t get too hung up on that. I’d have more faith in DiskWarrior doing its job, restoring any stray Library files to their rightful places, and a full backup (which is always a good practice for any computer, natch).
It’s not that I get an error message, it’s that viewing or repairing permissions isn’t even an option; those buttons are greyed out when I launch Disk Utility. Some files disappeared into the ether (read: were overwritten because of extent allocation errors) so it looks like I have to run some sort of re-installation of OS X (10.2.8, since you asked) before re-installing the other programs that lost files.
Can’t remember if 10.2.8 had this feature or not, but I know 10.3 definitely lets you do an “Archive and Install” of the OS – it installs a fresh version of the OS, but keeps your previous version and all your user files intact. I’d give that a try.
My old computer from 1997 (which actually dates to 1995 but who’s counting) is still doing quite useful and respectable duty in my office.
rjung is right, an archive and install is the way to go at this point — all the vital components of OS X will be reinstalled but your settings and preferences and documents will be preserved intact.
And this time around you’re going to backup nightly to a separate volume, right?
Well, I must admit, the .223 acted as much as I figured it would: hot knife through butter. Even at 100 yards. When I tear things apart, I’ll see how bad it fucked up the hard drive. It ought to be cool. Right now, the thing is outside on the patio. I’m letting the snow melt out of it (I knocked it over a few times).
The .38 Special surprised me though, as it actually cleared the power supply (the .357 Mag was a given). Now, the real fun was the 20-gauge at 10 yards and 5 yards. It’s amazing what 15 feet will do. Bent the fuckin’ frame to hell!
Don’t worry, pictures forthcoming tomorrow. I feel much, much better now.
[QUOTE=AHunter3And this time around you’re going to backup nightly to a separate volume, right?[/QUOTE]
Nah, I figure any system that runs with major extent allocation errors for 18 months before causing problems is very close to rock solid. That, and nothing on my home machine warrants a daily backup…
Now, if I pick up that ipod shuffle, I might back up some essential stuff twice weekly.
You could also sign up with Apple’s .Mac service and have your essential files automatically backed up on their servers regularly. I don’t use it myself, but if you’re working with Important Stuff™, it’s an option.
