Opened 23 months ago

Closed 2 weeks ago

Last modified 2 weeks ago

#801 closed enhancement (fixed)

Add Kingston A400 SSD to smartdb

Reported by: Matthew Eaton Owned by: Christian Franke
Priority: minor Milestone: Release 6.7
Component: drivedb Version:
Keywords: Cc: AGHost

Description

Please add Kingston A400 SSD to smartdb.

Model numbers:
KINGSTON SA400S37120G
KINGSTON SA400S37240G
KINGSTON SA400S37480G

Datasheet:
http://www.kingston.com/datasheets/SA400S37_us.pdf

SMART attributes:
http://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf

Attachments (2)

smartctl-kingston-a400.txt (9.6 KB) - added by Matthew Eaton 23 months ago.
kingston.txt (6.2 KB) - added by AGHost 3 weeks ago.
Out of smartctl -r ioctl,2 -i command

Download all attachments as: .zip

Change History (22)

Changed 23 months ago by Matthew Eaton

Attachment: smartctl-kingston-a400.txt added

comment:1 Changed 23 months ago by Christian Franke

Keywords: kingston a400 removed
Milestone: Release 6.6

comment:2 Changed 13 months ago by Christian Franke

Milestone: Release 6.6Release 6.7

comment:3 Changed 3 months ago by Christian Franke

Owner: set to Christian Franke
Status: newaccepted

comment:4 Changed 3 months ago by Christian Franke

Resolution: fixed
Status: acceptedclosed

comment:5 Changed 3 weeks ago by AGHost

Hello

Today I'm update smartmontools to 6.7 and DB from trunk. But this SSD still unsupported.

=== START OF INFORMATION SECTION ===
Device Model:     KINGSTON  SA400S37480G
Serial Number:    50026B777301E2CD
LU WWN Device Id: 5 000000 000000000
Firmware Version: SBFK10D7
User Capacity:    480,103,981,056 bytes [480 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Nov 21 15:38:13 2018 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Unavailable

But information in

Last edited 3 weeks ago by Christian Franke (previous) (diff)

comment:6 Changed 3 weeks ago by AGHost

Resolution: fixed
Status: closedreopened

But information in exists:

# grep SA400S37 /usr/share/smartmontools/drivedb.h

"KINGSTON SA400S37(120|240|480|960)G", Kingston A400 SSD/SBFKB1D1

How to solve this?

comment:7 Changed 3 weeks ago by AGHost

And my firmware version differ than - SBFKB1D1. I have - SBFK10D7

comment:8 Changed 3 weeks ago by AGHost

Cc: AGHost added
Version: 6.5

More info:

#smartctl -P showall |grep SA400
MODEL REGEXP:       KINGSTON SEDC400S37(400|480|800|960|1600|1800)G|KINGSTON SUV300S37A(120|240|480)G|KINGSTON SKC310S3B?7A960G|KINGSTON SKC400S37(128G|256G|512G|1T)|KINGSTON SV310S3(7A|D7|N7A|B7A)960G|PNY CS1311 (120|240|480|960)GB SSD|SSD Smartbuy (60|120|240)GB|KINGSTON SHSS3B?7A(120|240|480|960)G|KINGSTON **SA400S37(120|240|480|960)G**

Full output:

smartctl 6.7 2018-11-13 r4834 [x86_64-linux-3.10.0-862.3.3.el7.x86_64] (local build)
Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     KINGSTON  SA400S37480G
Serial Number:    50026B777301E2CD
LU WWN Device Id: 5 000000 000000000
Firmware Version: SBFK10D7
User Capacity:    480,103,981,056 bytes [480 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Nov 21 15:51:43 2018 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever
					been run.
Total time to complete Offline
data collection: 		(65535) seconds.
Offline data collection
capabilities: 			 (0x79) SMART execute Offline immediate.
					No Auto Offline data collection support.
					Suspend Offline collection upon new
					command.
					Offline surface scan supported.
					Self-test supported.
					Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine
recommended polling time: 	 (   4) minutes.
Extended self-test routine
recommended polling time: 	 (  32) minutes.
Conveyance self-test routine
recommended polling time: 	 (   8) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000a   100   100   000    Old_age   Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       13201
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       7
167 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       0
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
169 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       10
170 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       20
172 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       13500752
181 Program_Fail_Cnt_Total  0x0012   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0032   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       5
194 Temperature_Celsius     0x0023   080   062   000    Pre-fail  Always       -       20 (Min/Max 17/38)
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0032   100   100   000    Old_age   Always       -       0
218 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       0
231 Temperature_Celsius     0x0013   100   100   000    Pre-fail  Always       -       79
233 Media_Wearout_Indicator 0x0013   100   100   000    Pre-fail  Always       -       77857
241 Total_LBAs_Written      0x0012   100   100   000    Old_age   Always       -       82489
242 Total_LBAs_Read         0x0012   100   100   000    Old_age   Always       -       69347
244 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       206
245 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       336
246 Unknown_Attribute       0x0000   100   100   000    Old_age   Offline      -       18016064

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%     13136         -

SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited 3 weeks ago by Christian Franke (previous) (diff)

comment:9 in reply to:  8 Changed 3 weeks ago by Christian Franke

Device Model:     KINGSTON  SA400S37480G

Does the drive actually report two spaces between vendor and model? Never seen this before.

If yes, this is the root of the problem.

Please provide the output of smartctl -r ioctl,2 -i ... as an attachment. Don't paste it into a comment.

Regex match results from latest CircleCI build for Windows:

$ smartctl
smartctl 6.7 2018-11-13 r4834 [i686-w64-mingw32-w10-1803(64)] (CircleCI)
...

$ smartctl -P showall "KINGSTON  SA400S37480G"
No presets are defined for this drive.  Its identity strings:
MODEL:    KINGSTON  SA400S37480G
FIRMWARE: (any)
do not match any of the known regular expressions.

$ smartctl -P showall "KINGSTON SA400S37480G"
Drive found in smartmontools Database.  Drive identity strings:
MODEL:              KINGSTON SA400S37480G
FIRMWARE:           (any)
match smartmontools Drive Database entry:
MODEL REGEXP:       KINGSTON SEDC400S37(400|480|800|960|1600|1800)G|...
FIRMWARE REGEXP:    .*
MODEL FAMILY:       Phison Driven SSDs
ATTRIBUTE OPTIONS:  002 Not_In_Use
                    003 Not_In_Use
                    005 Retired_Block_Count
...
                    246 Total_Erase_Count

Changed 3 weeks ago by AGHost

Attachment: kingston.txt added

Out of smartctl -r ioctl,2 -i command

comment:10 Changed 3 weeks ago by AGHost

Yes, have double spaces between KINGSTON and SA400S37480G

comment:11 Changed 3 weeks ago by AGHost

I have 4 SSD on this server and all have 2 spaces in device model.

comment:12 Changed 3 weeks ago by AGHost

And patching drivedb.h with add one space resolved this issue.

comment:13 Changed 3 weeks ago by Christian Franke

Interestingly there is only one space in the sample output attached above which reports same firmware version SBFK10D7 but different size.

Is there any special SATA(RAID?) controller involved? In the past, there were few cases were controller firmware modified ATA IDENTIFY data.

comment:14 Changed 3 weeks ago by AGHost

No, server have only software raid 10 and don't have any separate disk controllers. This is old server with Xeon E5640, those disks work only on 3Gbit instead of 6.

message log:

Device: /dev/sda, type changed from 'scsi' to 'sat'

Last edited 3 weeks ago by AGHost (previous) (diff)

comment:15 Changed 3 weeks ago by AGHost

I'm testing on other server with i7-7700K and have double spaces. So, this is not controller issue:

=== START OF INFORMATION SECTION ===
Device Model:     KINGSTON  SA400S37480G
Serial Number:    50026B777301E2B0
Last edited 2 weeks ago by Christian Franke (previous) (diff)

comment:16 Changed 2 weeks ago by Matthew Eaton

I'm not seeing the double spacing in your last comment?

Edit: Nevermind, looks like trac truncated the extra white space. It may be that identify device was set erroneously and we didn't catch it. You can contact our technical support and get them replaced with new drives.

But keep in mind your replacement drives may use a different controller than what you have now (Phison S11). We use different controllers for the A400 model family and you may get a Phison-based drive or a SMI-based drive, or even something else in the future.

Last edited 2 weeks ago by Matthew Eaton (previous) (diff)

comment:17 in reply to:  16 ; Changed 2 weeks ago by Christian Franke

I'm not seeing the double spacing in your last comment?

Now made visible with Trac markup for preformatted text.

We use different controllers for the A400 model family and you may get a Phison-based drive or a SMI-based drive, or even something else in the future.

Do IDENTIFY strings and/or attributes depend on controller?

comment:18 Changed 2 weeks ago by Christian Franke

Resolution: fixed
Status: reopenedclosed

Extra space added to regex in r4836, r4837.

comment:19 Changed 2 weeks ago by AGHost

I'm not seeing the double spacing in your last comment?

Probably this website converted double-spaces to tab when I'm paste from terminal. And you will see one symbol.

Extra space added to regex

Thank you, now all is fine.

comment:20 in reply to:  17 Changed 2 weeks ago by Matthew Eaton

We use different controllers for the A400 model family and you may get a Phison-based drive or a SMI-based drive, or even something else in the future.

Do IDENTIFY strings and/or attributes depend on controller?

For the A400 model family:
The model number will always be the same (although the double spacing was a mistake).
The firmware revision number will change depending on the controller used.
The SMART attributes *should* remain the same.
Some other identify strings may change depending on what features that particular controller supports.

BTW thanks for fixing this issue in drivedb.

Last edited 2 weeks ago by Matthew Eaton (previous) (diff)
Note: See TracTickets for help on using tickets.