Howdy @stovepipe_jones , welcome to PhotoStructure!
If possible, I’d recommend having a full backup of those 5TB of files, perhaps sitting on an offline external drive, rather than deleting it altogether. I’d hate to have you lose anything because PhotoStructure filtered out something unexpected.
Did you typo the filename perhaps? The screenshot is for DSCF2384.JPG
Ugh, sorry for that confusion. I believe I fixed that a while ago–there’s no reference to /ps/Library in the code anymore.
Know that the list tool is trying to make sense of the AssetFile.URI column. PhotoStructure doesn’t store pathnames–instead, it uses 4 different URI “schemes,” listed here: Moving from PC to Raspberry Pi - #6 by mrm
If list can’t find the prior volume with the same UUID, the rendered path may not be correct. More information is here: PhotoStructure | What's a “drive,” or “volume?”
Are you running list from a docker container with the same bind mount configuration? Is there a .uuid file in /var/photo-dump? photostructure info --volumes (available in v2.x builds), as well as the /about page will show you what volumes PhotoStructure is currently aware of.