On 10/15/23 11:55, A. F. Cano wrote:
https://github.com/borgbackup/borg/issues/4631Lots of possible solutions that people tried that ended up not working in this report.
[...]
Any other ideas, anyone?
You attempts seemed to have worked. You ran into another problem that was fixed recently and will be available in next release. To workaround the problem right away, run the following command:
# borg info /media/{id}/FreedomBoxBackups
Warning: Attempting to access a previously unknown unencrypted repository!
Do you want to continue? [yN]
Answer 'y' above. The command will succeed. Repeating the command does
not show the warning anymore. FreedomBox will now show the contents of
the repository properly and scheduled backups will work.
By the way, I was able to reproduce the problem when I replaced the backup repository with an older copy. With this, I was able to find a workaround to the problem that works reliably. I am writing the solution here for future reference.
I ran the following commands
# rm -rf /root/.cache/borg
# rm -rf /root/.config/borg/security/{repo_id}/manifest-timestamp
{repo-id} for the troublesome repository needs to be found through a
process of elimination. Look at the IDs in /root/.config/borg/security/.
Run 'borg info {repo_path}' to known the ID of a working repository such
as /var/lib/freedombox/borgbackup/. Eliminate the working IDs from the
list and remaining one is the ID of the non-working repository.
This is sufficient if the repository is encrypted. However, if the repository is unencrypted the workaround involving 'borg info' command above (or the next version of FreedomBox are needed).
-- Sunil
OpenPGP_0x36C361440C9BC971.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ Freedombox-discuss mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
