Idea about corrupt on transfer

[Green1]

I'm afraid there's not many details even in the debug log.

rclone copy D:\Desktop\1.txt filestream: -vv
2020/12/24 16:42:27 DEBUG : rclone: Version "v1.53.3" starting with parameters ["rclone" "copy" "D:\\Desktop\\1.txt" "filestream:" "-vv"]
2020/12/24 16:42:27 DEBUG : Creating backend with remote "D:\\Desktop\\1.txt"
2020/12/24 16:42:27 DEBUG : Using config file from "S:\\Portable\\Rclone\\rclone.conf"
2020/12/24 16:42:27 DEBUG : fs cache: adding new entry for parent of "D:\\Desktop\\1.txt", "//?/D:/Desktop"
2020/12/24 16:42:27 DEBUG : Creating backend with remote "filestream:"
2020/12/24 16:42:28 DEBUG : Creating backend with remote "G:\\My Drive"
2020/12/24 16:42:28 DEBUG : fs cache: renaming cache item "G:\\My Drive" to be canonical "//?/G:/My Drive"
2020/12/24 16:42:28 DEBUG : 1.txt: Need to transfer - File not found at Destination
2020/12/24 16:42:28 ERROR : 1.txt: Failed to copy: corrupted on transfer: MD5 crypted hash differ "5f64a7c54ecf885f643bb29308e5c680" vs "dcc09d3a9fdad32f7f4e4c67717493c6"
2020/12/24 16:42:28 ERROR : Attempt 1/3 failed with 1 errors and: corrupted on transfer: MD5 crypted hash differ "5f64a7c54ecf885f643bb29308e5c680" vs "dcc09d3a9fdad32f7f4e4c67717493c6"
2020/12/24 16:42:28 DEBUG : 1.txt: Need to transfer - File not found at Destination
2020/12/24 16:42:28 ERROR : 1.txt: Failed to copy: corrupted on transfer: MD5 crypted hash differ "8bbe83fa20e22f6b9d75d0841982e8de" vs "22ddc7c70f3ba2dd8047d9828ab57e95"
2020/12/24 16:42:28 ERROR : Attempt 2/3 failed with 1 errors and: corrupted on transfer: MD5 crypted hash differ "8bbe83fa20e22f6b9d75d0841982e8de" vs "22ddc7c70f3ba2dd8047d9828ab57e95"
2020/12/24 16:42:28 DEBUG : 1.txt: Need to transfer - File not found at Destination
2020/12/24 16:42:28 ERROR : 1.txt: Failed to copy: corrupted on transfer: MD5 crypted hash differ "d839425344f21f28cc1d369918aa7e3a" vs "f5a53e834d3a2e2814af7becbb0e05ba"
2020/12/24 16:42:28 ERROR : Attempt 3/3 failed with 1 errors and: corrupted on transfer: MD5 crypted hash differ "d839425344f21f28cc1d369918aa7e3a" vs "f5a53e834d3a2e2814af7becbb0e05ba"
2020/12/24 16:42:28 INFO  :
Transferred:           153 / 153 Bytes, 100%, 1 kBytes/s, ETA 0s
Errors:                 1 (retrying may help)
Elapsed time:         0.5s

2020/12/24 16:42:28 DEBUG : 2 go routines active
2020/12/24 16:42:28 Failed to copy: corrupted on transfer: MD5 crypted hash differ "d839425344f21f28cc1d369918aa7e3a" vs "f5a53e834d3a2e2814af7becbb0e05ba"

Conf:

[filestream]
type = crypt
remote = G:\My Drive
filename_encryption = standard
directory_name_encryption = true
password = ...............................

[asdffdsa (jojothehumanmonkey)]

why not create a crypted remote in the normal way and rclone copy to that?

what does the gfstream log show?

[Green1]

I use hydrus software for managing files. It does the reading, writing and deleting, and can only work with what it thinks are directories. Mounts are a necessity.

No new entries in that log at all when copying fails.

At this point I'm pretty sure it's some way under the hood issue with something like a go library acting weird on a filesystem that's not quite real. Hence, I think that it isn't easily fixable, especially not with file stream being proprietary.
Thanks for trying though!