OS X acting up...

[crenz]

Suddenly, my installation of OS X has begun acting up: Every time I reboot, the dock is replaced by the standard dock. Safari will tell me upon startup that it has problems saving my bookmarks and will forget some preferences. Plus it will crash if I enter anything into a textfield (am posting this using IE).

I already repaired the permissions, but that didn't seem to help. Any clues?

 

[Mblazened]

Re-install os x

 

[crenz]

Originally posted by Mblazened
Re-install os x

Thanks

Well, I did an fsck -y in single-user mode. That helped, but Safari still crashes more often than normal... *sigh*.

 

[Horrortaxi]

Before going to the trouble of reinstalling, create a new user and see if you still have the same problem.

 

[arn]

Re: OS X acting up...

Originally posted by crenz
Suddenly, my installation of OS X has begun acting up: Every time I reboot, the dock is replaced by the standard dock. Safari will tell me upon startup that it has problems saving my bookmarks and will forget some preferences. Plus it will crash if I enter anything into a textfield (am posting this using IE).

I already repaired the permissions, but that didn't seem to help. Any clues?

Did you run out of hard drive space?

Are you close? (within megabytes?)

if so, clear some space. Mac OS X can act very weird when it hits the Virtual Memory wall, and lose all your prefs.

arn

 

[idea_hamster]

Originally posted by crenz
I did an fsck -y in single-user mode. That helped...

If you ran fsck and it came back with anything besides "[volume] seems to be ok", you should run fsck again.

As I understand it, as fsck fixes problems, it can uncover others that won't be fixed unless you run it again. In general, four passes of fsck is enough to fix pretty much every thing that fsck can fix. After that, you should go to third-party software (DiskWarrior, etc.).

Best of Luck!

 

[crenz]

Thanks for the suggestions (arn, you're doing support now? Guess there's not much news at the moment ). fsck didn't come up with any error messages, so I didn't start it again. It still helped
I'm quite surprised -- on Linux, fsck seems to be much more verbose.

I actually did run out of disk space earlier and freed up space when I noticed it. The trouble I described started shortly afterwards. Guess I'll better make sure I don't run out of disk space again...