I ran fsck on the drive and it returns the following.
[gumper@nucdora ~]$ sudo fsck /dev/sdb1
fsck from util-linux 2.38.1
Unsupported: replay_log()
Unsupported: check_volume()
Checking 132412 MFT records.
Unsupported cases found.
ntfsck was unable to run properly.
I’m not sure what this tells me.
I also then tried running the check command in restic and it’s giving me all sorts of errors. It’s complaining about stale NFS file handle and also about a whole bunch of packs missing.
Some new information. I was able to eliminate the stale NFS file handle by connecting the drive to a Windows PC and running the tools to fix the errors that it found.
Now, when I run restic check, I’m only getting about a dozen of the following errors:
That’s much better than what I was seeing before when it was page after page of errors. 
Is this fixable or should I wipe the drive and start over with another file system, like ext4?
When I check the drive SMART status, it’s not showing any bad sectors and no other red flags, so I’m assuming the drive is physically ok.
I’ll let others more knowledgeable than I speak to whether the restic repository is fixable or not. Regarding the drive though…
If the drive is only going to be used with linux, then ext4 or another native linux filesystem would be a better fit than NTFS. If it is going to be also used with windows, I think NTFS should be fine if used with a recent kernel (you’re running Fedora, so no concerns there). Although it seems you’re running into issues in spite of this, which suggests something in the storage stack is having difficulties; either generally or with the specific restic workload.
You can follow the steps at Troubleshooting — restic 0.16.3 documentation to repair the repository.
However, NTFS on Linux seems to have a certain tendency to cause problems. In particular, a sudden disconnect of the external drive can damage the repository. I’m not aware of such reports in regards to ext4. Restic also instructs the OS to properly write all data to disk before completing the backup, however, this seems to be unsuccessful for NTFS from time to time.
Yeah, I tried that last night and things went south from there. 
I’ll start over with ext4.
Thanks to all for the help!
