Unmashal: parsing time ... error

What does this mean and how to fix is? (I tried also with restic stable 0.11.0)

root@host ~ # ./restic_v0.11.0-221-g9c41e4a3_linux_amd64 check
using temporary cache in /tmp/restic-check-cache-177756569
repository 38d9a80c opened successfully, password is correct
created new cache in /tmp/restic-check-cache-177756569
create exclusive lock for repository
load indexes
check all packs
check snapshots, trees and blobs
error for tree 35eb29dd:
Unmarshal: parsing time "“2020-07-09T16:04:47.728975#42+02:00"” as "“2006-01-02T15:04:05Z07:00"”: cannot parse “#42+02:00"” as “Z07:00”
Fatal: repository contains errors

restic prune did’nt fix it

[0:17] 55.56% 5 / 9 snapshots
parsing time "“2020-07-09T16:04:47.728975#42+02:00"” as "“2006-01-02T15:04:05Z07:00"”: cannot parse “#42+02:00"” as “Z07:00”
Unmarshal
github.com/restic/restic/internal/restic.(*Node).UnmarshalJSON
/home/beta/restic.git/internal/restic/node.go:360
encoding/json.(*decodeState).object
/usr/local/go/src/encoding/json/decode.go:609
encoding/json.(*decodeState).value
/usr/local/go/src/encoding/json/decode.go:370
encoding/json.(*decodeState).array
/usr/local/go/src/encoding/json/decode.go:558
encoding/json.(*decodeState).value
/usr/local/go/src/encoding/json/decode.go:360
encoding/json.(*decodeState).object
/usr/local/go/src/encoding/json/decode.go:765
encoding/json.(*decodeState).value
/usr/local/go/src/encoding/json/decode.go:370
encoding/json.(*decodeState).unmarshal
/usr/local/go/src/encoding/json/decode.go:180
encoding/json.Unmarshal
/usr/local/go/src/encoding/json/decode.go:107
github.com/restic/restic/internal/repository.(*Repository).LoadTree
/home/beta/restic.git/internal/repository/repository.go:799
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:19
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
github.com/restic/restic/internal/restic.FindUsedBlobs
/home/beta/restic.git/internal/restic/find.go:31
main.getUsedBlobs
/home/beta/restic.git/cmd/restic/cmd_prune.go:552
main.runPruneWithRepo
/home/beta/restic.git/cmd/restic/cmd_prune.go:168
main.runPrune
/home/beta/restic.git/cmd/restic/cmd_prune.go:151
main.glob…func19
/home/beta/restic.git/cmd/restic/cmd_prune.go:35
github.com/spf13/cobra.(*Command).execute
/home/beta/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:826
github.com/spf13/cobra.(*Command).ExecuteC
/home/beta/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:914
github.com/spf13/cobra.(*Command).Execute
/home/beta/go/pkg/mod/github.com/spf13/cobra@v0.0.5/command.go:864
main.main
/home/beta/restic.git/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

I don’t recall seeing that type of data corruption in a Github issue, could you please open one?

The error is very likely caused by hardware problems: It seems like a bitflip occurred in the memory or CPU. (’#’ has the ascii code 0x23 and the probably correct number ‘3’ has 0x33.). Please run a memtest.
I suspect there might be some further hidden damage in the repository, so please run tell check to fully read every data file: restic check --read-data.

Would it be possible for you to help with investigating the damage to repository or do you want to repair the repository ASAP? If the repository is small enough a backup copy of it would be perfect to give us the possibility to further analyze the damage.

That said, to repair the repository you could try the steps from here: Data blobs seem to be missing, aborting prune to prevent further data loss! · Issue #3023 · restic/restic · GitHub . The initial command to find the problematic pack file would be restic find --show-pack-id --tree 35eb29dd. With the results from that you should be able to follow “Route 1”.