Sensing Drive Temp on Samsung T7 SSD?

So, this is a bit of a surprise. inxi can’t get the drive temperature off a Samsung T7 2.5" SSD plugged directly into the Pi.

  Local Storage: total: 465.76 GiB used: 30.78 GiB (6.6%) 
  ID-1: /dev/sda maj-min: 8:0 type: USB vendor: Samsung model: PSSD T7 
  size: 465.76 GiB block-size: physical: 512 B logical: 512 B type: SSD 
  serial: <filter> scheme: MBR 
  SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? 

The unknown USB bridge part is odd. It’s a USB-C drive, using a USB-C to USB-A cable that came out of the box.

It’s hard to imagine that there’s not a temperature sensor in the enclosure.

(I’m not really worried about cooking the drive, but I do like to check temps from time to time. I’ve caught drives and Pis running hot just because they weren’t getting good airflow.)

EDIT: Here’s what hdparm reports about the drive:

❯ sudo hdparm -I /dev/sda


Unknown device type:
        bits 15&14 of general configuration word 0 both set to 1.
❯ sudo hdparm -I /dev/sda2


ATA device, with non-removable media
        Likely used: 1
        Logical         max     current
        cylinders       0       0
        heads           0       0
        sectors/track   0       0
        Logical/Physical Sector size:           512 bytes
        device size with M = 1024*1024:           0 MBytes
        device size with M = 1000*1000:           0 MBytes 
        cache/buffer size  = unknown
        IORDY not likely
        Cannot perform double-word IO
        R/W multiple sector transfer: not supported
        DMA: not supported
        PIO: pio0 
❯ lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
    |__ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M
❯ sudo hdparm -I /dev/sda1


ATAPI , with removable media
        Media Serial Num:    � � � �p�B�@� �p�F�@
        Media Manufacturer: "� �p�J�@B�
        Transport:          0x23e2; Revision: 0x9100
        Likely used: 3
        DRQ response: 50us.
        Packet size: 12 bytes
        cache/buffer size  = unknown
        Nominal Media Rotation Rate: 53888
        IORDY(may be)(cannot be disabled)
        Overlap support: 40888us to clear BSY after SERVICE cmd.
        DMA: not supported
        PIO: pio0 


Looks like it’s an NVMe interface within a USB enclosure:

As it stands now, it’s unlikely you can feasibly use low-level *nix commands over its USB-to-NVMe bridge.


This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.