Nope. I shucked the drive from its original enclosure and put it into my known-good one. Drive is dead. RIP (You were a bastard)

Update: the USB to SATA controller in the enclosure (?)… died? I will hook it up to another system and see what’s up but I may have to schuck this drive and put it into another enclosure. Seagate quality. 👌

I blacklisted the uas module from the equation just to rule that out entirely. Now we wait.

This is likely a problem with Seagates choice of USB-to-SATA controller and the uas kernel driver and I would need to fall back to the usb-storage driver.

TLDR something to do with writes hitting a timeout and error handling.

- know what they are losing when they don't have those things. "Fuck you, got mine" is the attitude that is taught, but any means necessary.

- to their own preconceived notions of what nuclear family safety and security is.

Not proving anything, but personal anecdotal experience: Those with many safety nets and familial support systems are often the ones who don't want others to have them. They often feel entitled because they -

The right heavily relies on tribalism. If you're "not in the tribe," you lose any and all support system. Not having anyone to rely on tends to radicalize people. When they then realize that if it came down to basic survival, they severely lack the resources to do so without making huge sacrifices -

What’s the point of a global env file if each script is just going to hardcode it anyway? On the flip side, a picture of me trying to find a source a dependent env variable that’s not declared in said script. Hint: it’s not the global env file.

The experiment didn't fail. It was just falsely advertised.

Yes you can.