Unreferenced pack

After a recent prune on a wasabi backup I received an error:

7 snapshots have been removed, running prune
counting files in repo
building new index for repo
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 626.580639ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 488.882551ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 586.725506ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 1.709585167s: We encountered an internal error.  Please retry the operation again later.
pack file cannot be listed cf1073c0104dcdb4e4eca0ec4a75c86332c60c7d0ce0a7e8316280a09a5e8b33: We encountered an internal error.  Please retry the operation again later.
[1:41:25] 100.00%  472106 / 472106 packs

repository contains 472105 packs (1799721 blobs) with 2.251 TiB
processed 1799721 blobs: 0 duplicate blobs, 0 B duplicate
load all snapshots
find data that is still in use for 93 snapshots
[0:27] 100.00%  93 / 93 snapshots

found 1792437 of 1799721 data blobs still in use, removing 7284 blobs
will remove 0 invalid files
will delete 1467 packs and rewrite 814 packs, this frees 9.221 GiB
[17:47] 100.00%  814 / 814 packs rewritten

counting files in repo
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 593.90195ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 517.029352ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 663.25251ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 1.764323123s: We encountered an internal error.  Please retry the operation again later.
pack file cannot be listed cf1073c0104dcdb4e4eca0ec4a75c86332c60c7d0ce0a7e8316280a09a5e8b33: We encountered an internal error.  Please retry the operation again later.
[1:45:57] 100.00%  470222 / 470222 packs

Trying to find pack cf1073c010 throws the same error. Rebuilding the index throws the same error:

repository 8df0f8a6 opened successfully, password is correct
counting files in repo
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 566.001717ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 999.931362ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 979.050978ms: We encountered an internal error.  Please retry the operation again later.
Load(<data/cf1073c010>, 591, 4514385) returned error, retrying after 1.925209386s: We encountered an internal error.  Please retry the operation again later.
pack file cannot be listed cf1073c0104dcdb4e4eca0ec4a75c86332c60c7d0ce0a7e8316280a09a5e8b33: We encountered an internal error.  Please retry the operation again later.
[1:43:17] 100.00%  469689 / 469689 packs
finding old index files
saved new indexes as [5a3490ee d69d3a5f 31916519 31cd5ce2 8702e645 f04a7ac9 f5c8354c b75363d3 ef6b986d 4f2d99a6 1f951317 89cf5de4 dbc80ed4 1bf18f58 bff4136b 7f264225 80d4c6f9 19bb7cec 206b5f6c 7fd6ac79 4937bf0f b3ef8582 ba70bcd0 93ce92f5 ade8c37b 196899bc 14f89da6 60a29cb8 893ffd3d df80af03 c0c60d56 f3dbb617 1cf19880 602364f3 85843257 698b7dbc bebc4174 c42e5f34 4735d0fd 08afceea 55ee98de d6ac5d9d db349efb 45f651f5 909bbd61 cab90789 8dc539ee 63e29c94 3814db94 21008bc6 b019e9b6 e932038a e07b0cf1 66890be3 2b0ae445 1080b3ea 175a6a9a 9a900222 e883dbef 7c52d233 03fdad65 bf22ad90 93f3cdd1 891a010f 6b23e67b fef56dc4 54355f8e ef73969d 29052c60 a99454ca 6997d617 9f1ce438 01cb5a33 308435b0 c7fc8ded 06d7e908 d43f3f85 ea6168de 58616240 79ab5233 d23072d3 bb88bdab 8b29a406 ae3292a7 4276a234 0ec41a2f 92b5b4cc 141c55db dce95e2a 02fb83d4 be5ddbd9 91d25c53 c9bb62aa 57e41c7b ce7c1acd 708ec83d c56e243d 4a187faa 4b406210 2fbebb7c 1211113a 36a0dea3 b759a2e7 c64bb087 e4f86d5f a5b84080 4abb29f0 8d6a7ce1 8cf0629b 71b93798 bb60952c 9862aad7 1d9a8bc7 d17735e4 dcbdf25f 64ef2567 067e2698 56f6f2c9 8042fd08 29d6b81c 3fffdf5e 115869c3 cc523ce9 a90fcf07 e2634696 8d307551 c77ff493 2a9f5d37 3937f896 7ba0f591 07066d49 76e1d360 e634c421 e6674940 dcb1dd4b 4e856f57 013f5d14 0ddd9d78 6ffc3dfa b3d9072d 5e1ab480 06ace3a1 b1088917 c64f09d6 2a8edb08 5ee6c53c 57e1c86a 69fde8a9 a60ec626 f64d6e0b b40803eb cd93d32d 380f0b28 5d91a28e d4bf164f a2a595df 9431749c]
remove 158 old index files

This is using Tumbleweed version: restic 0.9.5 compiled with go1.11.11 on linux/amd64

Is there a way of fixing this? If not, is it harmful to continue?

The error message appears to be coming from Wasabi. You may need to reach out to their support to correct the problem.

I contacted wasabi and heard back from them. In the meantime I used the wasabi console and deleted the
data/cf/cf1073c0104dcdb4e4eca0ec4a75c86332c60c7d0ce0a7e8316280a09a5e8b33
file. Following that, prune and check both ran with no reported errors.

Wasabi support indicated there were many 500 errors when restic tried to GET/load the data. There was obviously something wrong with that file.