At least with kernel 5.3 I was still needing the patch to not get my disk failing after some time of inactivity. What output would you need from it? lsusb -v? Maybe the blacklist is "too general" and should be more restricted. In my case, with uas, it fails easily simply doing to work on the disk, leaving it for some minutes (I don't know...maybe 15 mins...), and when you try to use it again, it fails. On the other hand, with usb-storage it works perfectly. Thanks El jue., 16 abr. 2020 a las 3:49, Steven Ellis (<sellis@xxxxxxxxxx>) escribió: > > Afraid I don't have access to an enclosure for testing at present as it is on extended loan to someone. > > Steven > > On Thu, 16 Apr 2020 at 13:28, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: >> >> On Wed, 15 Apr 2020, Cyril Roelandt wrote: >> >> > Hello, >> > >> > I own a WD Blue 1TB hard drive that I use in combination with an Icy Box >> > IB-273StU3-B enclosure in order to plug it to my laptop using USB. It >> > worked fine with all the Linux versions I tried, up until 5.4.17. >> > >> > >> > Using Linux 5.3 >> > --------------- >> > Everything works as expected when I plug the drive, and I can mount the >> > partitions: >> > >> > # dmesg -T >> > [Sun Mar 22 23:48:39 2020] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd >> > [Sun Mar 22 23:48:39 2020] usb 2-2: New USB device found, idVendor=357d, idProduct=7788, bcdDevice= 1.14 >> > [Sun Mar 22 23:48:39 2020] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 >> > [Sun Mar 22 23:48:39 2020] usb 2-2: Product: USB to ATA/ATAPI Bridge >> > [Sun Mar 22 23:48:39 2020] usb 2-2: Manufacturer: JMicron >> > [Sun Mar 22 23:48:39 2020] usb 2-2: SerialNumber: 74D7851513309E5 >> > [Sun Mar 22 23:48:39 2020] usbcore: registered new interface driver usb-storage >> > [Sun Mar 22 23:48:39 2020] scsi host6: uas >> > [Sun Mar 22 23:48:39 2020] usbcore: registered new interface driver uas >> > [Sun Mar 22 23:48:39 2020] scsi 6:0:0:0: Direct-Access WDC WD10 JPVT-00A1YT0 0114 PQ: 0 ANSI: 6 >> > [Sun Mar 22 23:48:39 2020] sd 6:0:0:0: Attached scsi generic sg1 type 0 >> > [Sun Mar 22 23:48:39 2020] sd 6:0:0:0: [sdb] Spinning up disk... >> > [Sun Mar 22 23:48:40 2020] ..ready >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] 4096-byte physical blocks >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] Write Protect is off >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] Mode Sense: 53 00 10 08 >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes) >> > [Sun Mar 22 23:48:41 2020] sdb: sdb1 >> > [Sun Mar 22 23:48:41 2020] sd 6:0:0:0: [sdb] Attached SCSI disk >> > >> > >> > Using Linux 5.4 >> > --------------- >> > >> > # uname -a >> > Linux Susan 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux >> > >> > # mkdir /tmp/mnt >> > >> > # mount /dev/sdb1 /tmp/mnt >> > mount: /tmp/mnt: can't read superblock on /dev/sdb1. >> > >> > # fsck -y /dev/sdb1 >> > fsck from util-linux 2.34 >> > e2fsck 1.45.6 (20-Mar-2020) >> > /dev/sdb1: clean, 2951657/61054976 files, 115035523/244190208 blocks >> > >> > # dmesg -T >> > [Mon Mar 23 18:43:06 2020] usb 3-2: new SuperSpeed Gen 1 USB device number 8 using xhci_hcd >> > [Mon Mar 23 18:43:06 2020] usb 3-2: New USB device found, idVendor=357d, idProduct=7788, bcdDevice= 1.14 >> > [Mon Mar 23 18:43:06 2020] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 >> > [Mon Mar 23 18:43:06 2020] usb 3-2: Product: USB to ATA/ATAPI Bridge >> > [Mon Mar 23 18:43:06 2020] usb 3-2: Manufacturer: JMicron >> > [Mon Mar 23 18:43:06 2020] usb 3-2: SerialNumber: 74D7851513309E5 >> > [Mon Mar 23 18:43:06 2020] usb 3-2: UAS is blacklisted for this device, using usb-storage instead >> > [Mon Mar 23 18:43:06 2020] usb-storage 3-2:1.0: USB Mass Storage device detected >> > [Mon Mar 23 18:43:06 2020] usb-storage 3-2:1.0: Quirks match for vid 357d pid 7788: 4800000 >> > [Mon Mar 23 18:43:06 2020] scsi host6: usb-storage 3-2:1.0 >> > [Mon Mar 23 18:43:07 2020] scsi 6:0:0:0: Direct-Access WDC WD10 JPVT-00A1YT0 0114 PQ: 0 ANSI: 6 >> > [Mon Mar 23 18:43:07 2020] sd 6:0:0:0: Attached scsi generic sg1 type 0 >> > [Mon Mar 23 18:43:07 2020] sd 6:0:0:0: [sdb] Spinning up disk... >> > [Mon Mar 23 18:43:08 2020] ..ready >> > [Mon Mar 23 18:43:09 2020] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) >> > [Mon Mar 23 18:43:09 2020] sd 6:0:0:0: [sdb] Write Protect is off >> > [Mon Mar 23 18:43:09 2020] sd 6:0:0:0: [sdb] Mode Sense: 47 00 10 08 >> > [Mon Mar 23 18:43:09 2020] sd 6:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA >> > [Mon Mar 23 18:43:09 2020] sdb: sdb1 >> > [Mon Mar 23 18:43:09 2020] sd 6:0:0:0: [sdb] Attached SCSI disk >> > [Mon Mar 23 18:43:30 2020] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE >> > [Mon Mar 23 18:43:30 2020] sd 6:0:0:0: [sdb] tag#0 Sense Key : Illegal Request [current] >> > [Mon Mar 23 18:43:30 2020] sd 6:0:0:0: [sdb] tag#0 Add. Sense: Invalid field in cdb >> > [Mon Mar 23 18:43:30 2020] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 08 00 00 08 00 00 00 08 00 >> > [Mon Mar 23 18:43:30 2020] blk_update_request: critical target error, dev sdb, sector 2048 op 0x1:(WRITE) flags 0x20800 phys_seg 1 prio class 0 >> > [Mon Mar 23 18:43:30 2020] Buffer I/O error on dev sdb1, logical block 0, lost sync page write >> > [Mon Mar 23 18:43:30 2020] EXT4-fs (sdb1): I/O error while writing superblock >> > [Mon Mar 23 18:43:30 2020] EXT4-fs (sdb1): mount failed >> > >> > # lsusb >> > Bus 003 Device 008: ID 357d:7788 Sharkoon QuickPort XT >> > >> > >> > Other considerations >> > -------------------- >> > This enclosure works as expected with another drive: I tried with an old >> > Fujitsu 250GB drive and was able to mount the partitions. >> > >> > The WD drive works with a similar enclosure: the Icy Box IB-268U3-B >> > enclosure. It has the exact same vendor id and product id (357d:7788) >> > but a different bcdDevice (2.03). >> > >> > Looking at the dmesg logs I pasted above, I see that the main difference >> > is the driver used: >> > - uas in Linux 5.3; >> > - usb-storage in Linux 5.4, since uas is blacklisted. >> > >> > >> > I believe the uas driver was blacklisted because of an old bug[1] in >> > Fedora. In Linux, the commit that disabled uas is >> > bc3bdb12bbb3492067c8719011576370e959a2e6. >> > >> > I do not really mind not being able to use uas, however I would like to >> > be able to mount my partitions using usb-storage. >> >> It's entirely possible that the blacklisting is not necessary any more. >> After all, it was added four and a half years ago; the kernel has >> improved since then. I guess you're not in a position to test this, >> but maybe Steve Ellis or Takeo Nakayama is...? >> >> Does 5.3 work if you add a similar blacklist entry? >> >> Can you collect usbmon traces showing what happens with both uas and >> usb-storage? Perhaps different sequences of commands get sent to the >> drive with the two drivers. >> >> Alan Stern >> > > > -- > > Steven Ellis > > TECHNICAL PORTFOLIO EVANGELIST - APAC > > APAC PRINCIPAL PRODUCT MANAGER - STORAGE & HCI > > Red Hat Asia Pacific - Auckland NZ > > E: sellis@xxxxxxxxxx M: +64 21 321 673 > > @RedHat Red Hat Red Hat > >
