Error code 120

Discussion in 'Mac Basics and Help' started by Dark Lain, Jan 22, 2006.

  1. Dark Lain macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #1
    I have a number of locked files on my computer that I can no longer access.
    When I use File > Get Info under ownerships and permissions it lists the following

    You have: No Access
    Owner : Unknown
    Group : Unknown

    When I try to change the permisions I get "The operation could not be completed. An unexpected error occurred (error code 120)."

    I've tried repairing permissions useing Disk Utility and restarting and using Disk Utility from the Install DVD

    OSX 10.4.3


    Please Help
     
  2. iMeowbot macrumors G3

    iMeowbot

    Joined:
    Aug 30, 2003
    #2
    Is that 120 or -120? If -120, that means directory not found, which kind of hints at a corrupted disk given the other stuff you are seeing.

    Repairing permissions is probably not what you want anyway, it won't fix most files (where are the files, in Applications, Library, your home folder, or somewhere else?). Are there any error messages when you try to verify the disk (not permissions)?
     
  3. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #3
    The files are located on my Home Folder in Documnets and Pictures

    I just tried verifing the disk and got the following results.

    Volume Header needs minor repair
    The volume Macintosh HD needs to be repaired.

    Error: The underlying task reported failure on exit

    1 HFS volume checked
    Volume needs repair

    because of the above error i am unable to repair the disk
     
  4. iMeowbot macrumors G3

    iMeowbot

    Joined:
    Aug 30, 2003
    #4
    You can try booting into single user mode and running fsck by hand. Here are the instructions at Apple. Yeah, if the stuff is in your home folder, repair permissions will do nothing for you.
     
  5. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #5
    I tride booting in single user mode and successfuly repaird the disk but this did not solve the problem of the locked files that are inaccessible and cant have permisions changed.
     
  6. jeremy.king macrumors 603

    jeremy.king

    Joined:
    Jul 23, 2002
    Location:
    Fuquay Varina, NC
    #6
    if you feel comfortable using Terminal, you should try to change the permissions using the chmod command.

    For example,

    Code:
    sudo chmod 774 /path/to/your/problem/file
    if you want to learn more about the command type

    Code:
    man chmod
     
  7. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #7
    I'll try this latter on tonight or tomorrow

    Thanks for all the advice.
    updates to my problem when I can get around to it.
     
  8. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #8
    I haven't tried the Terminal idea yet but I have found a partial alternate solution that works. I create a new folder and move the locked files to it and for some reason the copied locked file permissions now work. I can then delete the locked files that don't work. However this does not work with locked folders I can copy the files in the folder but I can't erase the original locked folder and files


    Again thanks for all the usefule advice.
     
  9. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #9
    I tride the Terminal command mentioned above and got the following result "no such file or directory"
     
  10. jeremy.king macrumors 603

    jeremy.king

    Joined:
    Jul 23, 2002
    Location:
    Fuquay Varina, NC
    #10
    Well, I am guessing you have the wrong path to the file. Make sure that if one of the folders contains a space that you escape it with a backslash.

    Again, type man chmod in Terminal to learn all about the command.
     
  11. Dark Lain thread starter macrumors member

    Dark Lain

    Joined:
    Apr 29, 2005
    #11
    I tried the Terminal method again being careful with the path and recieved the following result "Operation not permitted"
     
  12. Leareth macrumors 68000

    Leareth

    Joined:
    Nov 11, 2004
    Location:
    Vancouver
    #12
    I had some files like this last week
    didnt do anything could not delete them , and kept getting -120 error
    used Spring cleaning to get rid of them and no problems since :)
     
  13. Milquetoast macrumors newbie

    Joined:
    Apr 14, 2008
    Location:
    Maryland
    #13
    Robust solution found?

    New member, old thread...

    I had a similar problem. File owned by root.
    I'd rather not set up root on the box.

    Could not trash the file, change ownership in the get info box, etc. Got the Error 120 from the Finder.

    Could not move the file to another folder as the Finder would force a copy (didn't think to try with Terminal, but I suspect that wouldn't work either). FWIW, the copy of the file was now fully controllable. I didn't need it.

    Nothing I could do with Terminal and sudo would work (and I'm experienced with UNIX for decades - I suspect before sudo was written;)).

    What worked for me was to do the following from the Finder:
    1. create a new folder at the same level as the enclosing folder (could be anywhere on the same volume),
    2. move all other files to it,
    3. trash the current folder containing only the offending file
    4. Empty the Trash
    5. rename the new folder to the proper name

    Given the 120 error type (HFS "Directory not found"?), it sounds like some data structure in the parent directory (the directory list itself, the file inode pointer?) was hosed.

    This was in user space (low risk). I have two other files in /Library/Preferences with similar attributes. They may be a bit trickier. May have to boot from elsewhere to get rid of safely.
     
  14. jaiyenyen macrumors newbie

    Joined:
    May 17, 2008
    #14

Share This Page