Finder error -50 when moving files from external NTFS hard disk

errorfinderntfs

As per title, I'm using a external NTFS hard disk for storage (guess it doesn't matter the type, but I can give more informations if needed). It happen many times, however, that I receive Finder error -50

The operation could not be completed.
An unexpected error occurred (error code -50).

when trying to remove files (it also happen when move files from the external hd to the local one, dragging and dropping with cmd pressed).
I read on the web that it may be related to illegal characters in files' names, however it seems to happen also for files that have nothing "strange" in the name (i.e. asdf.txt).

Besides, when the popup appears, the file gets deleted even if I cancel the operation.

I'm using MacOS 10.7.4 and Paragon NTFS 9.0.1 for enabling NTFS read/write.

Any idea of what may be the error?

Best Answer

As you might expect, it is an error copying between disparate file systems. This is a link to a very old Apple Support Document. It does however, give you the shell script to handle the copy/delete from terminal.

Another possible solution is this app: Tuxera instead of Paragon.

Related Solutions

MacOS – How to you avoid error -43 when copying symlinked folder in Finder with a SAMBA share

In your configuration, you have unix extensions = no which is fine, but that is why symbolic links on the server are showing up as folders and not aliases. In this mode the server resolves the symbolic links and the client never sees them. If the client tries to create a symbolic link, the server actually generates an alias file, not a host-OS symbolic link. Reasons for this include security (preventing someone from getting access to /etc/passwd on the server by creating a symbolic link to it) and client compatibility, as OS X and Windows and Unix have slightly different ideas about what constitutes a symbolic link but they pretty much agree on what is a directory or a file.

Permissions issues with SAMBA are complex, so it's not clear that you do not have a permissions issue. Likewise symbolic like resolving is complex, so it is not clear that what you are doing should, in theory work, and there's always the possibility of a bug (most likely in the SAMBA server).

When accessing a SAMBA server from a Mac, these identities and permissions are involved:

The Mac User you are logged into the Mac as
The SAMBA user you are logged into the SAMBA server as
The SMABA server host OS user you get converted to
Unix-style file permissions
For NTFS and HFS+, associated file-system ACLs

So even though you have provided a lot of information, it's still not clear that you are not having permissions problems. The fact that you can mv and cp on the server (using what account?) does not mean you do not have a permissions problem preventing you from doing it on the client (using what accounts and with what effective account on the server?).

If the server is supporting ACLs and since you have options like inherit permissions = yes and inherit acls = yes set there could be some kind of ACL problem that is only allowing read access to directories accessed via symbolic links. There are several other avenues of investigation based on the server configuration.

I would really expect you should be able to find more information in the SAMBA server logs than you have communicated. They should give you a much better sense of exactly what is being denied.

For what it is worth, I tried to duplicate your setup using an Ubuntu 12.04 host as the SAMBA server and could not reproduce your problem. Symbolic links worked for me as expected.

MacOS – How to open shell scripts in editor when double clicking on them

Install duti by running brew install duti, save a file like

com.apple.TextEdit public.unix-executable all

as ~/.duti, and then run /usr/local/bin/duti ~/.duti. After that executable scripts with no filename extension should be opened in TextEdit.

Another option is to run plutil -convert xml1 ~/Library/Preferences/com.apple.LaunchServices.plist, open the plist in a text editor, add an entry like

<dict>
  <key>LSHandlerContentType</key>
  <string>public.unix-executable</string>
  <key>LSHandlerRoleAll</key>
  <string>com.apple.TextEdit</string>
</dict>

under LSHandlers, and then restart to apply the changes.

The default application for shell scripts with a .sh extension can be changed from Finder:

Best Answer

Related Solutions

MacOS – How to you avoid error -43 when copying symlinked folder in Finder with a SAMBA share

MacOS – How to open shell scripts in editor when double clicking on them

Related Question