Another : ciphertext verification failed at "check"

I got into trouble with one of 5 backups to the same storage/machine.

  • I run a daily backup from client using SSH to server (crypted ext4) / restic runs locally at client
  • I run daily at server ‘restic forget --prune --keep…’ at the moment also without problems
  • I also run daily at server ‘restic check’ to this repo … since two days I get

SuS-GW:/root$ restic check
using temporary cache in /tmp/restic-check-cache-3678210625
repository e3d19ef0 opened (version 2, compression level auto)
created new cache in /tmp/restic-check-cache-3678210625
create exclusive lock for repository
load indexes
[0:10] 100.00% 29 / 29 index files loaded
check all packs
check snapshots, trees and blobs
error for tree 0a4670fa:
decrypting blob 0a4670fadbc1a90c8a2f9d3cb22370adba3bb7dac9084e438f13de680c3c3bcd failed: ciphertext verification failed
[1:21] 100.00% 26 / 26 snapshots
Fatal: repository contains errors

The next I should try is ‘restic check --read-data’ but this results in a loop like output for about two days now

Load(<data/e772b66cfd>, 17028913, 0) returned error, retrying after 17.795871739s: open /backup_veeam/crypted/restic/sus-srv-ns2/data/e7/e772b66cfd28147e8b14d101ad50e4af3db21431976c944c38a79d57de6629c7: required key not available
pack c7ee92a3b738710fe329e93da27ccf501864cf908e500d8ed3ef3be68cf71ca2 failed to download: StreamPack: open /backup_veeam/crypted/restic/sus-srv-ns2/data/c7/c7ee92a3b738710fe329e93da27ccf501864cf908e500d8ed3ef3be68cf71ca2: required key not available
Load(<data/b78b24efee>, 17370213, 0) returned error, retrying after 467.969968ms: open /backup_veeam/crypted/restic/sus-srv-ns2/data/b7/b78b24efee5eab3a7bea1172b318ae5f6ae5bbf6def6ce1aa4dc0376297ce5a2: required key not available
Load(<data/b78b24efee>, 17370213, 0) returned error, retrying after 490.100954ms: open /backup_veeam/crypted/restic/sus-srv-ns2/data/b7/b78b24efee5eab3a7bea1172b318ae5f6ae5bbf6def6ce1aa4dc0376297ce5a2: required key not available

I’m not sure, what to do next. I’ve got a second backup of this client to another target and would like to keep integer data but remove broken blobs/packs/snapshots to get backups going on.

regards, Ronny

A few steps later - running as root - I was able to fix it without any loss of data inside any snapshot.

1 Like