#801 closed enhancement (fixed)
Add Kingston A400 SSD to smartdb
| Reported by: | Matthew Eaton | Owned by: | Christian Franke |
|---|---|---|---|
| Priority: | minor | Milestone: | Release 7.0 |
| 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 (3)
Change History (26)
by , 7 years ago
| Attachment: | smartctl-kingston-a400.txt added |
|---|
comment:1 by , 7 years ago
| Keywords: | kingston a400 removed |
|---|---|
| Milestone: | → Release 6.6 |
comment:2 by , 6 years ago
| Milestone: | Release 6.6 → Release 6.7 |
|---|
comment:3 by , 6 years ago
| Owner: | set to |
|---|---|
| Status: | new → accepted |
comment:4 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
comment:5 by , 5 years ago
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
comment:6 by , 5 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
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?
follow-up: 9 comment:8 by , 5 years ago
| Cc: | 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
comment:9 by , 5 years ago
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
comment:13 by , 5 years ago
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 by , 5 years ago
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'
comment:15 by , 5 years ago
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
follow-up: 17 comment:16 by , 5 years ago
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.
follow-up: 20 comment:17 by , 5 years ago
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 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
comment:19 by , 5 years ago
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 by , 5 years ago
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.
by , 4 years ago
| Attachment: | smartctl-KINGSTON-SA400S37480G.txt added |
|---|
comment:22 by , 4 years ago
Comment deleted. This is in https://www.smartmontools.org/browser/trunk/smartmontools/drivedb.h, but was missing from /var/lib/smartmontools/drivedb/drivedb.h
update-smart-driveb (suggested by the faq) does not exist on updated Ubuntu 18.04.5 LTS. Instead, I used:
sudo wget https://raw.githubusercontent.com/smartmontools/smartmontools/master/smartmontools/drivedb.h -O /var/lib/smartmontools/drivedb/drivedb.h
r4765, r4767.