Changes between Version 16 and Version 17 of USB
- Timestamp:
- Mar 28, 2019, 7:28:38 PM (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
USB
v16 v17 9 9 = USB devices and smartmontools = 10 10 11 To access USB storage devices, the operating system sends SCSI commands through the USB transport to the device. If the USB device is actually a PATA or SATA disk in an USB enclosure, the firmware of its USB bridge chip translates these commands into the corresponding ATAcommands. This works straightforward for read and write commands, but not for SMART commands.11 To access USB storage devices, the operating system sends SCSI commands through the USB transport to the device. If the USB device is actually a (S)ATA or NVMe drive in an USB enclosure, the firmware of its USB bridge chip translates these commands into the corresponding ATA or NVMe commands. This works straightforward for read and write commands, but not for SMART commands. 12 12 13 To access SMART functionality, smartmontools must be able to send ATA commands directly to the disk. For USB devices, at least the following conditions must be met:14 * The USB bridge provides an ATA pass-through command.13 To access SMART functionality, smartmontools must be able to send native ATA or NVMe commands directly to the drive. For USB devices, at least the following conditions must be met: 14 * The USB bridge provides an ATA or NVMe pass-through command. 15 15 * This command is supported by smartmontools. 16 16 * The operating system provides a SCSI pass-through I/O-control which works through its USB-layer. 17 17 * SCSI support is implemented in the operating system interface of smartmontools. 18 18 19 Some recent USB bridges already support the vendor independent SAT (SCSI/ATA Translation, ANSI INCITS 431-2007) standard. Other USB bridges provide vendor specific ATApass-through commands. The current version of smartmontools supports the following pass-through commands and USB bridges:19 Many recent USB to SATA bridges support the vendor independent SAT (SCSI/ATA Translation, ANSI INCITS 431-2007) standard (there is no such standard for NVMe). Other USB bridges provide vendor specific pass-through commands. The current version of smartmontools supports the following pass-through commands and USB bridges: 20 20 ||= '''Command''' =||= '''USB bridges''' =||= '''smartctl option''' =||= '''48-bit ATA support''' =||= '''Comment''' =|| 21 21 || SAT ATA pass-through 12 and 16 || various (ASMedia, Initio, Oxford, newer JMicron, ...) || -d sat[,16]; -d sat,12 || requires '-d sat[,16]' || Older Linux kernels may require '-d sat,12' || … … 24 24 || Prolific ATA pass-through || Prolific PL2571/2771/2773/2775 || -d usbprolific || Yes || SMART access via eSATA may not work (ticket #719) || 25 25 || Sunplus ATA pass-through || Sunplus SPIF215/6, SPIF225/6 || -d usbsunplus || Yes || || 26 || JMicron NVMe pass-through || JMicron JMS583 || -d sntjmicron || n/a || Supported since smartmontools 7.0 || 26 27 27 28 Smartmontools was successfully tested with [wiki:Supported_USB-Devices many USB devices] on several Platforms. If the USB ID can be obtained from the operating system, smartmontools also supports auto-detection of (the already tested) USB devices. Then it is not necessary to specify the '-d' option. See the following table for details: