Opened 7 years ago
Closed 7 years ago
#849 closed defect (invalid)
TS64GSSD370S - problems with self-tests
Reported by: | viktor | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | smartctl | Version: | 6.5 |
Keywords: | Cc: |
Description
Seems like smartctl doesn't handle self-tests properly for this device. First, I ran some tests when I bought these drive. When I tried to stop them smartctl still have been showing me that test routine is in progress. Then I set up auto-tests via smartd.conf. In "smartctl -a /dev/sda" output I was able to see the results of the last 20 test. Lifetime hours were increasing up to ~250 hours and then this counter reset - the numbering of lifetime started again from ~18 hours. Seems like overflow for unsigned integer. After executing "smartctl -x /dev/sda" all the results of self-test cleared - there are no entries in "smartctl -a /dev/sda" output! I've attached "smartctl -x /dev/sda" output
Attachments (4)
Change History (13)
by , 7 years ago
Attachment: | smartctl.txt added |
---|
comment:1 by , 7 years ago
by , 7 years ago
comment:2 by , 7 years ago
Now you can see difference in Power_On_Hours and Lifetime Hours in out.txt
comment:3 by , 7 years ago
Keywords: | self-test logging overflow removed |
---|---|
Milestone: | Release 6.6 → undecided |
Priority: | major → minor |
Essentially smartctl prints what the drive firmware returns. If bogus info is returned, there is nothing we could do.
After executing "smartctl -x /dev/sda" all the results of self-test cleared - there are no entries in "smartctl -a /dev/sda" output!
Note that these outputs contain different (legacy vs. extended) self-test logs. Please provide output of both self-test logs (use smartctl -a -x
).
PS: Please do not set the Milestone in future submissions.
by , 7 years ago
comment:4 by , 7 years ago
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE ... 9 Power_On_Hours ------ 100 100 000 - 658 ... SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 654 - ... #19 Short offline Completed without error 00% 581 - ... SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 142 - ... #19 Short offline Completed without error 00% 69 - ... Device Statistics (GP Log 0x04) Page Offset Size Value Flags Description ... 0x01 0x010 4 658 --- Power-on Hours
Hours in (legacy) SMART Self-test log are possibly only returned as 8/9-bit values or as hours - 512
.
comment:6 by , 7 years ago
Milestone: | undecided |
---|---|
Resolution: | → invalid |
Status: | new → closed |
Possibly a harmless firmware problem in legacy SMART Self-test log.
Missing feedback from reporter - closing ticket.
comment:7 by , 7 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
comment:8 by , 7 years ago
===== [SMART READ LOG] DATA START (BASE-16) ===== ... Entry # 1 at offset 2 + (((21- 1) + 14) % 21 * 24) = 314: 304-319: 00 00 00 00 00 00 00 00 00 00[01 00 17 00 00 00 Type (0x01=Short)---------------------^^ Status (0x00=OK)-------------------------^^ Hours (0x0017=23)---------------------------^^-^^ 320-335: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Entry #21 at offset 2 + (((21-21) + 14) % 21 * 24) = 338: 336-351: 00 00|01 00 c2 00 00 00 00 00 00 00 00 00 00 00 Hours (0x00c2=194)--^^-^^ 352-367: 00 00 00 00 00 00 00 00 00 00]02 00 c3 00 00 00 ... 496-511: 00 00 00 00 00 00 00 00 00 00 00 00 0e 00 00 df Self-test index (0x0e=14)-------------------^^ Checksum---------------------------------------------^^ ... Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 23 - ... #21 Short offline Completed without error 00% 194 -
comment:9 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | reopened → closed |
Drive firmware truncates 16-bit self-test hours to 8-bit. Smartctl prints the value correctly.
NB: Power On Hours attribute still increasing with time, so seems like the problem is related to the self-tests only