MD5 hash differ

What is the problem you are having with rclone?

2019/11/08 11:52:14 ERROR : Serien/_ToSort/XXX/S03/XXX.mkv: Failed to copy: corrupted on transfer: MD5 crypted hash differ "6cfb87bea1d2434d5a079d4f69307c64" vs "4272086a059629fef92768b633a543ed"
2019/11/08 11:52:14 ERROR : Serien/_ToSort/XXX/S03/XXX.mkv(0xc001e60120): failed to transfer file from cache to remote: corrupted on transfer: MD5 crypted hash differ "6cfb87bea1d2434d5a079d4f69307c64" vs "4272086a059629fef92768b633a543ed"
2019/11/08 11:52:14 ERROR : Serien/_ToSort/XXX/S03/XXX.mkv(0xc001e60120): RWFileHandle.Release error: failed to transfer file from cache to remote: corrupted on transfer: MD5 crypted hash differ "6cfb87bea1d2434d5a079d4f69307c64" vs "4272086a059629fef92768b633a543ed"
2019/11/08 11:52:14 ERROR : IO error: failed to transfer file from cache to remote: corrupted on transfer: MD5 crypted hash differ "6cfb87bea1d2434d5a079d4f69307c64" vs "4272086a059629fef92768b633a543ed"

What is your rclone version (output from rclone version)

rclone v1.50.1

  • os/arch: windows/amd64
  • go version: go1.13.4

Which OS you are using and how many bits (eg Windows 7, 64 bit)

Windows 10 64bit

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

mount --config "C:\Users\XXX.config\rclone\rclone.conf" --allow-other --drive-use-trash --cache-dir "E:\RClone\Cache01" --cache-info-age=120h --dir-cache-time=96h --drive-chunk-size 128M --vfs-read-chunk-size 128M --vfs-read-chunk-size-limit off --vfs-cache-mode writes --log-file "E:\RClone\log01.log" --log-level INFO --cache-tmp-upload-path "E:\RClone\tmp-cache01" --cache-db-path "E:\RClone\GCache01" --cache-chunk-path "E:\RClone\GCache01" --cache-tmp-wait-time=10m --buffer-size=0 --timeout=1h GCrypt01: U:

I have this since i updated yesterday to the new stable release...

No one else having this issue? :frowning:

You need to include a debug log.

Is it just this one file that you are having the problem with?

Can you paste your config with the secrets redacted please?

Can you reproduce the problem with rclone copy?

Debug log: https://gofile.io/?c=JyEsGi
Line 13456

I have this problems with more files, but there is no pattern. Some files (small ones) work after several tries.

Heres my config:

[GDrive01]
type = drive
client_id =
client_secret =
scope = drive
token = {}

[GCache01]
type = cache
remote = GDrive01:
chunk_size = 40M
info_age = 3d
chunk_total_size = 500G

[GCrypt01]
type = crypt
remote = GCache01:
password =
password2 =

rclone copy now worked:

But rclone mount is more easy for me^^

Are the files being written to as they are being uploaded? That would explain the md5 hash errors.

Nope. They are moved from the download folder. And later i move them to the mounted drive. There should be no access especially no write access to the files.

The other alternative would be that you have some RAM / Disk problem on your computer that is corrupting files.

Rclone takes a lot of care with your data checking file integrity as it transfers the data.

Can you double check (maybe with some tool) that the files aren't open? How about running a RAM test (eg memtest86) on your computer?

The files are unlocked (checked with Lockhunter), the disks are okay (chkdsk /f /r) and the RAM has also no errors. I checked it twice.

Today i copied about 120GB without problems. Now i have one file again that produces only the md5 hash differ errors...

But you think, its a problem on my side?

It sounds like it but I'm not 100% certain.

If you do the copies with rclone copy instead of copying them to the mount do you get the same error?

How about to the mount but without the cache backend?

I tried it again:

Copy with total commander to the mount: md5 hash error
Copy with rclone to the cache: md5 hash error (rclone copy D:\Test.mkv GCache01:Serien --fast-list --progress --log-file "E:\RClone\copylog01.log" --log-level INFO)
Copy with rclone to the crypt: works (rclone copy D:\Test.mkv GCrypt01:Serien --fast-list --progress --log-file "E:\RClone\copylog01.log" --log-level INFO)

So you think it might be the cache that is the problem?

How many times have you done the test?

Can something bad happen if i just delete everything inside my cache folders?

Hmm, i tried it several times. I think 5 or 6 times. I try it again, when i have more time. And then i test my use case without cache again. The last time, it was terrible slow without cache. That's why i have a cache remote.

If you run rclone once with --cache-db-purge then it will delete all the cached data, eg

rclone lsf --cache-db-purge NameOfCacheRemote:

That is probably a good idea!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.