fsck at startup question
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?
Comments
Originally posted by Vox Barbara
Hi there,
(snip)
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?
Yep. Starup in Single User mode again (sbin/fsck -f).
If you get the "Volume can not be repaired." message it means you need to re-enter sbin/fsck -f and repeat the procedure (just hit the arrow up key and the text will appear; then ENTER).
However, the fact you will be repeating the singler user startup routine a second time may well sort out the problem.
While you're at it, you might as well run Repair Permissions from Disc Utility. And a program like MacJanitor to do those daily, weekly and monthly cleanouts would be handy, especially if your PB is often in sleep mode.
Hope this helps !
Originally posted by jackthemac
...
If you get the "Volume can not be repaired." message it means you need to re-enter sbin/fsck -f and repeat the procedure (just hit the arrow up key and the text will appear; then ENTER).
However, the fact you will be repeating the singler user startup routine a second time may well sort out the problem.
...
Did not fix the prob. Let it run dozen times. At least.
Meself thought running the fsck several times
would fix the prob. Fixed permissions also. To no avail.
Run the cronies, nothing. Hm.
The PB is stable, but the message
"Volume can not be repaired." hooks my head down.
Originally posted by Vox Barbara
Did not fix the prob. Let it run dozen times. At least.
Meself thought running the fsck several times
would fix the prob. Fixed permissions also. To no avail.
Run the cronies, nothing. Hm.
The PB is stable, but the message
"Volume can not be repaired." hooks my head down.
Have you tried a third party utility like Onyx ?
If I were you I would do a back up to dot.mac or CD of your important files, just in case it's an HD problem.
Originally posted by jackthemac
Have you tried a third party utility like Onyx ?
If I were you I would do a back up to dot.mac or CD of your important files, just in case it's an HD problem.
Cocktail. Nothing. Perhaps a Pro App like DW
would fix the problem, but this is out of reach
actually.
Backed up, just in case.
Originally posted by Vox Barbara
Cocktail. Nothing. Perhaps a Pro App like DW
would fix the problem, but this is out of reach
actually.
Backed up, just in case.
Coctail (from memory) isn't as comprehensive as Onyx or System Optimiser X. Which version of OSX are you running ?
Originally posted by jackthemac
Coctail (from memory) isn't as comprehensive as Onyx or System Optimiser X. Which version of OSX are you running ?
Mac OS X Version 10.3.9 (Build 7W98)
with all the latest updates.
(i should mention, that my PB was infected
with that "Java" bug after 10.3.9, but reinstalling
secupdate-02 IIRC solved the issue.)
Originally posted by Vox Barbara
Mac OS X Version 10.3.9 (Build 7W98)
with all the latest updates.
(i should mention, that my PB was infected
with that "Java" bug after 10.3.9, but reinstalling
secupdate-02 IIRC solved the issue.)
HMM...
I'd would
a) Wait and see what anyone else contributes
b) Download Onyx and run "Automation" having first checked the "Optimize whole system" boxes.
c) Wait for 10.4 at the weekend and do a clean install (tedious but always best).
Originally posted by Vox Barbara
Mac OS X Version 10.3.9 (Build 7W98)
with all the latest updates.
(i should mention, that my PB was infected
with that "Java" bug after 10.3.9, but reinstalling
secupdate-02 IIRC solved the issue.)
hi Voxy i like Onyx...
good luck...
Originally posted by sunilraman
hi Voxy i like Onyx...
good luck...
Oh you do like Onyx too, hear hear
Originally posted by Vox Barbara
Oh you do like Onyx too, hear hear
Yep. It needs some Onyx
Originally posted by Vox Barbara
Oh you do like Onyx too, hear hear
mostly because i can get my Bling Bling on...
edit: only a Mac utility can make system maintenance such a classy experience
Try fsck_hfs instead.
Dobby.