#1054 closed enhancement (wontfix)
Unknown USB bridge 0x26bd:0x9917
Reported by: | Pro Backup | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | all | Version: | 6.6 |
Keywords: | Cc: |
Description
# smartctl --all /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org /dev/sdb: Unknown USB bridge [0x26bd:0x9917 (0x100)] Please specify device type with the -d option. Use smartctl -h to get a usage summary # lsusb -d 0x26bd:0x9917 -v Bus 001 Device 002: ID 26bd:9917 Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.10 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x26bd idProduct 0x9917 bcdDevice 1.00 iManufacturer 1 iProduct 2 USB DISK 3.0 iSerial 3 0701672129FCF433 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x0020 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 300mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Binary Object Store Descriptor: bLength 5 bDescriptorType 15 wTotalLength 0x0016 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType 16 bDevCapabilityType 2 bmAttributes 0x00000006 BESL Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength 10 bDescriptorType 16 bDevCapabilityType 3 bmAttributes 0x00 wSpeedsSupported 0x000e Device can operate at Full Speed (12Mbps) Device can operate at High Speed (480Mbps) Device can operate at SuperSpeed (5Gbps) bFunctionalitySupport 2 Lowest fully-functional device speed is High Speed (480Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat 2047 micro seconds can't get debug descriptor: Resource temporarily unavailable Device Status: 0x0000 (Bus Powered) # smartctl --all -T permissive -d sat,auto /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Product: USB DISK 3.0 Revision: PMAP Compliance: SPC-4 User Capacity: 31,029,460,992 bytes [31.0 GB] Logical block size: 512 bytes scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 >> Terminate command early due to bad response to IEC mode page === START OF READ SMART DATA SECTION === Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Error Counter logging not supported scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 Device does not support Self Test logging # smartctl --all -T verypermissive -d sat,auto /dev/sdb smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Vendor: Product: USB DISK 3.0 Revision: PMAP Compliance: SPC-4 User Capacity: 31,029,460,992 bytes [31.0 GB] Logical block size: 512 bytes scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 >> Terminate command early due to bad response to IEC mode page === START OF READ SMART DATA SECTION === Current Drive Temperature: 0 C Drive Trip Temperature: 0 C Error Counter logging not supported scsiModePageOffset: response length too short, resp_len=4 offset=4 bd_len=0 Device does not support Self Test logging
Change History (5)
comment:1 by , 6 years ago
Milestone: | → undecided |
---|
comment:2 by , 6 years ago
-d sat looks less promising:
# smartctl --all -T verypermissive -d sat /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported scsi opcode === START OF INFORMATION SECTION === Device Model: [No Information Found] Serial Number: [No Information Found] Firmware Version: [No Information Found] Device is: Not in smartctl database [for details use: -P showall] ATA Version is: [No Information Found] Local Time is: Sat Jul 28 22:42:35 2018 CEST SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. Checking to be sure by trying SMART RETURN STATUS command. SMART support is: Unknown - Try option -s with argument 'on' to enable it. Read SMART Data failed: scsi error unsupported scsi opcode === START OF READ SMART DATA SECTION === SMART Status command failed: scsi error unsupported scsi opcode SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Read SMART Error Log failed: scsi error unsupported scsi opcode Read SMART Self-test Log failed: scsi error unsupported scsi opcode Selective Self-tests/Logging not supported
Maybe I should indeed try to turn SMART on:
# smartctl -T verypermissive -s on -d sat /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported scsi opcode SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. Checking to be sure by trying SMART RETURN STATUS command. SMART support is: Unknown - Try option -s with argument 'on' to enable it.=== START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enable failed: scsi error unsupported scsi opcode
Now with sat,12:
# smartctl -T verypermissive -s on -d sat,12 /dev/sda smartctl 6.6 2017-11-05 r4594 [x86_64-linux-4.17.10-1-ARCH] (local build) Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: scsi error unsupported scsi opcode SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported. SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled. Checking to be sure by trying SMART RETURN STATUS command. SMART support is: Unknown - Try option -s with argument 'on' to enable it.=== START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enable failed: scsi error unsupported scsi opcode
note: Strange to suggest a user to try option -s with argument 'on' when the user has already supplied that option.
comment:3 by , 6 years ago
note: Strange to suggest a user to try option -s with argument 'on' when the user has already supplied that option.
Yes, this (very old) message is not suitable for this corner case.
comment:4 by , 6 years ago
Milestone: | undecided |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
This is a USB flash drive. These devices do not support ATA SMART.
Various other devices with same USB ID exist, see http://usbspeed.nirsoft.net/?vid=9917&pid=39191.
comment:5 by , 6 years ago
Summary: | Unknown USB bridge 0x26bd:0x9917 Samsung MUF-32BB → Unknown USB bridge 0x26bd:0x9917 |
---|
Note:
See TracTickets
for help on using tickets.
Option
-d sat,auto
does not detect SAT support of USB drives because these never return"ATA "
as SCSI VENDOR string. Please try-d sat
or-d sat,12
.