Windows -> F2-210 with USB Drive (NTFS) connected can write small files, but struggles with a 20gb file with the error
the USB drive will quite happily hold a 100gb file (Virtual Hard Drive) put onto it via USB Copy as part of a backup routine (from the F2-210 every day), so the drive connected to the F2-210 is set up correctly
if i plug the USB into a windows 10 computer and share it, i can copy the exact same file 20gb to the USB without any problems across the network to it, so again suggests that the USB drive is fine and its not a windows issue but something to do with the F2-210 that is causing it?
is there a problem with the SMB implementation when it comes to detecting the host of the file share as this might be somethng thats different, although both show Dialect 3.1.1 when i do Get-SMBConnection from powershell
luckily i only use the USB as a backup drive so the fact that USB Copy can write to the drive means its not an actual issue to me as i wouldnt be wanting to copy files over the network to the USB drive, they go to the actual NAS drive which the 20gb file copies to without any issues also
not sure ive helped at all but atleast confirmed / ruled out certain things
Same issue here: copying large files from a local folder to a network share pointing to the external drive connected to USB port of the NAS returns error 0x8007003B.
Copying the same file directly on the NAS' internal drives works flawlessly, as does copying the file on the same USB Drive when it is directly connected via USB to the PC instead of the NAS.
I started experiencing this issue since I updated my F2-421 to FW4.2.30, and is still happening after upgrading to 4.2.32.
So I would say OP is not the only one having the issue, and it would be appropriate to fix the problem in the next update - shouldn't be impossible to figure out what caused it by analysing which changes were introduced by 4.2.30 regarding external drive management...
Is anyone at Terramaster looking into this?
This has now been reported multiple times by several different users (see also viewtopic.php?f=28&t=3212), so it's clearly due to the 4.2.30 update: can we expect this to be fixed anytime soon?
I had this same problem after updating the NAS to 4.2.32, here is how I got it fixed. Everything you find on google won't work because the root cause of this problem is the NAS itself. I luckily had a device configuration backup from around 3 months ago and by restoring the configurations the issue disappeared. Please note that by restoring the configuration it apparently also changes your device password to what you had at the time of creation so make sure you had set up a way to restore your password via e-mail or phone at that time. If you don't have a configuration backup that you made when the device was working normally then it seems you will have to reinstall the OS itself(without losing data*contact terramaster support?*) or just wait until a new update is released and that hope that fixes it. Cheers.