- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Can´t copy a file, getting error operation not supported in ReadyNas102
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can´t copy a file, getting error operation not supported in ReadyNas102
Hi team, i getting error "operation not supported" in the backup routine when trying to ready a file to write in a USB or even to my desktop OS Windows 10.
The file is a video with 574Mb.
I am using the backup feature from ReadyNAS sending the file to USB Back Top port.
Model: ReadyNAS 102
OS 6.5.2
Could you please if it is a common error and maybe there is a solution?
Tnx
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can´t copy a file, getting error operation not supported in ReadyNas102
Is the file on the NAS? If so, can you copy it to your PC?
Also, you can try inserting the USB drive in a PC, and if Windows offers to "repair it", then let it. Sometimes a USB drive isn't ejected properly, and then the NAS will mount it read-only. Linux doesn't handle unexpected removal as nicely as Windows.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can´t copy a file, getting error operation not supported in ReadyNas102
Yes, files are on the NAS. I can´t copy them to PC or USB Hard drive.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Can´t copy a file, getting error operation not supported in ReadyNas102
@Maikon_Zeppe wrote:
Yes, files are on the NAS. I can´t copy them to PC or USB Hard drive.
If these are in a public share, then (as a test) try setting "allow anonymous access" on the network access tab for the share. If that fails, try resetting the file permissions on the file access tab (using the reset control on the left).
Are there any indications in the log that the NAS isn't healthy?