Cloud Sync Job to Hetzner Storage Box fails "last error was: not deleting files as there were IO errors"

TrueNAS General
1

I have a problem with a cloud sync job via webdav to a Hetzner storage box.

It’s one of several such jobs and the only one that fails.
The error message is: [EFAULT] Checks: 356478 / 356478, 100%, Listed 983645 Transferred: 52 / 52, 100% Elapsed time: 21m34.7s 2025/12/07 00:21:39 NOTICE: Failed to sync with 152 errors: last error was: not deleting files as there were IO errors

The log show lot’s of those errors:

2025/12/07 22:20:13 ERROR : crowdsec/config/scenarios/CVE-2024-9474.yaml: Listing error: symlink: stat /mnt/ssd_mirror/mediastack_config/.zfs/snapshot/cloud_sync-4-20251207210534/crowdsec/config/scenarios/CVE-2024-9474.yaml: no such file or directory
2025/12/07 22:20:13 ERROR : crowdsec/config/scenarios/CVE-2022-40684.yaml: Listing error: symlink: stat /mnt/ssd_mirror/mediastack_config/.zfs/snapshot/cloud_sync-4-20251207210534/crowdsec/config/scenarios/CVE-2022-40684.yaml: no such file or directory
2025/12/07 22:20:13 ERROR : crowdsec/config/scenarios/spring4shell_cve-2022-22965.yaml: Listing error: symlink: stat /mnt/ssd_mirror/mediastack_config/.zfs/snapshot/cloud_sync-4-20251207210534/crowdsec/config/scenarios/spring4shell_cve-2022-22965.yaml: no such file or directory

They are all in the .zfs subdirectory although I exlcuded it after I spotted the error for the first time in the job logs.

Any ideas how to resolve this? I found no way to customize the rclone command run by the cloud sync jobs.

Einrichtung Backup auf Hetzner Cloud mittels rsync
2

Just to give myself a bump so people from other timezones may stumble across this: any ideas?

3

Don’t know if you’re the right person to ask but.. @kris any idea?:sweat_smile: Sorry to bother you but I’m a bit desperate right now.

4

For anyone who might face the same error: it occurs with webdav as well as sftp but only because of symlinks. The .zfs path is only there because i left the use snapshot checkbox checked - of course theres a snapshot in the synced path then.

Without follow symlinks it works but all symlinks are lost (which they still are with follow symlinks on, that just errors out).