USB controllers & peripherals

USB mass storage: Bulk-Only Transport

Bulk-Only Transport carries storage commands through a USB interface before the block device appears.

On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

Mass-storage class 08 alone cannot distinguish Bulk-Only from UAS. For this generic profile, confirm interface subclass and protocol as well as the observed usb-storage binding.

This is an explicit class, transport or driver-context profile. It is not an exact numeric product match.

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

usb_storage registers a USB interface driver and hands storage to the SCSI/block layers. A bridge can expose an ATA, NVMe or flash device behind the same USB transport; those are different identities.

  • usb_storage — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

Device/revision dependent

No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Inspect interfaces and negotiated speed

lsusb -t

This read-only usbutils query normally needs no sudo. Driver belongs to the displayed interface, while speed is the negotiated connection. Other interfaces of the same physical device may use other drivers.

Associate transport with block devices

lsblk -o NAME,TYPE,TRAN,MODEL,SIZE

This read-only util-linux query normally needs no sudo. TRAN=usb identifies the outer transport, while MODEL is a reported label and may describe a bridge or device rather than verified silicon.

Limitations & related issues

A transport binding does not identify the bridge chipset or establish disk health. Do not turn UAS off based only on a generic USB storage label; that would be a configuration change requiring separate evidence.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.