I’ve found it okay to get a general feel for stuff but I’ve been given insidiously bad code. Functions and data structures that look similar enough to real stuff but are deeply wrong or non+existent.

I was hoping that testdisk would show you something funky going on with the partition table based on the parted error. No luck I guess.

My next two ideas are,

1. As far as I know wipefs just tries to wipe what blkid sees and it might have screwed up something. What if we just dd the whole drive with zeros and let your enclosure take it from there?
2. What does smartctl say? Might be worth it to run the long and short tests to make sure that the drives themselves are okay.

Total shot in the dark but what does testdisk say?