Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Error code 120

Dark Lain

Dark Lain

macrumors member
Original poster
Apr 29, 2005
49
6
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
 
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)?
 
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
 
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.
 
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.
 
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
 
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.
 
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.
 
I tride the Terminal command mentioned above and got the following result "no such file or directory"
 
Dark Lain said:
I tride the Terminal command mentioned above and got the following result "no such file or directory"
Click to expand...

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.
 
I tried the Terminal method again being careful with the path and recieved the following result "Operation not permitted"
 
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 :)
 
Robust solution found?

Dark Lain said:
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.
Click to expand...

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.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back