Same symptom as the original -- critical filesystem sectors that are not usually rewritten are returning uncorrectable ECC errors, and other evidence of bit rot.

I'm going to try to get this one replaced in hopes it can be done, but every other time I have, tried Seagate insisted that I use their tools to replace the bad sectors and then it verified good.

One drive developed two bad sectors, a reformat mapped them out

Sit it aside for a while and even zeroed sectors rot; try their tool and it rewrites all the bad sectors, then declares the drive fine again.

Wipe it, verify all sectors good, write data to it.

Began to fail (bad sectors) approximately one year after purchase

Doesn't show up on any other PC in the house and my laptop won't detect it when trying to install Windows on it (stock WD drive in my 5 yr old laptop developed bad sectors and the last couple weeks the laptop barely worked)

But now there are a bunch of bad sectors and corrupted data

Less than six months in, one of the drives threw up several bad sectors.

My neighbor's laptop stopped working because the hard drive got bad sectors and that stopped windows from booting I was still able to get some data off of it like pictures and stuff like that

After 2 months I started getting bad blocks, which required thorough surface scans to identify and lock out the failed sectors

I have a 14 of these setup in a raid 6 array, out of the blue 3 months after installing two drive failed the same day (bad sectors

Had many corrupted sectors

The HDD had a 1-pass format, to make sure there is no bad sector upon putting into my server

They historically will not accept return of a drive that will not 'stay' bad after having all its bad sectors rewritten

copying files from my other hard drive using this as a backup got as slow as 90 kb/s.

What's got me riled is that I looked at the specs for this drive and realized the whole SSHD moniker is pure bullsh!t

Both R/W errors began to rise along with Reallocated sectors