Rolled the odometer over..

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

gregsachs

Active Member
Aug 14, 2018
562
192
43
Replacing some old 2tb Constellation ES drives at home, and pulled the smart data for one on a whim:
Accumulated power on time, hours:minutes 1881:48
Manufactured in week 06 of year 2013
Specified cycle count over device lifetime: 10000
Accumulated start-stop cycles: 129
Specified load-unload count over device lifetime: 300000
Accumulated load-unload cycles: 3017
Elements in grown defect list: 0
I wonder where it actually rolls over,
102k hours=4245 days, or 11.6 years, which would be very interesting vs a Manufacturing date of 2013....
 
  • Like
Reactions: Marjan

gregsachs

Active Member
Aug 14, 2018
562
192
43
Try sg_logs -p15h,0 /dev/sdX
still rolled over, but it shows error at 77k hours:

Status parameters:
Accumulated power on minutes: 113255 [h:m 1887:35]
Status: background scan enabled, none active (waiting for BMS interval timer to expire)
Number of background scans performed: 625
Background medium scan progress: 0 %
Number of background medium scans performed: 625
Medium scan parameter # 1 [0x1]
Power on minutes when error detected: 3010279 [50171:19]
Logical block recovered by device server via rewrite
sense key: Recovered Error [sk,asc,ascq: 0x1,0x17,0x1]
Additional sense: Recovered data with retries
LBA (associated with medium error): 0x00000000d1a52c00
 

UhClem

just another Bozo on the bus
Jun 26, 2012
438
252
63
NH, USA
Something's fishy.
That "Accumulated power on minutes" value is specified in the SCSI/SAS standards as a 4-byte (32-bit) field; so no reason for any "rollover". Seagate's own "SCSI Commands Ref Manual" spells out everything for that Background Results Log Page (15h), and that field is defined as: "number of minutes the device server has been powered on since manufacturing."

By the way, this is the only place where Seagate maintains the total accumulated power-on time (until present) for SAS device; at least, as of 2010, the date of the manual I had a copy of. HGST also has that same Log Page 15h, but also has a vendor-specific page 37h which includes a Power-On Hours (hours only) as a 4-byte field.

For a HGST 4TB SAS drive (closest "vintage" I have at hand to your 2TB ES), my sg_logs results:
Code:
Background scan results page  [0x15]
  Status parameters:
    Accumulated power on minutes: 2919991 [h:m  48666:31]
    Status: background scan enabled, none active (waiting for BMS interval timer to expire)
    Number of background scans performed: 311
    Background medium scan progress: 0.00 %
    Number of background medium scans performed: 311
...
HGST/WDC miscellaneous page [0x37]
  Power on hours = 48666
  Total Bytes Read = 21717018301648
  Total Bytes Written = 18406346834384
  Max Drive Temp (Celsius) = 54
  GList Size = 0
  Number of Information Exceptions = 0
  MED EXC = 0
  HDW EXC = 0
  Total Read Commands = 110691526
  Total Write Commands = 20215286
  Flash Correction Count =
Below are some page images from the 2010 Seagate manual, relevant to this matter.
----
SGT-SCSI_SAS-pg1.jpg
-----
SGT-SCSI_SAS-pg300.jpg
-----
SGT-SCSI_SAS-pg301.jpg
-----
SGT-SCSI_SAS-pg302.jpg
-----

-----
SGT-SCSI_SAS-pg304.jpg
 

Attachments

gregsachs

Active Member
Aug 14, 2018
562
192
43
Only idea I have is this is somehow related to storage spaces, but that doesn't make a lot of sense;
I currently have 4 of the seagates hooked up. 1 is a standalone 'scratch' drive, the others just got pulled out of the storage pool but haven't been physically pulled yet.
The scratch disk shows ~73k hours, which is plausible.
The other 3 all show ~1900 hours, which is not. The scratch disk is on internal raid card but jbod, the others are on external raid card and xyratex enclosure.
Possible bug in windows implementation of sg_Scan or related to the drives hanging off of a raid card in JBOD mode? (9286-cv8e)
I tried with 3 different drives and same thing on , ~1900 hours power on but errors logged at over 70k hours.
 

UhClem

just another Bozo on the bus
Jun 26, 2012
438
252
63
NH, USA
Please post the results from a sg_logs -p15h,0 /dev/sdX for each of the other 3 drives, similar to what was posted in your 2nd post above; indicate which one is the "scratch".
 

gregsachs

Active Member
Aug 14, 2018
562
192
43
Please post the results from a sg_logs -p15h,0 /dev/sdX for each of the other 3 drives, similar to what was posted in your 2nd post above; indicate which one is the "scratch".
I literally just got done pulling them and putting in storage.
Scratch shows this:
SEAGATE ST2000NM0001 XRBA
Background scan results page [0x15]
Status parameters:
Accumulated power on minutes: 4377902 [h:m 72965:2]
Status: background medium scan is active
Number of background scans performed: 357
Background medium scan progress: 8.83331 %
Number of background medium scans performed: 357
If it is really interesting I can throw one back in, part of this was about moving to have spare bays in the enclosure.
 

UhClem

just another Bozo on the bus
Jun 26, 2012
438
252
63
NH, USA
I literally just got done pulling them and putting in storage.
Scratch shows this:
...
If it is really interesting I can throw one back in, part of this was about moving to have spare bays in the enclosure.
Not worth the trouble, really (but appreciate the "offer").

It piqued my curiosity (yours too?), but you know what they say:
"Curiosity killed the cat." (or tired him unrewardingly :))
 
  • Like
Reactions: gregsachs