Despite its user-friendly interface, OS X sometimes gives no more information than an error code when something goes wrong. One of these is error code -50, which may occur when you attempt to copy, move, or delete files from external hard drives. If this occurs and you are stuck with a file you cannot manage, then you can likely overcome this error with a few possible approaches.
1. Check your drive with Disk Utility
First, ensure the drive’s formatting is OK, by using Disk Utility to run a verification routine on the storage volume that contains the file. To do this, select the volume in Disk Utility’s sidebar, and then go to the First Aid tab and click Verify Disk. If any errors show up (text in red), then use the Repair button to fix them.
As a general and less-intrusive approach, you can also try ejecting your drive, followed by unplugging it. Then reboot your system, and then plug your drive in again. When it mounts, try managing the file on it.
3. Rename the file
One quick solution to this problem, suggested by MacIssues reader Matt, is to try renaming the file. Give it a general name like “myfile.txt” and confirm that you want to change the file extension (or even remove it). Then attempt to move or delete the file using the OS X Finder, and hope for success.
4. Use the Terminal to manage the file
The Finder moves files using more checks and restrictions that Terminal commands, so you might have better luck moving or deleting the file using the Terminal.
To delete the file, type “rm -f ” followed by a single space, then drag the file to the Terminal window and press Enter. If the Terminal states the file cannot be deleted because you do not have permissions, then run the command “sudo !!” (the word “sudo” followed by a space and then two exclamation points) to re-run the prior command while prefixing it with “sudo” so it will run as administrator. Enter your password when prompted (it will not show when typed), and the command should now successfully run.
To move the file instead of deleting, perform the following steps in the Terminal:
- Type “mv ” followed by a single space.
- Drag the problematic file from the Finder to the Terminal window (its path should be entered).
- Similarly drag the destination folder to the Terminal window.
- Press Enter to execute the command.
As with removing the file, if this gives you a permissions-related error, then enter “sudo !!” and authenticate to repeat the command as administrator. You might also use “cp” instead of “mv” to invoke a copy action (as opposed to moving it). This will still have the problematic one stuck in its location, but you should be able to preserve the copy in case you cannot recover the first.
3. Rename the file.
On an external HD it is not likely the OS is preventing an important file from being deleted, still this is a possiblitiy. Be very sure the file you want to delete is not an important file you will regret before renaming and deleting the file.
But what actually IS error -50, and is there a list of these somewhere?
Here’s one list:
“error -50 paramErr: error in user parameter list”
Cryptic, as per usual.
I find it baffling that a company like Apple which prides itself on it’s usability and design prowess still has not replaced this arcane error reporting system with a modern version…
I suggest to give them feedback about this via http://www.apple.com/feedback/macosx.html
In the meantime, If you want to get a slightly less unhelpful textual message for an error code, go into the Terminal and type “macerror ERRORNUMBER”.
Perfect, you provided a solution to my problem 🙂 Cheers
None of the solutions here work for me, even the Terminal approach. “Invalid argument” error. I hate when dumb people code operating systems.
awesome post. I would suggest a TarDisk as the best way to upgrade MacBooks with no tools. I had an external and then bought this thing and it works flawlessly – http://www.tardisk.com
Hi there, all is going perfectly here and ofcourse every one is sharing data,
that’s actually good, keep up writing.
I just like the valuable info you supply for your articles.
I will bookmark your blog and test again here regularly.
I am relatively certain I’ll learn many new stuff right here!
Good luck for the following!
Just to share:
while copying a complete OS X MacBook Pro disk to a new one, the WHOLE process is flawed because of ONE file… the Google Earth installer. What is really interesting is that no matter what you do or try to do through traditional processes or through advanced ones, it’s impossible to remove this file from the drive and so it is impossible to copy the whole disk in one go, since everything will stop once the process tries to copy the faulty file. This is the first time since my Apple II that I feel completely clueless and frustrated!
And I can see no one has found a way to fix this… not even using sudo in the Terminal.