fsck at startup question

Jump to First Reply
Posted:
in Genius Bar edited January 2014
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?

Comments

  • Reply 1 of 12
    Quote:

    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 !
     0Likes 0Dislikes 0Informatives
  • Reply 2 of 12
    vox barbaravox barbara Posts: 2,021member
    Quote:

    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.
     0Likes 0Dislikes 0Informatives
  • Reply 3 of 12
    Quote:

    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.
     0Likes 0Dislikes 0Informatives
  • Reply 4 of 12
    vox barbaravox barbara Posts: 2,021member
    Quote:

    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.
     0Likes 0Dislikes 0Informatives
  • Reply 5 of 12
    Quote:

    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 ?
     0Likes 0Dislikes 0Informatives
  • Reply 6 of 12
    vox barbaravox barbara Posts: 2,021member
    Quote:

    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.)
     0Likes 0Dislikes 0Informatives
  • Reply 7 of 12
    Quote:

    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).
     0Likes 0Dislikes 0Informatives
  • Reply 8 of 12
    sunilramansunilraman Posts: 8,133member
    Quote:

    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... maybe give it a shot (Onyx) and then see if fsck still throws an error



    good luck...
     0Likes 0Dislikes 0Informatives
  • Reply 9 of 12
    vox barbaravox barbara Posts: 2,021member
    Quote:

    Originally posted by sunilraman

    hi Voxy i like Onyx... maybe give it a shot (Onyx) and then see if fsck still throws an error



    good luck...




    Oh you do like Onyx too, hear hear
     0Likes 0Dislikes 0Informatives
  • Reply 10 of 12
    Quote:

    Originally posted by Vox Barbara

    Oh you do like Onyx too, hear hear



    Yep. It needs some Onyx
     0Likes 0Dislikes 0Informatives
  • Reply 11 of 12
    sunilramansunilraman Posts: 8,133member
    Quote:

    Originally posted by Vox Barbara

    Oh you do like Onyx too, hear hear



    mostly because i can get my Bling Bling on... check out the interface..!



    edit: only a Mac utility can make system maintenance such a classy experience this is why windows people hate us, right there:



     0Likes 0Dislikes 0Informatives
  • Reply 12 of 12
    dobbydobby Posts: 797member
    fsck is for ufs volumes. I don't know if it alternates automatically to hfs.

    Try fsck_hfs instead.



    Dobby.
     0Likes 0Dislikes 0Informatives
Sign In or Register to comment.