Changes between Version 17 and Version 18 of SAT-with-UAS-Linux


Ignore:
Timestamp:
Nov 23, 2019, 11:36:49 PM (4 years ago)
Author:
Nathan Stratton Treadway
Comment:

make first phrase of each workaround a label in the corresponding HTML anchor name (allowing the user's browser to highlight that phrase when following a link to that anchor)

Legend:

Unmodified
Added
Removed
Modified

  • SAT-with-UAS-Linux

    v17 v18  
    145145There are two approaches to getting smartmontools to work with one of these devices, both involving setting a "quirks" flag for the device in question.
    146146
    147 A. [=#workaround-set-u]If you just want to get smartmontools working again and don't care about the performance improvements the come from using UAS mode, you can simply use the IGNORE_UAS flag to tell Linux to stick with the usb-storage mode instead, by using the "u" flag on the `usb-storage.quirks` setting.[[BR]][[BR]]
    148 A. [=#workaround-unset-t]If you want to continue using UAS mode and are sure your particular device does properly support SAT mode even though the kernel detects it as a device that does not (e.g. as described in ticket:971#comment:12) , you can override that default configuration and suppress the NO_ATA_1X/":t" flag by passing an empty flag list in the `usb-storage.quirks` setting.
     147A. [=#workaround-set-u If you just want to get smartmontools working again and don't care about the performance improvements the come from using UAS mode], you can simply use the IGNORE_UAS flag to tell Linux to stick with the usb-storage mode instead, by using the "u" flag on the `usb-storage.quirks` setting.[[BR]][[BR]]
     148A. [=#workaround-unset-t If you want to continue using UAS mode and are sure your particular device does properly support SAT mode] even though the kernel detects it as a device that does not (e.g. as described in ticket:971#comment:12) , you can override that default configuration and suppress the NO_ATA_1X/":t" flag by passing an empty flag list in the `usb-storage.quirks` setting.
    149149
    150150Note that in either case, you will need to find the idVendor and idProduct fields for your device, in 4-digit hex format.  This information is found in the `New USB device found, idVendor=NNNN, idProduct=NNNN`