google cloud sync failing

[pplui]

newbie here, doing my first baby steps on truenas

I want to have a copy of my google drive in truenas, and be able to sync them both ways
Created credential, created the cloud sync task, and it is partially working
My settings are:
Direction:Pull
Transfer mode: SYNC

but:

It is not synchronizing from my local truenas drive to google drive
Status shows failed :

Code:

<6>INFO  :
Transferred:                 0 / 0 Byte, -, 0 Byte/s, ETA -
Elapsed time:         1.0s

<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
<5>NOTICE: AndroMoney.xlsx: Duplicate object found in source - ignoring
... 60820 more lines ...
<6>INFO  : alquiler/02 Setterington/2009/Claims/Re update.pdf: Copied (new)
<6>INFO  : alquiler/02 Setterington/2009/Claims/meeting.pdf: Copied (new)
<6>INFO  : alquiler/02 Setterington/2009/Claims/payment.pdf: Copied (new)
<6>INFO  : alquiler/02 Setterington/2009/Claims/update.pdf: Copied (new)
<6>INFO  : alquiler/02 Setterington/2009/Claims/Meeting.pdf: Copied (replaced existing)
<6>INFO  : alquiler/02 Setterington/2009/Claims/Payment.pdf: Copied (replaced existing)
<3>ERROR : Local file system at /mnt/pool/_cloud_backups drive: not deleting files as there were IO errors
<3>ERROR : Local file system at /mnt/pool/_cloud_backups drive: not deleting directories as there were IO errors
<3>ERROR : Attempt 3/3 failed with 39 errors and: corrupted on transfer: md5 hash differ "5ff1438200f898727ed6f9f16eb3768a" vs "19377a22da3cc759fc9d9c7e84daac75"
Failed to sync with 39 errors: last error was: corrupted on transfer: md5 hash differ "5ff1438200f898727ed6f9f16eb3768a" vs "19377a22da3cc759fc9d9c7e84daac75"

How can i solve this?

 

[MrT_134]

For the md5 hash differ errors, I'm seeing a similar issue reported on the rclone forums with a couple possibilities mentioned like the files could be in use while the task is running or there is a RAM or disk problem with the hardware that could be causing file corruption.

 

[sfatula]

rcloning live files is indeed quite a common reason for the md5 errors.