Changes between Initial Version and Version 1 of Ticket #971


Ignore:
Timestamp:
Jan 29, 2018, 1:35:06 PM (3 years ago)
Author:
Christian Franke
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #971 – Description

    initial v1  
    66
    77With UAS enabled I can see info with -d scsi (-d sat{,12} doesn't work), but SMART info is not available:
     8{{{
    89 # smartctl -d scsi -i /dev/sdb
    910smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.15-1-ARCH] (local build)
     
    2425Local Time is:        Sun Jan 28 11:28:14 2018 WET
    2526SMART support is:     Unavailable - device lacks SMART capability.
     27}}}
    2628
    2729If I blacklist UAS, then I get from smartctl:
     30{{{
    2831 # smartctl -i  /dev/sdb
    2932smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.14.15-1-ARCH] (local build)
     
    4649SMART support is: Available - device has SMART capability.
    4750SMART support is: Enabled
     51}}}
    4852
    4953I wonder if it's possible to get SMART access without blacklisting UAS. I don't like the "very big device" messages I receive in dmesg and I guess the device will perform better with UAS enabled (Kernel 4.14.15-1 from Archlinux X86_64).
    50 
     54{{{
    5155kern  :info  : [  +4.501957] usbcore: registered new interface driver usb-storage
    5256kern  :info  : [  +4.470776] usb 4-1.4: new high-speed USB device number 12 using ehci-pci
     
    6771kern  :notice: [  +0.072621] sd 7:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    6872kern  :notice: [  +0.002571] sd 7:0:0:0: [sdb] Attached SCSI disk
    69 
     73}}}
    7074And just in case:
     75{{{
    7176# lsusb -v -d 0bc2:231a                   
    7277Bus 004 Device 010: ID 0bc2:231a Seagate RSS LLC Expansion Portable
     
    106111      bInterfaceProtocol     80 Bulk-Only
    107112      iInterface              0
     113}}}