KINGSTON SKC600M : "-l error" returns Invalid Error Log index

[Kévin]

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

[Kévin]

./smartctl --log error -r ataioctl,2 /dev/sda

[Kévin]

./smartctl -a /dev/sda

[Kévin]

Thank you very much

Have a nice day
Kévin

[Christian Franke]

This is likely a harmless firmware bug. Some devices don't support the legacy (28-bit LBA only) error log at all, therefore smartctl -a should not be used

Please provide output of smartctl -x as an attachment.

[Christian Franke]

The hex dump of the error log sector actually shows an error log index of 10 (which does not make sense for a log with 5 entries), a bogus first log entry and an error count of 0.

REPORT-IOCTL: Device=/dev/sda Command=SMART READ LOG InputParameter=1
 Input:   FR=0xd5, SC=0x01, LL=0x01, LM=0x4f, LH=0xc2, DEV=...., CMD=0xb0 IN
 [Duration: 0.000141s]
REPORT-IOCTL: Device=/dev/sda Command=SMART READ LOG returned 0

===== [SMART READ LOG] DATA START (BASE-16) =====
000-015: 01 0a 00 00 00 00 00 00 00 c8 00 00 00 00 00 00
              [<-------- bogus first entry -------------
            ^^---- bogus index 10
016-031: 00 00 00 00 00 ec 00 00 00 00 00 00 00 00 00 00
...
080-095: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
         --------- bogus first entry --------->]
...
448-463: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
                     ^^-^^---- error count 0
464-479: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
480-495: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
496-511: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 91
                                                      ^^---- checksum

Conclusion: Firmware bug.

[Kévin]

Thanks for taking a look and for the clarification. I'll take this case to Kingston

[Christian Franke]

Harmless SSD firmware bug, not a smartctl issue.

[Christian Franke]

Related minor improvement: r5407.