Dear support,
I use netdrive3 to move files in folder A to folder B within the same Mounted drive.
I have now gotten a few missing files when using move. I got an error message the file was unavailable on the source, however this file is also not in the destination either.
So I would like this to be fixed, if this cannot be fixed I will need to not use netdrive3 and will want a credit of netdrive3, as this didn’t happen in the TRAIL of the product.
Please disconnect and re-connect the drive item and check if there are files which were previously missing.
It seems that file move operation failed by some reason. From the log file it seems that the Synology Server returned 500 error which means internal server error.
Dear YSH,
thanks for the update, the files concerned are gone.
They are also not in my backup’s within DSM (synology) as this was a move and not a copy and then delete.
If this happened with a folder with 10 files, where I lost 4. I’m not sure where the issue is now. I have never had issues with CIFS and sFTP, but I thought webdav was a better option as this should move direct and not copy via local pc. (As I was connected remotely)
Can you please let me know how to prevent this in the future.
Should I turn on FULL logging within netdrive3 for the near future, and accept this issue could return any moment. Or just copy everything after succesful copy deleting the files manually.
Dear Jyyoon,
I think this is related indeed to the caching of certain files by bdrive netdrive3. (I was on netdrive2 but upgraded because of these issues and in the trial everything went smoothly)
Within the debug it stated that the file could not be moved as it was opened. (But it wasn’t)
so I suspect this is the cause.
And I have this only when I am transferring 3 to 6 files at the same time with the total size of 20+ gb.
Is there a setting that I can change to resolve this? as I am only moving within the webdav share itself.
FYI this time as soon as it was released the copy could resume but took within explorer 5 to 10 minutes.
So I was very patiently waiting for this move to go through.
I have an ds716Ii with an dx513 connected with esata. The dx513 is an raid5 with btfs and this worked great a few years with netdrive2. However i didn’t have active support and win10 updates wrecked the setup. Netdrive3 was the solution in trail, however now gotten this issue.
I will update you when i tested this version. Thanks so far for the help!