Humming along with Preview, Elements, Snapz Pro X and a few other apps, I noticed a screen flash and realized several items in the Menu Bar were gone.
No Clock, no Time Machine, PathFinder, current user name, etc.
I decided something was wrong!
And thought it best to Restart.
After half an eternity, I decided that the machine wasn't going to even Shut Down, much less restart! Finally used the power button. Then experienced the other half of eternity waiting for the log in screen. Or
anything besides the blue screen!
Tried Safe mode and nothing much changed. So I started looking through all the printed tips, tricks and methods and found one suggesting I use Safe mode. So much for the printed matter!
But that did slow me down enough to see that the Start Up had finally reached the Log In screen. As long as we were up and running, I ran Disk Utility and it reported one modification. Instead of running it again, I tried another Restart. Same slow as molasses results.
Now I'm really getting ticked off. Found the Single User mode method: Command-S. Much faster if not as pretty. Noticed a "...timing out!" line on the screen. About 30 seconds later, same "...timing out!" message. Didn't make much sense and that's not what I was looking for, anyway. So, the real deal here is to let the utilities in Unix do some checking/repairing of the disk. OK! I type "fsck -y", press Return and notice that another of those timing out messages came in as I was typing and corrupted my command.
Tried again and got it typed and then got a message that no checking had been done since the drive was Journaled. OK, I knew that, so what. Type the command again. Same results. No kidding!
Then I noticed some text that said I should use "-f" with the fsck command to "force" checking. What else could I do? All the time the stoopid timing out message kept coming along at the most inopportune times...but the checking finally completed and said no problems were found, the disk looks OK.
So, if your drive has Journaling enabled (standard ops in Tiger/Leopard AFAIK) you'll probably need to use "-f" instead of "-y" to get fsck to run. That's the way I see it, anyway. Why haven't I seen this before?