I will not give to anyone who panhandles in dangerous locations. I will not give to people who stop me.
the only time I will give cash is if they have kids with them and I have seen them interact positively with the kids.
there's one woman in my area that has her three kids with her. she's everywhere in town. she does not have positive interactions with the kids. one day I saw her and the kids sneaking back to a parked escalade in a park across from where they were at. very nice, new, and clean. clearly she is using her kids for sympathy. this is why I have that rule.
this thread has multiple documented instances of poor QA and firmware bugs Seagate has implemented at the cost of their own customers.
my specific issue was even longer ago, 20+ years. there was a bug in the firmware where there was a buffer overflow from an int limit on runtime. it caused a cascade failure in the firmware and caused the drive to lock up after it ran for the maximum into limit. this is my understanding of it anyway.
the only solution was to purchase a board online for the exact model of your HDD and swap it and perform a firmware flash before time ran out. I think you could also use a clip and force program the firmware.
at the time a new board cost as much as a new drive, finances of which I didn't have at the time.
eventually I moved past the 1tb of data I lost, but I will never willingly purchase another Seagate.
my guess is because the CPU power levels are fucking trashed because of all the patches they have to run at runtime. before Intel went all "wild west" with their security practices to improve performance, sleep worked just fine for me.
keep in mind, this was before uefi too, so it might also have a hand in the problems.
you don't fuck with moms spaghetti.