[smartmontools-support] Incorrect bad drive report on Debian ARM dev board - Intel

[Christian Franke]

David Pottage wrote:
> I have a brand new Intel D3-S4510 SDD. On my ARM dev board smartctl 
> report it as bad, and sometimes causes a kernel panic, and then a 
> bootloop. On my Ubuntu desktop (with an AMD64 CPU) it is reported as 
> fine.

The latter is likely true, see below.

> The drive is about 3 days old, and I have not written any data to it, 
> though I did update the firmware to the latest release from Intel 
> using their isdct tool.
>
> My Arm dev board is an Allwinner cubietruck board running debian 
> stretch (oldstable) with kernel 4.19.0-0.bpo.2-armmp-lpae
>
> The drive is connected via a USB3 to SATA adaptor.

USB Id (lsusb output) of the adapter ?


> I tested using the 7.0 release of smartmontools that I compiled from 
> source. I used the latest version of drivedb.h taken from SVN.
>
> ...
> root at central:~# /home/david/Downloads/smartmontools-7.0/smartctl 
> /dev/sdb -x
> ...
> Model Family:     Intel S4510/S4610/S4500/S4600 Series SSDs
> Device Model:     INTEL SSDSC2KB240G8
> ...
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: FAILED!
> Drive failure expected in less than 24 hours. SAVE ALL DATA.

Unlike other commands issued by smartctl, SMART STATUS requires ATA 
output registers which are occasionally not properly returned by USB 
pass-through layers.


> No failed Attributes found.
>
> General SMART Values:
> Offline data collection status:  (0x00)    Offline data collection 
> activity
>                     was never started.
>                     Auto Offline Data Collection: Disabled.
> Total time to complete Offline
> data collection:         (    0) seconds.
> Offline data collection
> capabilities:              (0x00)     Offline data collection not 
> supported.
> SMART capabilities:            (0x0000)    Automatic saving of SMART 
> data                    is not implemented.
> Error logging capability:        (0x00)    Error logging supported.
>                     General Purpose Logging supported.

SMART READ DATA apparently command returned nothing (all zero data 
block) when issued via this USB bridge.


> ...
> ATA_READ_LOG_EXT (addr=0x03:0x00, page=0, n=1) failed: scsi error 
> aborted command
> Read SMART Extended Comprehensive Error Log failed
>
> Read SMART Error Log failed: scsi error aborted command
> ...
> ATA_READ_LOG_EXT (addr=0x11:0x00, page=0, n=1) failed: scsi error 
> aborted command
> Read SATA Phy Event Counters failed

These may SCSI errors suggest that the USB bridge only supports a small 
subset of ATA pass-through commands.

Conclusion: This output does not indicate a problem with this SSD. It 
indicates a problem in the SAT (or vendor specific) pass-through 
functionality of the USB bridge.

For further diagnostics, please provide the output of this command as an 
attachment:
smartctl -r ioctl,2 -icAH /dev/sdb

Thanks,
Christian