Hi there,
Just out of curiosity (there was really no need to do that,
because everything is or seemed to be fine) i booted my PB
into Single User Modus. Then i performed
a "fsck -f" and - surprisingly - fsck found a problem.
After the 3rd phase of checking (Checking Catalog file)
a message appeared (Missing thread record id72635)
The following phases found some minor probs, which
usually got repaired.
That is it. After the whole checking process was finished
the message "Volume can not be repaired." appeared.
WTF??? What does that mean exactly? Something concerning
hardware? Maybe software?
I checked the volume from the Installer CD, same thing.
I have no idea what happend. The system behaves pretty
normal so far. I don't have time to deal with
this issue, so someone better tell me that i safely
can ignore this message
Any ideas?
Just out of curiosity (there was really no need to do that,
because everything is or seemed to be fine) i booted my PB
into Single User Modus. Then i performed
a "fsck -f" and - surprisingly - fsck found a problem.
After the 3rd phase of checking (Checking Catalog file)
a message appeared (Missing thread record id72635)
The following phases found some minor probs, which
usually got repaired.
That is it. After the whole checking process was finished
the message "Volume can not be repaired." appeared.
WTF??? What does that mean exactly? Something concerning
hardware? Maybe software?
I checked the volume from the Installer CD, same thing.
I have no idea what happend. The system behaves pretty
normal so far. I don't have time to deal with
this issue, so someone better tell me that i safely
can ignore this message

Any ideas?
" I will not commit anything to memory that I can get from another source . . . "
ALBERT EINSTEIN
ALBERT EINSTEIN
" I will not commit anything to memory that I can get from another source . . . "
ALBERT EINSTEIN
ALBERT EINSTEIN





maybe give it a shot (Onyx) and then see if fsck still throws an error
this is why windows people hate us, right there: