Re: Bug#731016: Can't mount external USB HD Asus AN300
Control: reassign -1 src:linux On Ma, 07 ian 14, 10:01:50, Ido Halperin wrote: I have just upgraded into kernel 3.12-1-amd64 but the problem persists. Until this issue will be solved I am trying to find some way to manually create the block device for this HDD but I don't know where I should look. I found some pages about adding scsi device and following that I typed: **$ dmesg | tail -n 100 [...] [24690.748752] usb 2-4: new SuperSpeed USB device number 7 using xhci_hcd [24690.765189] usb 2-4: New USB device found, idVendor=0b05, idProduct=17b6 [24690.765196] usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [24690.765200] usb 2-4: Product: Super Speed Mass Storage [24690.765203] usb 2-4: Manufacturer: USB3.0 Device [24690.765205] usb 2-4: SerialNumber: 40201208020A [24690.765975] usb-storage 2-4:1.0: USB Mass Storage device detected [24690.766258] scsi17 : usb-storage 2-4:1.0 [24691.768698] scsi 17:0:0:0: Direct-Access USB3.0 D Super Speed Mass 0PQ: 1 ANSI: 0 [24691.768878] scsi 17:0:0:1: CD-ROMASMT VirtualCDROM PQ: 0 ANSI: 0 [24691.769160] scsi 17:0:0:0: Attached scsi generic sg2 type 0 [24691.769681] sr1: scsi-1 drive [24691.769834] sr 17:0:0:1: Attached scsi CD-ROM sr1 [24691.769920] sr 17:0:0:1: Attached scsi generic sg3 type 5 [24691.820241] xhci_hcd :00:14.0: WARN Event TRB for slot 14 ep 2 with no TDs queued? [24691.960100] ISO 9660 Extensions: Microsoft Joliet Level 3 [24691.960231] ISOFS: changing to secondary root I understand from that output that 17:0:0:0 is my hdd. I tried: **$ echo 0 0 0 /sys/class/scsi_host/host17/scan but no progress was achieved. Do you know if there is some scsi administration tool that may help me tom manually create the block device file? Ido. -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Processed: Re: Bug#731016: Can't mount external USB HD Asus AN300
Processing control commands: reassign -1 src:linux Bug #731016 [linux-image-3.11-2-amd64] can't mount external USB HDD - /dev/sdb wasn't created (but /dev/sg2 does...) Warning: Unknown package 'linux-image-3.11-2-amd64' Bug reassigned from package 'linux-image-3.11-2-amd64' to 'src:linux'. No longer marked as found in versions linux/3.11.8-1. Ignoring request to alter fixed versions of bug #731016 to the same values previously set -- 731016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b731016.138925493521393.transcr...@bugs.debian.org
Bug#731016: Can't mount external USB HD Asus AN300
On Mon, 2013-12-02 at 18:15 +0100, Josua Dietze wrote:
[...]
In case there IS a driver required on Windows, you might be able to catch the
initial traffic between this driver and the device once the thing is
re-plugged. In a second step, the initiating command(s) can possibly be
'replayed' in Linux. This is the usual way usb_modeswitch works.
Note that if a special Windows driver is required for actually ACCESSING the
disk (not just for initialization), then a new Linux driver may be required
as well ...
[...]
I don't know if it will help but I tried to capture the USB traffic on
Windows station at the time I connected the drive. I got some output but
I don't know it's meaning. That what I got by the USB capturing
software:
USB data
SMI Corporation USB DISK - USB Mass Storage Device
ID: 1
Function: IRP_MJ_PNP
Minor function: PNP_IRP_UNKNOWN (0x18)
Status code: 0xC0BB
Status: ERROR
ID: 2
Function: IRP_MJ_PNP
Minor function: IRP_MN_QUERY_RESOURCE_REQUIREMENTS
Status code: 0xC0BB
Status: ERROR
ID: 3
Function: IRP_MJ_PNP
Minor function: IRP_MN_FILTER_RESOURCE_REQUIREMENTS
Status code: 0xC0BB
Status: ERROR
ID: 4
Function: IRP_MJ_PNP
Minor function: IRP_MN_START_DEVICE
Status code: 0x
Status: STATUS_SUCCESS
ID: 5
Function: IRP_MJ_PNP
Minor function: IRP_MN_QUERY_CAPABILITIES
Status code: 0x
Status: STATUS_SUCCESS
ID: 6
Function: IRP_MJ_PNP
Minor function: IRP_MN_QUERY_PNP_DEVICE_STATE
Status code: 0x
Status: STATUS_SUCCESS
ID: 7
Function: IRP_MJ_SYSTEM_CONTROL
Status code: 0x
Status: STATUS_SUCCESS
That's the properties of the device under windows:
USB device details
USB3.0 Device Super Speed Mass Storage - USB Mass Storage Device
File:
\??\USB#VID_0B05PID_17B6#40201208020A#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
Driver key name: {36fc9e60-c465-11cf-8056-44455354}\0019
Device instance ID: USB\VID_0B05PID_17B6\40201208020A
Device hardware ID: USB\VID_0B05PID_17B6REV_0100
Device service: USBSTOR
Device friendly name:
Device location: Port_#0005.Hub_#0004
Device physical object name: \Device\USBPDO-4
Device descriptor
USB: 0x0210
Device class: 0x00
Device subclass: 0x00
Device protocol: 0x00
Max packet size: 0x40 (64)
Vendor: 0x0B05 (ASUSTek Computer, Inc.)
Product ID: 0x17B6
Device ID: 0x0100
Manufacturer: 0x02 (USB3.0 Device)
Product: 0x03 (Super Speed Mass Storage)
Serial number: 0x01 (40201208020A)
Number of configurations: 1
Connection status: Device connected
Current config value: 0x01
Device bus speed: High (USB 2.0, 480 Mbit/s)
Device address: 0x02
Open pipes: 2
Pipe information
Endpoint address: 0x81, Input
Transfer type: Bulk
Max packet size: 0x0200 (512)
Interval: 0x00 (0)
Pipe information
Endpoint address: 0x02, Output
Transfer type: Bulk
Max packet size: 0x0200 (512)
Interval: 0x00 (0)
Configuration descriptor
Total length: 0x0020
Number of interfaces: 1
Configuration value: 0x01
Configuration ID: 0x00
Attributes: 0xC0 (Bus powered, Self powered)
Max power: 0x00 (0 Ma)
Interface descriptor
Interface number: 0x00
Alternate setting: 0x00
Num of endpoints: 2
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1386279583.9471.6.camel@ihlaptop
Bug#731016: Can't mount external USB HD Asus AN300
I appologize. I accidently posted the traffic of regular flash-memory disk. This is the traffic for the HDD: USB data USB3.0 Device Super Speed Mass Storage - USB Mass Storage Device ID: 1 Function: IRP_MJ_PNP Minor function: PNP_IRP_UNKNOWN (0x18) Status code: 0xC0BB Status: ERROR ID: 2 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_RESOURCE_REQUIREMENTS Status code: 0xC0BB Status: ERROR ID: 3 Function: IRP_MJ_PNP Minor function: IRP_MN_FILTER_RESOURCE_REQUIREMENTS Status code: 0xC0BB Status: ERROR ID: 4 Function: IRP_MJ_PNP Minor function: IRP_MN_START_DEVICE Status code: 0x Status: STATUS_SUCCESS ID: 5 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_CAPABILITIES Status code: 0x Status: STATUS_SUCCESS ID: 6 Function: IRP_MJ_PNP Minor function: IRP_MN_QUERY_PNP_DEVICE_STATE Status code: 0x Status: STATUS_SUCCESS ID: 7 Function: IRP_MJ_SYSTEM_CONTROL Status code: 0x Status: STATUS_SUCCESS Ido On Mon, 2013-12-02 at 18:15 +0100, Josua Dietze wrote: [...] In case there IS a driver required on Windows, you might be able to catch the initial traffic between this driver and the device once the thing is re-plugged. In a second step, the initiating command(s) can possibly be 'replayed' in Linux. This is the usual way usb_modeswitch works. Note that if a special Windows driver is required for actually ACCESSING the disk (not just for initialization), then a new Linux driver may be required as well ... [...] I don't know if it will help but I tried to capture the USB traffic on Windows station at the time I connected the drive. I got some output but I don't know it's meaning. That what I got by the USB capturing software: USB data SMI Corporation USB DISK - USB Mass Storage Device [...] -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386280523.9471.9.camel@ihlaptop
Processed: Re: Bug#731016: Can't mount external USB HD Asus AN300
Processing control commands: reassign -1 linux-image-3.11-2-amd64 3.11.8-1 Bug #731016 [usb-modeswitch] can't mount external USB HDD - /dev/sdb wasn't created (but /dev/sg2 does...) Bug reassigned from package 'usb-modeswitch' to 'linux-image-3.11-2-amd64'. Ignoring request to alter found versions of bug #731016 to the same values previously set Ignoring request to alter fixed versions of bug #731016 to the same values previously set Bug #731016 [linux-image-3.11-2-amd64] can't mount external USB HDD - /dev/sdb wasn't created (but /dev/sg2 does...) Marked as found in versions linux/3.11.8-1. -- 731016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b731016.138615491210348.transcr...@bugs.debian.org
Processed: Re: Bug#731016: Can't mount external USB HD Asus AN300
Processing control commands: tag -1 upstream Bug #731016 [linux-image-3.11-2-amd64] can't mount external USB HDD - /dev/sdb wasn't created (but /dev/sg2 does...) Added tag(s) upstream. -- 731016: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b731016.138616606722115.transcr...@bugs.debian.org
Bug#731016: Can't mount external USB HD Asus AN300
Control: tag -1 upstream On Wed, 2013-12-04 at 12:01 +0100, Didier 'OdyX' Raboud wrote: Control: reassign -1 linux-image-3.11-2-amd64 3.11.8-1 Le mercredi, 4 décembre 2013, 11.01:14 Josua Dietze a écrit : It's clear now that usb_modeswitch can't do anything here. I don't see that at all. There could be some magic file on the virtual CD-ROM that Windows already knows how to interpret. (I don't know what the point of that would be!) Please reassign - my guess is that it's a kernel driver thing, either USB 3.0 host or usb-storage (or both). Hereby reassigning to the originally reported kernel version. Ben: if there's something we (as usb-modeswitch upstream and maintainer) can do to help here, please ask. Well I'm not going to do anything about this, but maybe it can be fixed upstream. Ben. -- Ben Hutchings friends: People who know you well, but like you anyway. signature.asc Description: This is a digitally signed message part
Bug#731016: Can't mount external USB HD Asus AN300
Am 04.12.2013 15:07, schrieb Ben Hutchings: Le mercredi, 4 décembre 2013, 11.01:14 Josua Dietze a écrit : It's clear now that usb_modeswitch can't do anything here. I don't see that at all. There could be some magic file on the virtual CD-ROM that Windows already knows how to interpret. (I don't know what the point of that would be!) That is highly unlikely. After all, there are only two possibilities: 1. Windows accesses the main drive device in a generic (built-in) way. If this included some sort of 'magic' file, then that way of access would be known - if not documented - by now. It's not likely that the Asus drive would be the only device where this special generic access method applied. 2. A special software is used for access or at least for initialisation before using the main drive device. This has been ruled out by Ido's tests. usb_modeswitch helps with devices that change their complete layout after receiving a specific command. In most cases this involves a change of the USB product ID, but there is *always* a change in interface layout and classes. I can't see that with the Asus drive. The interfaces with their expected device class seem to be there from the moment of plug-in. That said, it would become clearer with a detailed lsusb listing. Some interface details are visible in the udev monitoring output from the original report, but not very concise. Ido, can you run the following terminal command with the drive connected? $ sudo lsusb -v -d 0b05:17b6 Then post the output in your reply, please. (As a side note, I noticed that long lines of text are not wrapped on the bug track page - is that intended?) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/529f4940.9090...@draisberghof.de
Bug#731016: Can't mount external USB HD Asus AN300
That what I got: **$ sudo lsusb -v -d 0b05:17b6 Bus 002 Device 004: ID 0b05:17b6 ASUSTek Computer, Inc. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 9 idVendor 0x0b05 ASUSTek Computer, Inc. idProduct 0x17b6 bcdDevice1.00 iManufacturer 2 USB3.0 Device iProduct3 Super Speed Mass Storage iSerial 1 40201208020A bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 44 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xc0 Self Powered MaxPower0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 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 bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0400 1x 1024 bytes bInterval 0 bMaxBurst 15 Binary Object Store Descriptor: bLength 5 bDescriptorType15 wTotalLength 22 bNumDeviceCaps 2 USB 2.0 Extension Device Capability: bLength 7 bDescriptorType16 bDevCapabilityType 2 bmAttributes 0x0002 Link Power Management (LPM) Supported SuperSpeed USB Device Capability: bLength10 bDescriptorType16 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 1 Lowest fully-functional device speed is Full Speed (12Mbps) bU1DevExitLat 10 micro seconds bU2DevExitLat2047 micro seconds Device Status: 0x000d Self Powered U1 Enabled U2 Enabled Regarding the line wrapping, it messed out in the copy-paste procedure. I am sorry for that ... It happend not only for Asus. It seems that this bug appeared 3 years ago for external Corsair disk but no solution was found: http://superuser.com/questions/225314/cant-mount-linux-usb-disk-it-just-create-dev-sg-device-but-no-dev-sd http://forum.corsair.com/v3/showthread.php?t=91434 I also wanted to say to you guy's that I very appreciate your efforts in solving this issue. Thank you. Ido -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386173717.14568.18.camel@ihlaptop
Bug#731016: Can't mount external USB HD Asus AN300
On Wed, 2013-12-04 at 16:24 +0100, Josua Dietze wrote: Am 04.12.2013 15:07, schrieb Ben Hutchings: Le mercredi, 4 décembre 2013, 11.01:14 Josua Dietze a écrit : It's clear now that usb_modeswitch can't do anything here. I don't see that at all. There could be some magic file on the virtual CD-ROM that Windows already knows how to interpret. (I don't know what the point of that would be!) That is highly unlikely. After all, there are only two possibilities: 1. Windows accesses the main drive device in a generic (built-in) way. If this included some sort of 'magic' file, then that way of access would be known - if not documented - by now. It's not likely that the Asus drive would be the only device where this special generic access method applied. [...] Yes, I would expect so. I had a quick look on MSDN and didn't find anything like this. Ben. -- Ben Hutchings Knowledge is power. France is bacon. signature.asc Description: This is a digitally signed message part
