Both SMART values haven't deviated from being reset after a 5-hr.
chkdsk /r /f. Some sort of numeric relative values, possibly endemic
to Samsung's SMART implementation, at a base 100 designee for the seek
errors, and 252 for reallocation counts;- fields repeated twice for
comparative values presumably of severity. (Other fields would not
permit a reset, without guarded manufacturer codes -- e.g. UDMA or CRC
errors.)

That was a couple weeks ago. Subsequent data to the HDD
I'll continue to favor, subtractively, with a 1T SSD working now in
conjunction over a database specifically the SSD absorbs as further
data modification resume: Sets of data modification can be moved off
the HDD drive and its prior SMART errors, to the SDD, with reasonable
time and adequate storage the SSD provides.

Of course the HDD has not, per se, been written to since the check
disk routine, only copied from and to the SDD. A recommended course,
for some at least, upon encountering the above errors, check disk at a
sector level bubble-gum back together, (not necessarily in accounting
the added writing precautionary measure I thought to add), while still
able to and should deteriorating sector counts not again resume;-
Along with a working back-up for another clear meaning deterioration
is given to eminent failure with no forewarning.

Also haven't noticed any glitches since in media playback. Not sure
how old that particular 2T HDD unit, not having tracked down a serial
nomenclature for a date of manufacture. I'd guess it's been largely
dormant in a shelved back-up capacity for perhaps eight years. I
installed it for 24/7 service maybe six months ago with really no
concern or special note for probable SMART errors then present;- not
until, that is, the glitches more of late began to occur, potentially
capable of gumming-up drive retrieval if not an "organic aspect" of
the whole SATA-controller and system driver device chain.