JMicron JMS581DL (0x152d:0x0581, -d sat or -d sntjmicron)

[Cmdr_Zod]

I am a bit unsure if this can be handled by the drivedb, please change component if not set correctly.
I own a noname "M.2 SSD enclosure" with a JMicron JMS581DL inside. This bridge is able ho handle either M.2 SATA or M.2 NVMe drives.
The USB-ID is not known in the drivedb.

Unfortunately, the behavior depends on the SSD installed.

If I put an M.2 SATA SSD into the slot, I can get SMART attributes using
"-d sat". If I have an M.2 NVMe installed, this fails with:

Read Device Identity failed: scsi error unsupported scsi opcode

If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

With an NVMe drive installed, I can use "-d sntjmicron", which works perfectly for NVMe. However, If I use "-d sntjmicron" on a SATA-drive, smartctl hangs.

In short, the way this controller needs to be addressed seems to depend on the drive installed.

lsusb seems to report identical devices whether a SATA or NVMe drive is installed.
The kernel, however, seems to know about the drive type, dmesg is different:
NVMe:

[Tue Nov  5 01:55:06 2024] usb 2-2: new SuperSpeed USB device number 73 using xhci_hcd
[Tue Nov  5 01:55:06 2024] usb 2-2: New USB device found, idVendor=152d, idProduct=0581, bcdDevice=42.04
[Tue Nov  5 01:55:06 2024] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Tue Nov  5 01:55:06 2024] usb 2-2: Product: USB to SATA/PCIe Bridge
[Tue Nov  5 01:55:06 2024] usb 2-2: Manufacturer: General
[Tue Nov  5 01:55:06 2024] usb 2-2: SerialNumber: 0123456789ABCDEF
[Tue Nov  5 01:55:06 2024] scsi host5: uas
[Tue Nov  5 01:55:06 2024] scsi 5:0:0:0: Direct-Access     General  Generic SATA     4204 PQ: 0 ANSI: 6
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: Attached scsi generic sg5 type 0
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] 62533296 512-byte logical blocks: (32.0 GB/29.8 GiB)
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] 4096-byte physical blocks
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Write Protect is off
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Mode Sense: 53 00 00 08
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Preferred minimum I/O size 4096 bytes
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Optimal transfer size 33553920 bytes not a multiple of preferred minimum block size (4096 bytes)
[Tue Nov  5 01:55:06 2024]  sde: sde1 sde2 sde3
[Tue Nov  5 01:55:06 2024] sd 5:0:0:0: [sde] Attached SCSI disk

SATA:

[Tue Nov  5 01:51:04 2024] usb 2-2: new SuperSpeed USB device number 72 using xhci_hcd
[Tue Nov  5 01:51:04 2024] usb 2-2: New USB device found, idVendor=152d, idProduct=0581, bcdDevice=42.04
[Tue Nov  5 01:51:04 2024] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Tue Nov  5 01:51:04 2024] usb 2-2: Product: USB to SATA/PCIe Bridge
[Tue Nov  5 01:51:04 2024] usb 2-2: Manufacturer: General
[Tue Nov  5 01:51:04 2024] usb 2-2: SerialNumber: 0123456789ABCDEF
[Tue Nov  5 01:51:04 2024] scsi host5: uas
[Tue Nov  5 01:51:04 2024] scsi 5:0:0:0: Direct-Access     General  Generic PCIE     4204 PQ: 0 ANSI: 6
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: Attached scsi generic sg5 type 0
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] 125026902 4096-byte logical blocks: (512 GB/477 GiB)
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Write Protect is off
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Mode Sense: 53 00 00 08
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Preferred minimum I/O size 4096 bytes
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Optimal transfer size 268431360 bytes
[Tue Nov  5 01:51:04 2024] sd 5:0:0:0: [sde] Attached SCSI disk
[Tue Nov  5 01:54:51 2024] usb 2-2: USB disconnect, device number 72
[Tue Nov  5 01:54:51 2024] sd 5:0:0:0: [sde] Synchronizing SCSI cache
[Tue Nov  5 01:54:51 2024] sd 5:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK

Is there a way to work around this problem?

[Christian Franke]

An auto detection of -d sat vs. some -d snt* would make sense but does not yet exist.

However, If I use "-d sntjmicron" on a SATA-drive, smartctl hangs.

This is bad news. In this case, trying -d sat first would work but not the other way round.

All we could currently do is to add two entries which tells the user to use -d sat or -d sntjmicron.

Leaving ticket open as undecided for now.