This may or may not help in your situation.
1) Some Seagate drives don't report SMART data correctly. Personally I've only seen it on their short-lived SSD line, but I suppose it could happen on a spinner also.
2) Some drive monitoring programs simply pull the SMART data wrong, or report it wrong. Some SSDs have SMART values that do not exist on spinning drives, such as for TB read and written from host, and some have it also for TB read and written to NAND. I've seen GPartEd / PartedMagic tell me that a perfectly good SSD was failing because the apps skipped an entry for TB read and written, causing the app to display 3 trillion CRC errors rather than 3 trillion bytes read. Said differently, those lines reported in the SMART reporting utilities differ considerably from app to app and drive to drive.
3) HD Tune is useless. Sorry but true. CrystalDiskInfo is much more accurate, most of the time. Be sure to go to Function -> Advanced Feature -> Raw Values and report them in 10(Dec). Now its starts to make sense.
4) My experience only, but SeaTools is absolutely useless. The ONLY thing it's useful for is getting Seagate to take a failing drive back.
5) You probably know, but be aware that only a few SMART values mean anything to the consumer. And see this attached pic for what I mean about entries specific to SSDs (at the bottom).