SSDSC2KB019T7R scsi error badly formed scsi parameters

[Mark Heily]

Dell-branded Intel drive with model # SSDSC2KB019T7R is not in the database, and generates an error message in smartctl 6.2:

Read SMART Selective Self-test Log failed: scsi error badly formed scsi parameters

I compiled smartmontools from source and tried again, but got the same error.

See attached for the full output of "smartctl -r ioctl,2 -a /dev/sda"

[Christian Franke]

Please note that drive database and the SCSI error are unrelated. Adding the device to database won't fix the SCSI error.

Possibly related: tickets #819 and #826.

Please check kernel log for original ATA error code (see ticket #826).

[Christian Franke]

Please also provide output of smartctl -r ioctl,2 -x /dev/sda to check whether 48-bit ATA commands (e.g. READ LOG EXT) work. Also include possible kernel messages which report the original ATA error and status code: ...translated ATA stat/err 0x../.. to SCSI SK/ASC/ASCQ 0x5/21/04.

[mad1ost]

I have the same problem but with disk SSDSC2KB480G7R. The output of smartctl -r ioctl,2 -x /dev/sda in attachment.

[Christian Franke]

Please also provide kernel messages related to the error (see ticket #826).

[mad1ost]

Unfortunately there are no any error messages in dmesg. Should I use a more verbose mode?

[Linas Vepstas]

crucial-ct500-smart-v6.6.log

[Linas Vepstas]

My apologies if I'm piling on inappropriately ... have a brand new Crucial MX500 SSD drive, sata-attached. Device Model: CT500MX500SSD1 The smartctl -a looks reasonable, except for:

Read SMART Error Log failed: scsi error badly formed scsi parameters
Read SMART Self-test Log failed: scsi error badly formed scsi parameters
Read SMART Selective Self-test Log failed: scsi error badly formed scsi parameters

This is with smartmon version 6.6 ... no obvious kernel dmesg errors... attaching output of
smartctl -r ioctl,2 -x /dev/sdb ... which ... does show the correct log info: (wow!)

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged
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% 0 -
# 2 Conveyance offline Completed without error 00% 0 -

Above looks correct, since I just plugged in the brand new disk (thus zero lifetime hours), and then ran the conveyance and the short tests...

Simply running smartctl -x /dev/sdb declutters the display slightly, and suggestively reveals the likely problem:

START OF INFORMATION SECTION

... the usual stuff...
Read SCT Status failed: scsi error badly formed scsi parameters
Wt Cache Reorder: Unknown (SCT Feature Control command failed)

START OF READ SMART DATA SECTION

... the usual stuff...
SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

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% 0 -
# 2 Conveyance offline Completed without error 00% 0 -

Read SMART Selective Self-test Log failed: scsi error badly formed scsi parameters

Read SCT Status failed: scsi error badly formed scsi parameters

SCT Error Recovery Control command not supported

[petera703]

Still getting the same issue in Jan 2023...

Device Model:     Samsung SSD 870 EVO 1TB
Device is:        In smartctl database 7.3/5319

Getting the error trying to do a short test:

[root@sysrescue ~]# smartctl -t short /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.83-1-lts] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Read SMART Data failed: scsi error badly formed scsi parameters

And the error is reported repeatedly in the --all output:

[root@sysrescue ~]# smartctl --all /dev/sdb
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.83-1-lts] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 870 EVO 1TB
Serial Number:    S626NF0R233316P
LU WWN Device Id: 5 002538 f4121c384
Firmware Version: SVT01B6Q
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5319
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.3, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Fri Jan 20 16:41:04 2023 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: scsi error badly formed scsi parameters

=== START OF READ SMART DATA SECTION ===
SMART Status command failed: scsi error badly formed scsi parameters
SMART overall-health self-assessment test result: UNKNOWN!
SMART Status, Attributes and Thresholds cannot be read.

Read SMART Log Directory failed: scsi error badly formed scsi parameters

Read SMART Error Log failed: scsi error badly formed scsi parameters

Read SMART Self-test Log failed: scsi error badly formed scsi parameters

Selective Self-tests/Logging not supported

This is a SATA SSD so not sure why it's talking about SCSI anyway?
Hope the additional info helps someone investigate and resolve this eventually.

[petera703]

Another snippet of info that may help investigation: I just tried the SMART test on the same bad disk via Disks in Linux Mint, and here the error is reported as:

Error starting SMART self-test

sk_disk_open:Input/output error (udisks-error-quark,0)