Samsung Flash Drive FIT support (0x090c:0x1000, Silicon Motion)

[René Bertin]

Samsung makes nice little very fast USB3 thumb drives that appear to use something more akin to SSD drives than what's used in regular thumb drives.

They also appear to support SMART:

> smartctl -a -d scsi -T permissive -T permissive -s on /dev/sdc    
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.23-ck1-mainline-core2-rjvb] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor:               Samsung
Product:              Flash Drive FIT
Revision:             1100
Compliance:           SPC-4
User Capacity:        64,160,400,896 bytes [64.1 GB]
Logical block size:   512 bytes
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
Logical Unit id:      0x534d490033323830
Serial number:        AA00000000000489
Device type:          disk
scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
Local Time is:        Mon Jan  4 17:04:42 2021 CET
SMART support is:     Available - device has SMART capability.
SMART support is:     Disabled
Temperature Warning:  Disabled or Not Supported

=== START OF ENABLE/DISABLE COMMANDS SECTION ===
unable to enable Exception control and warning [Operation not permitted]

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK
Current Drive Temperature:     0 C
Drive Trip Temperature:        0 C

Error Counter logging not supported

scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0
Device does not support Self Test logging
Exit 4

> smartctl -a -d test -T permissive -T permissive -s on /dev/sdc    
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.23-ck1-mainline-core2-rjvb] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdc: Unknown USB bridge [0x090c:0x1000 (0x1100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Exit 1

Any chance to get this family of drives supported? Here's some more info:

> lsusb -vvv -d 0x090c:0x1000

Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Couldn't open device, some information will be missing
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.10
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         9
  idVendor           0x090c Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.)
  idProduct          0x1000 Flash Drive
  bcdDevice           11.00
  iManufacturer           1 
  iProduct                2 
  iSerial                 3 
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x002c
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              304mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               8
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               8

[Christian Franke]

Please retry with smartctl -d sat -x /dev/sdc to check whether it uses ATA protocol internally and USB bridge supports SAT pass-through.

[René Bertin]

> sudo smartctl -d sat -x /dev/sdc
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.23-ck1-mainline-core2-rjvb] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported scsi opcode

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
Exit 2

> sudo smartctl -d sat -x -T permissive -T permissive -T permissive -T permissive  /dev/sdc    
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-4.14.23-ck1-mainline-core2-rjvb] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported scsi opcode

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   [No Information Found]
Local Time is:    Thu Jan  7 22:57:42 2021 CET
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.
                  Checking to be sure by trying SMART RETURN STATUS command.
SMART support is: Unknown - Try option -s with argument 'on' to enable it.AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Unavailable
Write cache is:   Unavailable
DSN feature is:   Unavailable
ATA Security is:  Unavailable
Wt Cache Reorder: Unavailable

Read SMART Data failed: scsi error unsupported scsi opcode

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

Read SMART Log Directory failed: scsi error unsupported scsi opcode

General Purpose Log Directory not supported

SMART Extended Comprehensive Error Log (GP Log 0x03) not supported

SMART Error Log not supported

SMART Extended Self-test Log (GP Log 0x07) not supported

SMART Self-test Log not supported

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP/SMART Log 0x04) not supported

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11) not supported

Exit 6

[Christian Franke]

If this device does not support any of the vendor specific pass-through protocols mentioned at the USB wiki page, we could only add it as unsupported to the drive database.

Does this device possibly use a Silicon Motion (SM3282?) USB to SSD controller which does not require a separate USB to SATA/NVMe bridge?

Do you have any evidence that this device provides a pass-through functionality to access SMART data: Vendor information, SMART info from other tools, ... ?

[René Bertin]

I have no idea what's inside or how to figure that out, nor any other evidence than what I posted above. I did look into contacting Samsung about it but if I found an appropriate means of contact I never received a reply. I filed another request with "Samsung Memory Services" (ticket id 17859672).

I was in fact hoping that someone here had some idea on how to obtain additional information or what other things I could try (I saw something about UAS quirks?)

[Christian Franke]

If UAS under Linux would be an issue the error message would be different: scsi error unsupported field in scsi command instead of scsi error unsupported scsi opcode.

Leaving ticket open as undecided.

[René Bertin]

This time I got an answer from Samsung:

Our USBs do have support for SMART diagnostics, however, you will need to use a third party tool.}}}

I've thus asked about the required documentation, but also about existing 3rd party tools that already support these drives.

[René Bertin]

Of course, Samsung being what they are (cheapskates to say the least):

Unfortunately, there is no documentation on how to access this information. We do not give recommendations on third party software. }}}

I've seen that the same USB interface (0x090c:0x1000) is used in other devices and apparently always poses a problem. Any idea why that is?

[Christian Franke]

Related: #1486.