Re: Issues with LaCie USB3 drive and UAS

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am Donnerstag, den 03.12.2020, 02:11 +0000 schrieb David C. Partridge:

Hi,

cool, thank your for testing! You having spent so much time
and effort on this, let's go through the log with a fine comb.

> Now with uas.ko	and usb-storage.ko 
> 
> Dec 03 02:05:56 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:05:56 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:05:56 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:05:56 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:05:56 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084

This is from usbcore. It reports that a new device has been detected.

> Dec 03 02:05:56 charon mtp-probe[3108]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3108]: bus: 2, device: 2 was not an MTP device

>From udev. It basically means that it is not a camera to import
pictures from.

> Dec 03 02:05:56 charon kernel: usb_storage: loading out-of-tree module taints kernel.
> Dec 03 02:05:56 charon kernel: usb_storage: module verification failed: signature and/or required key missing - tainting kernel
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver usb-storage

The kernel identified the device as storage and udev has loaded drivers
now being probed.

> Dec 03 02:05:56 charon kernel: scsi host5: uas
> Dec 03 02:05:56 charon kernel: usbcore: registered new interface driver uas

UAS is taking the device.

> Dec 03 02:05:56 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0

It is identified as a disk.

> Dec 03 02:05:56 charon mtp-probe[3117]: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:05:56 charon mtp-probe[3117]: bus: 2, device: 2 was not an MTP device

Again, not a camera.

> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:05:56 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Its size and caching attributes are determined. Is the size of 4 TB
correct?

> Dec 03 02:06:13 charon kernel: usb 2-1: USB disconnect, device number 2

A disconnect after 17 seconds. Whether this is a bug or not depends on
whether you pulled the plug. Did you?

> Dec 03 02:06:13 charon kernel: sd 5:0:0:0: [sdc] Optimal transfer size 33553920 bytes
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Sense not available.
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
> Dec 03 02:06:14 charon kernel: sd 5:0:0:0: [sdc] Attached SCSI disk

This has to happen if the device is unavailable.

> Dec 03 02:06:15 charon kernel: usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device found, idVendor=059f, idProduct=105f, bcdDevice= 0.01
> Dec 03 02:06:15 charon kernel: usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> Dec 03 02:06:15 charon kernel: usb 2-1: Product: 2Big Quadra USB3
> Dec 03 02:06:15 charon kernel: usb 2-1: Manufacturer: LaCie
> Dec 03 02:06:15 charon kernel: usb 2-1: SerialNumber: 00000000250e9e711084
> Dec 03 02:06:15 charon kernel: scsi host5: uas
> Dec 03 02:06:15 charon kernel: scsi 5:0:0:0: Direct-Access     LaCie    2Big Quadra v3   051E PQ: 0 ANSI: 6
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: Attached scsi generic sg3 type 0
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] 7814025564 512-byte logical blocks: (4.00 TB/3.64 TiB)
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write Protect is off
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Mode Sense: 43 00 00 00
> Dec 03 02:06:15 charon kernel: sd 5:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> Dec 03 02:06:15 charon mtp-probe[3209]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3209]: bus: 2, device: 3 was not an MTP device
> Dec 03 02:06:15 charon mtp-probe[3212]: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"
> Dec 03 02:06:15 charon mtp-probe[3212]: bus: 2, device: 3 was not an MTP device

This is basically a repeat of the first event.

> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 uas_eh_abort_handler 0 uas-tag 1 inflight: IN 
> Dec 03 02:06:46 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00

This is a SCSI command: REPORT SUPPORTED OPERATION CODES command
Having this command fail is a bit ironic I suppose.

> Dec 03 02:06:46 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:06:47 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:06:47 charon kernel: scsi host5: uas_eh_device_reset_handler success
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler start
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 uas_zap_pending 0 uas-tag 1 inflight: 
> Dec 03 02:07:17 charon kernel: sd 5:0:0:0: tag#28 CDB: Report supported operation codes a3 0c 01 12 00 00 00 00 02 00 00 00
> Dec 03 02:07:17 charon kernel: usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
> Dec 03 02:07:17 charon kernel: scsi host5: uas_eh_device_reset_handler success

And it happens again. This device is seriously buggy. Is it usable
after that or did you just cut the log?

	Regards & Thanks
		Oliver





[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux