Custom Query (1560 matches)

Dear maintainers,

I'm currently working with a couple of SATA SSD KINGSTON SKC600MS drive and smartclt cannot show the smart error log page :

# ./sbin/smartctl -l error,256 /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.55-mod-std] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
Invalid Error Log index = 0x0a (T13/1321D rev 1c Section 8.41.6.8.2.2 gives valid range from 1 to 5)

but no error is reported with xerror :

# ./smartctl --log xerror /dev/sda                                                                                                                                                                                                                                                   
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.55-mod-std] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

Disk details :

# ./smartctl -i /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.55-mod-std] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     KINGSTON SKC600MS256G
Serial Number:    50026B77840F1B4D
LU WWN Device Id: 5 0026b7 7840f1b4d
Firmware Version: S4500107
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        Not in smartctl database 7.3/5319
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Aug  9 15:42:08 2022 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Disk firmware seems to be the latest available on Kingston website :

​https://www.kingston.com/fr/support/technical/ksm-firmware-update ​https://media.kingston.com/support/downloads/SKC600_S4500107_RN.pdf

Do you think it's a disk firmware bug ? Or maybe a patch is missing on smartctl side ?

Attached : the full output of ./smartctl --log error -r ataioctl,2 /dev/sda

Spam

Hello,

The drivedb currently contains the following entry:

  { "Phison Driven SSDs", // see MKP_521_Phison_SMART_attribute.pdf
[...]
    "-v 170,raw24/raw24:z54z10,Bad_Blk_Ct_Erl/Lat " // Early bad block/Later bad block

I think that the early and late bad block count values are swapped (late in place of early, early in place of late) and the description should be changed to "Bad_Blk_Ct_Lat/Erl".

According to the documentation in the PDF: ​https://media.kingston.com/support/downloads/MKP_521_Phison_SMART_attribute.pdf

“Bad Block Count (Early / Later)”
Counts the number of Bad blocks.

Raw Value Byte [1~0]: Early bad block count
Raw Value Byte [5~4]: Later bad block count

I have a drive that identifies itself as SSDPR-CX400-512-G2. It is not yet in the database (I will submit it shortly), but the SMART parameters are very likely the same as in SSDPR-CX400-512 (based on comparing with a vendor's tool). Since birth, it had "146" as the raw uninterpreted value of this attribute:

170 Unknown_Attribute       PO----   100   100   000    -    146

but when I modify the drivedb and add it to a regex for "Phison Driven SSDs", it is displayed as:

170 Bad_Blk_Ct_Erl/Lat      PO----   100   100   000    -    0/146

I think that the best way to fix this problem is to change the description to "Bad_Blk_Ct_Lat/Erl" to avoid confusion for people that have historical smartctl outputs stored somewhere.

Greetings,

Mateusz