again - crashing info

yerodis

Registered
First thanks for the reply I get.

Today I crashed again and here are the info gived when booting in single user and passing fsck (just the quoted problems) :

BSD root : disk0s9, major 14, minor 20
...
...
-checking catalog file
Invalid leef record count
(It should be 150006 instead of 150008)

- checking multi linked files
Orphaned indirect node temp 90626

- checking volume bitmap
minor repair

-checking volume information
Invalid volume free block count
(It should be 983213 instead of 983135)

=> This is a tipical exemple of what look likes my crashes since I got my dual800 (I've seen those items so many time since one month that I'm feed up to reinstall my all system). Can someone explain me what's going on and what to do. :confused:
 
all of these are very common occurrences that can be easily fixed with a diagnostic and repair program. I reccomend Diskwarrior w/plus optimizer for defragmentation (on osx version is on the way) or †echtool pro (drive 10 if you insist on running an osx native program).
yes these cost money but you will use them often enough to make it worth the investment.

long time mac users don't reformat and reinstall to fix 99% of our problems - we have the best disk utilities programs made.
 
I second that with Ed on getting a commercial app to fix this.

When you get a leaf error, it's usually several of them.. it like a binder full of pages and they get all out of order. Had this happen a long time ago back in System 7 with some curruption problem. Norton Utilities back then was my most useful program and was able to fix my leaf errors. I think back then there had to be about 70 or 80 errors pertaining to this.

You would want to make sure that you get an app that will continue to fix these errors one after another so you don't have to check and then re-check over and over (just to save you time at least).
 
well - first thanks for your answers.
When I experience a crash usually it comes with the black unix screen and first I can read "cpu unknown error" then I reboot in single user and use fsck till I get my OSX volume OK.
I use eudora, IE, Omniweb, OfficeX, Itune, and in classic : photoshop, Illustrator, indesign and NUCD, more pitbull pro-carbon 232.

What I did since my last crash :
change my ram dimm location
re-alocate my swapfile
run mac janitor
run Xoptimise
desperatly search an utility to defragement my disks

last crash : yesterday 13h, I was not doing something special, just left my computer a few minutes and when coming back I had the unix screen above my screen saver.
 
Back
Top