Thank you. Honestly that had not really crossed my mind. I’m on the spectrum so I take people literally sometimes. That seems like a very real possibility.

Thank you! I’ll try this out. I’ve been mostly using it while playing around with new things rather than to expand scaffolding on existing stuff.

However what I find frustrating is that it so confidently gives you garbage sometimes. I was trying to configure some stuff in docker that needed a very extensive yaml config. It confidently gave me flags and keys to accomplish what I wanted that looked logical and fit in with rest of the style but simply did not exist.

Thank you! That’s been my experience as well. It just gives you insidious junk that you have to be vigilant to catch. That is so much more stressful for me than having to deal with repetitive stuff.

I can’t fathom how people are claiming it generated whole projects for them.

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?

Why not go even further? Just switch off the pesky temperature limits in the bios.