Opened 2 years ago
Last modified 7 months ago
#1070 new defect
SSDSC2KB019T7R scsi error badly formed scsi parameters
Reported by: | Mark Heily | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | undecided |
Component: | all | Version: | 6.2 |
Keywords: | linux scsi | Cc: |
Description
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"
Attachments (3)
Change History (9)
Changed 2 years ago by
Attachment: | smartctl6_2_with_ioctl.txt added |
---|
comment:1 Changed 2 years ago by
Keywords: | linux scsi added |
---|---|
Milestone: | → undecided |
comment:2 Changed 2 years ago by
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
.
comment:3 Changed 20 months ago by
I have the same problem but with disk SSDSC2KB480G7R. The output of smartctl -r ioctl,2 -x /dev/sda
in attachment.
Changed 20 months ago by
Attachment: | smartctl_output.txt added |
---|
comment:4 Changed 20 months ago by
Please also provide kernel messages related to the error (see ticket #826).
comment:5 Changed 19 months ago by
Unfortunately there are no any error messages in dmesg. Should I use a more verbose mode?
comment:6 Changed 7 months ago by
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
Oh, that's weird ... so I started to just plain use the disk, i.e. gdisk, copy data onto it, etc. and now the log is .. sort of working ... it shows the below ... so that is unexpected but pleasant surprise...
Read SMART Error Log failed: scsi error badly formed scsi parameters SMART Self-test log structure revision number 1 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
... or not ... half an hour later, the self-test log has disappeared, again. (but still visible with smartctl -x
) I conclude that I have in my possession brand-new faulty hardware with some kind of intermittency bug ...
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).