I am using restic. 0.11 and just noticed this error. The repo still mounting and backup still working.
[Edit]
As I use a script to backup, check and prune. This can probably be happening for a while or at least from my update to 0.11 in 15/nov.
repository 6d9f087d opened successfully, password is correct
counting files in repo
building new index for repo
[2:46] 100.00% 11822 / 11822 packs
repository contains 11822 packs (404282 blobs) with 57.861 GiB
processed 404282 blobs: 0 duplicate blobs, 0 B duplicate
load all snapshots
find data that is still in use for 49 snapshots
[0:21] 63.27% 31 / 49 snapshots
id 0000000000000000000000000000000000000000000000000000000000000000 not found in repository
github.com/restic/restic/internal/repository.(*Repository).LoadBlob
/restic/internal/repository/repository.go:156
github.com/restic/restic/internal/repository.(*Repository).LoadTree
/restic/internal/repository/repository.go:723
github.com/restic/restic/internal/restic.FindUsedBlobs
/restic/internal/restic/find.go:19
main.getUsedBlobs
/restic/cmd/restic/cmd_prune.go:276
main.pruneRepository
/restic/cmd/restic/cmd_prune.go:158
main.runPrune
/restic/cmd/restic/cmd_prune.go:62
main.glob..func19
/restic/cmd/restic/cmd_prune.go:27
github.com/spf13/cobra.(*Command).execute
/home/build/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
/home/build/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
/home/build/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
/restic/cmd/restic/main.go:98
runtime.main
/usr/local/go/src/runtime/proc.go:204
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1374
Ok, that’s odd. Somehow one of the sub dirs in a snapshot references an invalid tree ID (all zeroes). You could try finding out which snapshot it is by running:
❯ restic find --blob 0000000000000000000000000000000000000000000000000000000000000000
repository 6d9f087d opened successfully, password is correct
Unable to load tree 0000000000000000000000000000000000000000000000000000000000000000
... which belongs to snapshot 9f16b85875496e2f9618871af9775e5f41133043b3549f6d8bc4a0580df61542
I can’t recall, I think May 2019 with restic 0.9.3 (really guessing here).
Running this command that MichaelEischer suggested on GitHub, helped to find the snapshot causing the error. I mounted my repository and checked the snapshot with that date and time reference and it was empty. Removing it solved the error message:
restic list snapshots -q | while read idxid; do \
restic cat -q snapshot $idxid | jq 'select(.tree | contains ("0000000000000000000000000000000000000000000000000000000000000000"))'; \
done
As @cristian-spiescu mentioned that CTRL + C could’ve caused the problem, I can assume that it could be it or part of what caused it. Since I use two displays and keep various Windows/softwares opened, some times I issue a command in the wrong one and also some times it takes a while for me to notice . It could’ve happened maybe more than once because I also put some terminal windows on a separated Desktop when it’s going to take a while to finish.
. It could’ve happened maybe more than once because I also put some terminal windows on a separated Desktop when it’s going to take a while to finish.