Power-on hours (SMART attrib) can be spoofed [ST3200822A]
But I don't know how it's being done.

[ST3200822A is a Seagate 200GB 7200.7 IDE]

I've had this drive in service for 6 years 24/7 under heavy usage; never a problem. I thought: "Why not run a SMART report on it" so I installed it in a PC and did. Given its "stressful" life, I was not displeased that it had only 6 Reallocated_sectors, 0 Current_pending, and nothing else amiss. EXCEPT I noticed the Power_on_hours (raw value) was 1236. It should have been 50+K!

Further testing showed that, outside of its normal setting, the POH functioned properly (1:1 w/wall clock), but when "on the job" nada.

Is this a well-known fluke (and I'm the last to get the joke)?

[Note: I'm not trying to be coy by not describing its 24/7 environment--I'll follow-up with that, a little later. But I wanted to get learned response(s) prior to (possibly) prejudicing anyone.]

I've attached a [more] recent SMART report. Note +6 hours ([1242-1236] while it was in the PC) but there were 8 additional hours "on the job".

Puzzled,
UhClem

As always, I think it's worth remembering what status raw SMART attributes have, as far as using / interpreting them directly, although in this case I suspect there is an uncommon cause.


Personally I don't like questions where information is deliberately witheld (irrespective of the reason - I'm old enough not to need protecting from prejudice with that technique ). Of course others here might not mind being "kept in the dark" - YMMV.

I'll just make a brief comment that with the limited info given and based on my experiences, this sounds similar to something for which I eventually found the reason (several years ago). If that applies here, it would not be unique to your specific drive.

Of course my hypothesis could be wrong - we'll see what suggestions other members give