Overview & identity
Class 08 is only secondary context; the UAS path examines SCSI subclass, interface alternatives and protocol. A product advertising USB 3 is not automatically observed to use UAS.
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
The uas driver has class matches for relevant storage interfaces and checks whether the UAS alternative can be used. Actual lsusb -t binding tells whether uas or usb-storage won probing on this boot.
uas— kernel driver/module candidate
Firmware
Device/revision dependent
No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.
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 -tThis 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.
Read this boot’s storage and USB messages
journalctl -k -b --no-pagerThis reads kernel messages without changing the driver. Access depends on journal permissions; use sudo only if the local policy denies the read. Correlate reset timestamps with the same port and storage target.
Limitations & related issues
Resets can involve the cable, power, bridge firmware, host controller or media. This profile neither identifies an exact bridge nor declares every UAS device affected by a quirk.
These guides are linked for relevant observations, not as known defects of every device in this family.
- USB storage resets while using UAS · First documented next step
- SATA CRC errors and repeated link resets · First documented next step
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.
- Linux: drivers/usb/storage/uas.c
Reviewed upstream source
uas_usb_ids[] - Linux: drivers/usb/storage/uas.c
Reviewed upstream source
uas_switch_interface - Linux: Documentation/driver-api/usb/usb.rst
Project or distribution documentation
struct usb_driver