Changes between Initial Version and Version 1 of Ticket #594, comment 7


Ignore:
Timestamp:
Mar 6, 2016, 4:23:07 PM (5 years ago)
Author:
smartuser
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #594, comment 7

    initial v1  
    99The problem is when the enclosure runs in the enhanced UASP mode. Disabling UASP for the enclosure should allow access to the SMART functions of the the underlying drive.
    1010
    11 The solution is to blacklist the UAS driver and force the kernel to use the default USB mass storage driver. This can be done by creating a module options file inside /etc/modprobe.d/.
     11The trick is to blacklist the UAS driver and force the kernel to use the default USB mass storage driver. This can be done by creating a module options file inside /etc/modprobe.d/.
    1212
    1313For example in my case, the file is named:
     
    2121}}}
    2222
    23 The alphanumeric code after quirks= are the USB vendor and product IDs output by dmesg or lusub.
     23The alphanumeric code after quirks= is the USB vendor and product IDs output by dmesg or lusub.
    2424 
    2525The additional module directive should work without rebooting provided the "uas" module is not loaded. If the module has already been loaded, you can try to unload it using the command "modprobe -r uas" before inserting or reinserting your USB enclosure.
     
    4343[73162.672202] sd 3:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/931 GiB)
    4444}}}
     45
     46Incidentally, smartctl for this chipset  works out-of-the-box in Ubuntu 14.04, probably because its 3.x kernel still doesn't include uas support, but not in the latest Debian unstable (Linux 4.x).