Opened 10 years ago
Closed 10 years ago
#343 closed enhancement (fixed)
Read Defect Data commands for SSD
Reported by: | Kimito | Owned by: | Doug Gilbert |
---|---|---|---|
Priority: | minor | Milestone: | Release 6.4 |
Component: | all | Version: | 6.2 |
Keywords: | scsi | Cc: |
Description
The Read Defect Data command on most SAS SSD is going to return CHECK CONDITION for request of LBA, CHS, BFI format. Usually for KCQ=01/1C/02 "defect list not found".
This is because the retired NAND media does not fit any of those convictions. Most SAS SSD vendors will support and return a vendor unique format which depending on the vendor may not give you the format definition. Then this command becomes useful only to the vendor. Fortunately, most vendors provide other means to look at bad blocks.
My issue is that I use smartctl a lot and every time I run it during a long test run, it generates a bunch of CHECK CONDITIONS in my outputs that I have to filter out.
Could smartctl omit the Read Defect Data command if the device is an SSD? or provide a switch so that I can disable checking for defect through Read Defect Data?
Change History (5)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Keywords: | scsi added; SSD Read Defect Data removed |
---|---|
Milestone: | → Release 6.4 |
comment:3 by , 10 years ago
My issue is that I use smartctl a lot and every time I run it during a long test run, it generates a bunch of CHECK CONDITIONS in my outputs that I have to filter out.
Smartctl does not print any error message if a read defect command failed unless debug output is enabled (-r ioctl).
Please provide a sample smartctl command with output (as attachment).
comment:4 by , 10 years ago
Owner: | set to |
---|---|
Status: | new → assigned |
Sorry, the line above "This is because the retired NAND media does not fit any of those convictions." should have said "convention" not conviction.