Task run error - Rclone to Google Drive

TrueNAS General
1

Hello. I kept having error trying to run PULL/SYNC cloud task to Google Drive.

Knowledge level = beginner (inapt on terminology and how things work in FreeNAS/ TrueNAS so please bear with me).

As highlighted above. I was on FreeNAS 11.3 so decided to give TrueNAS a go by upgrading. Upgrade was simple, clicking a few buttons, rebooting and what not. Thought it might resolve the issue to no avail.

Below are the error.

Please help provide step by step (if possible) methods to troubleshoot and resolve the issue of not syncing. Assistance much appreciated.

–

Error: Traceback (most recent call last):
File “/usr/local/lib/python3.9/site-packages/middlewared/job.py”, line 355, in run
await self.future
File “/usr/local/lib/python3.9/site-packages/middlewared/job.py”, line 391, in __run_body
rv = await self.method(*([self] + args))
File “/usr/local/lib/python3.9/site-packages/middlewared/schema.py”, line 981, in nf
return await f(*args, **kwargs)
File “/usr/local/lib/python3.9/site-packages/middlewared/plugins/cloud_sync.py”, line 1098, in sync
await self._sync(cloud_sync, options, job)
File “/usr/local/lib/python3.9/site-packages/middlewared/plugins/cloud_sync.py”, line 1145, in _sync
await rclone(self.middleware, job, cloud_sync, options[“dry_run”])
File “/usr/local/lib/python3.9/site-packages/middlewared/plugins/cloud_sync.py”, line 242, in rclone
raise CallError(message)
middlewared.service_exception.CallError: [EFAULT] Checks: 3261924 / 3261924, 100%
Transferred: 15 / 15, 100%
Elapsed time: 3h43m29.2s

2024/10/20 09:27:17 Failed to sync: failed to open source object: open file failed: Use the --drive-acknowledge-abuse flag to download this file: googleapi: Error 403: This file has been identified as malware or spam and cannot be downloaded., cannotDownloadAbusiveFile

2

Yeah +1 with this!

It’s a perenniul issue - and affects scale as well - just ran into it today on 25.04.1

There are some workarounds, google search for “error-during-google-drive-cloud-sync” to find a thread on the old forums.

But we really need a tickbox to pass this " --drive-acknowledge-abuse " flag through and stop jobs erroring out! It still seems to sync everything else by the way - just results in nasty red marks and doesn’t sync that file (usually an executable, maybe inside a zip or 7z)

3

Oh Doh!

There is now an option to pass this argument :smiley:

Edit your jobs if you’re in the same boat as me! Tick “Allow files which return cannotDownloadAbusiveFile to be downloaded.” under “Advanced Options”