← All stories

The Great USB Drive Chaos of 2025 πŸ§Ÿβ€β™‚οΈπŸ’Ύ

A true cautionary tale β€” and the reason the node shopping list says buy your storage new, from a real brand.


The Setup: A Mother's Love and Amazon's Mysteries

So there I was, minding my own business with my Proxmox server humming along nicely, when I decided to check on my trusty USB backup drives. You know β€” the ones that are supposed to save my data, not speedrun deleting it.

Enter stage left: "usb5" β€” a seemingly innocent 512 GB USB drive that my wonderful mother picked up at one of those Amazon returns / warehouse stores. You know the ones: where Amazon quietly resells the stuff other people sent back for "mysterious reasons." She got it for what seemed like a steal.

As they say: "If it seems too good to be true… it's probably faking its own capacity."

The Crime Scene: When Backups Go Rogue

First sign of trouble β€” my backups started looking like they were written in ancient hieroglyphics:

???????????? ????  /????????

I thought, "Huh, maybe I set my terminal to Klingon." Nope. Much worse. Those ??? are what a directory looks like when the filesystem reads back bytes that were never actually stored.

The Domino Effect: How One Bad Drive Brought Down the Empire

This little gift from Mom didn't just corrupt its own files β€” that would be too simple. This overachiever:

  1. Faked its size β€” reported 512 GB while really holding a fraction of that.
  2. Silently ate my data β€” writes past the real capacity "succeeded" and went nowhere (or wrapped over earlier files).
  3. Handed back garbage β€” so the "backups" I thought I had were already corrupt.
  4. Spread the damage β€” when I copied those poisoned backups onto Silver-usb and usb-yellow, I copied the rot with them…
  5. …and finished the job β€” the flaky controller kept causing USB bus resets that interrupted writes mid-flight, trashing the filesystems on the good drives too.

Lovely parting gift:

EXT4-fs warning: htree_dirblock_to_tree: error -5 reading directory block

(Translation: error -5 is EIO β€” an I/O error. The filesystem is having an existential crisis and would like to speak to a manager.)

The Investigation: CSI β€” Computer Support Incidents

The Smoking Gun: Classic Signs of a Counterfeit Criminal

βœ… Suspiciously cheap for 512 GB β€” "What a bargain!" (famous last words)
βœ… No brand name β€” because brands are for suckers who want, y'know, working products
βœ… From a returns/warehouse reseller β€” previously returned by someone who learned this lesson first
βœ… Character corruption β€” the digital equivalent of speaking in tongues
βœ… Took its housemates down with it β€” bad RAID-of-one energy

πŸ›‘οΈ How To Never Get Burned (the part that actually helps)

Vet every new drive in ~5 minutes, before you trust it with anything:

Buy so you never have to:

The Aftermath: Server Down, Ego Bruised, Lesson Learned

The Plot Twist: The Hero Was The Villain

The drive that was supposed to be my backup solution nearly became my backup problem. It's like hiring a bodyguard who turns out to be running the heist.

The Moral of the Story

Mom's heart was in the right place. That USB drive's data was not.

When it comes to storage, you really do get what you pay for β€” and sometimes what you pay for is a very expensive lesson in filesystem corruption. Test new drives, buy real ones, and never let a stranger's flash near your backups.


P.S. β€” Mom, I love you, and this was honestly hilarious in hindsight. But maybe next time let's get USB drives from places that don't also sell returned underwear and mystery liquids. πŸ˜‚

P.P.S. β€” The drive has been exiled to the digital afterlife (the trash). It finally found a job it's good at: being a paperweight.

← More stories Β· The node shopping list