rhatguy

Updated the plugin this morning. Deleted and recreated my scheduled job. Ran the schedule manually. It worked successfully. I'll double check again tonight during the normal schedule. Thanks for the fix and this awesome plugin!

Thats right. This is the job log from when I click "backup now" on the remote backup in the gui (not the cron job) Remote backup session finished - 2026-03-24 22:13:15 Backup duration: 1m 23s Uploaded remote backup to -> backblaze-unraid-flashbackup:unraid-flashbackup/Flash_Backups Backup size is 1GB Full remote backup mode backing up entire /boot Plugin version: 2026.03.22.01 Remote backup session started - 2026-03-24 22:11:52 ---------------------------------------------------------------------------------------- This is the log from clicking "run" on the scheduled cron job (with the same configuration as my remote manual backup). Remote backup session finished - 2026-03-24 22:14:18 Backup duration: 0s [ERROR] No bucket name configured for remote: backblaze-unraid-flashbackup Plugin version: 2026.03.22.01 Remote backup session started - 2026-03-24 22:14:18 ----------------------------------------------------------------------------------------

I have the below configs. When I execute the job by clicking "backup now" the job runs fine and my backup is uploaded to B2. However, when the job executes via cron (or when I manually click "run" on the scheduled job) it fails saying [ERROR] No bucket name configured for remote: backblaze-unraid-flashbackup. I tried blowing away the config and re-creating it. I didn't think buckets were configured in rclone. Am I missing something obvious? Thanks! root@Tower:/boot/config/plugins/flash-backup# cat schedules-remote.cfg [schedule_remote_1774402262] CRON="45 1 * * *" ENABLED="yes" SETTINGS="{\"RCLONE_CONFIG_REMOTE\":\"backblaze-unraid-flashbackup\",\"REMOTE_PATH_IN_CONFIG\":\"/Flash_Backups/\",\"BACKUPS_TO_KEEP_REMOTE\":\"0\",\"DRY_RUN_REMOTE\":\"no\",\"NOTIFICATIONS_REMOTE\":\"no\",\"NOTIFICATION_SERVICE_REMOTE\":\"\",\"MINIMAL_BACKUP_REMOTE\":\"no\"}" TYPE="remote-backup" root@Tower:/boot/config/plugins/flash-backup# cat settings_remote.cfg B2_BUCKET_NAME="" BACKUPS_TO_KEEP_REMOTE="0" BUCKET_NAMES="REDACTED" DRY_RUN_REMOTE="no" MINIMAL_BACKUP_REMOTE="no" NOTIFICATION_SERVICE_REMOTE="" NOTIFICATIONS_REMOTE="no" PUSHOVER_USER_KEY_REMOTE="" RCLONE_CONFIG_REMOTE="backblaze-unraid-flashbackup" REMOTE_PATH_IN_CONFIG="/Flash_Backups/" WEBHOOK_DISCORD_REMOTE="" WEBHOOK_GOTIFY_REMOTE="" WEBHOOK_NTFY_REMOTE="" WEBHOOK_PUSHOVER_REMOTE="" WEBHOOK_SLACK_REMOTE="" root@Tower:/# cat /boot/config/rclone/rclone.conf [backblaze-unraid-flashbackup] type = b2 account = REDACTED key = REDACTED hard_delete = true

I'm sorry, I thought I was on the newest unraid....I'm not running the beta...I"m running 7.2.4. I manually copied the config from /root/.config/rclone/rclone.conf to /boot/config/rclone/rclone.conf and the gui immediately picks it up. I realize I'll probably need to undo this once I update to unraid 7.3. I did have to refresh the gui page to get the bucket field to show up, but after realizing that and entering the bucket everything worked. I see my flashbackup in back blaze. The usability of this is amazing! Maybe log/display where the plugin is looking for the rclone.conf file at? I could have self solved this if I knew where the plugin was looking for the file at. Regardless, thanks for a great tool!

That file doesn't exist on my system. My rclone.conf file is at /root/.config/rclone/rclone.conf

I just installed this. I don't have any rclone plugins or containers or nerd tools running today. Just have /usr/bin/rclone that came with unraid 7.3. I configured rclone with a back blaze B2 target and verified I was able to touch, list, and delete a file on back blaze from the rclone CLI. In the gui however, when I change the config to "remote" backups, it says there aren't any rclone configs found. How can I troubleshoot this further?

Should FCP remove the warning that a docker container needs an update after it has been updated (for compose based containers)? I have a few compose based containers and it seems that once the alert it triggered it never clears. Even after I update the container and verify via cli that there is not a newer container image to pull FCP does "clear". I'm happy with the warnings, I just want them to clear like they do for non-compose based containers.

Just wanted to add that I ran into this same error. I have QTY 2 9207-8i cards with the p20 firmware and my fstrim was failing. I downgraded them both using the files provided in this thread. I also found the instructions at the link below to be extremely helpful in describing what to do once I got into the efi shell as this was the first time I had used an efi shell. https://www.truenas.com/community/threads/how-to-flash-lsi-9211-8i-using-efi-shell.50902/

Can anyone help with the easiest way to add exiftool into this docker image? Is there a way to add exiftool such that I can continue to use the existing maintained template/dockerfile without having to maintain something separate from that?