Hi, Max Mikulin wrote: > Oct 09 09:02:25 hp kernel: usb 3-3: new high-speed USB device number 7 using > xhci_hcd > Oct 09 09:02:25 hp kernel: usb 3-3: New USB device found, idVendor=8564, > idProduct=1000, bcdDevice=11.00 > ... > Oct 09 09:02:25 hp kernel: scsi host4: usb-storage 3-3:1.0 > Oct 09 09:02:27 hp kernel: scsi 4:0:0:0: Direct-Access JetFlash > Transcend 128GB 1100 PQ: 0 ANSI: 6
This is when the kernel USB layer attaches the device as Transcend 8564:1000. The SCSI layer then gets "JetFlash Transcend 128GB" as identification of the storage device (from the SCSI command named "INQUIRY"). > Oct 09 09:51:22 hp kernel: usb 3-3: reset high-speed USB device number 7 > using xhci_hcd > Oct 09 09:51:24 hp kernel: usb 3-3: device firmware changed Something has happend on the USB bus so that the kernel is surprised. > Oct 09 09:51:24 hp kernel: sd 4:0:0:0: [sdb] tag#0 FAILED Result: > hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=2s > Oct 09 09:51:24 hp kernel: sd 4:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 0b f1 > de 30 00 00 f0 00 > Oct 09 09:51:24 hp kernel: I/O error, dev sdb, sector 200400432 op 0x0:(READ) > flags 0x84700 phys_seg 2 prio class 0 > Oct 09 09:51:24 hp kernel: usb 3-3: USB disconnect, device number 7 The SCSI layer perceives a failed read command. The USB layer disconnects the device. > Oct 09 09:51:24 hp kernel: sd 4:0:0:0: [sdb] tag#0 FAILED Result: > hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s > Oct 09 09:51:24 hp kernel: sd 4:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 0b f1 > df 20 00 00 20 00 The USB disconnect does not keep the SCSI layer from trying another read, 240 blocks higher (0x0df1df20 versus 0x0bf1de30 in the first attempt). > Oct 09 09:51:24 hp kernel: I/O error, dev sdb, sector 200400672 op 0x0:(READ) > flags 0x80700 phys_seg 1 prio class 0 > Oct 09 09:51:24 hp kernel: device offline error, dev sdb, sector 200400704 op > 0x0:(READ) flags 0x84700 phys_seg 2 prio class 0 The block device layer chimes in. > Oct 09 09:51:26 hp udisksd[1214]: Cleaning up mount point Userland takes action. > Oct 09 09:51:26 hp kernel: usb 3-3: new high-speed USB device number 8 using > xhci_hcd > Oct 09 09:51:26 hp kernel: usb 3-3: New USB device found, idVendor=090c, > idProduct=3265, bcdDevice= 1.00 > ... > Oct 09 09:51:27 hp kernel: scsi 4:0:0:0: Direct-Access SMI USB MEMORY BAR > 1000 PQ: 0 ANSI: 5 The kernel USB layer detects the device again which now identifies itself as Silicon Motion Inc. 090c:3265. The SCSI identification is now "SMI USB MEMORY BAR". (To my theory these are the generic ids of the board inside the USB stick, which normally should change to the Transcend ids, when the firmware reads what was programmed or configured by Transcend.) > It is possible to boot from the USB stick when it is connected to a USB3 > port of HP ProBook 445 G7. It fails in the case of the USB2 port of the same > laptop. Looks like there is some problem in the USB hardware of the stick, which strikes on most USB ports. I would stop plugging it into the USB ports where it does not work well. If it contains private data, i'd overwrite it with random data via the port where it works (if it works long enough, that is). Then i would return it to the seller. Have a nice day :) Thomas
