I aborted the task but that left some kind of lock hanging around. Whenever I try to run the task again, I get a “locked” error message but I can’t figure out where I find the “unlock” command it references.
errorFAILED
[EFAULT] repo already locked, waiting up to 0s for the lock
unable to create lock in backend: repository is already locked by PID 11571 on truenas-ee by root (UID 0, GID 0)
lock was created at 2024-09-07 02:59:01 (8h33m53.969079484s ago) storage ID e21b4a69
the unlock command can be used to remove stale locks
It did persist after a reboot but I eventually figured out that the lock was on the Storj side. I’ll file a bug as 1) an abort on TrueNAS side shouldn’t leave the Storj repository locked, and 2) if possible, any error message should distinguish if it is being generated by TrueNAS or Storj.
I found a posting that was somewhat related as it was about Storj, restic, and stale locks which led me to “restic unlock” so I’m guessing that is where the mysterious unlock command lives and that restic is being used instead of rclone (which I think is used by the regular Cloud Backup in Scale).
I ended up resintalling EE from scratch as part of the debugging process where I discovered that the resulting install didn’t work as it didn’t create the admin user. I ended up having to install 24.04 and upgrading which worked fine.
.