Re: Lacie Rugged USB3-FW does not work with UAS

Julian Sikorski
2021-07-17T08:28:28Z

Am 09.09.19 um 18:18 schrieb Julian Sikorski:
> W dniu 09.09.2019 o 14:45, Oliver Neukum pisze:
>> Am Mittwoch, den 04.09.2019, 19:10 +0200 schrieb Julian Sikorski:
>>>
>>>
>>> Moreover, does this matter that the two Read Capacity errors only appear
>>> after the device is disconnected?
>>
>> Hi,
>>
>> yes it does. However, it didn't in the first log I looked at.
>> Could you check whether the command the failure happens on
>> is constant? That is, test a few times and look for differences.
>>
>>     Regards
>>         Oliver
>>
> Hello,
>
> I can check again, but Idid at the old log again, the errors also
> happened after disconnect with both logs I shared earlier - with the
> first one there were some I/O errors in between:
>
> [16216.299763] usb 6-3.4.2: USB disconnect, device number 4
> [16216.350027] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350031] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350066] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350073] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350093] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350095] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350103] ldm_validate_partition_table(): Disk read failed.
> [16216.350121] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350123] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350143] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350145] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350167] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350169] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350189] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350191] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350199] Dev sdb: unable to read RDB block 0
> [16216.350215] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350217] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350231] print_req_error: I/O error, dev sdb, sector 0 flags 0
> [16216.350233] Buffer I/O error on dev sdb, logical block 0, async page
> read
> [16216.350239]  sdb: unable to read partition table
> [16216.514973] sd 12:0:0:0: [sdb] Read Capacity(16) failed: Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [16216.514977] sd 12:0:0:0: [sdb] Sense not available.
> [16216.634949] sd 12:0:0:0: [sdb] Read Capacity(10) failed: Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
>
> and
>
> [  431.853505] usb 2-4: USB disconnect, device number 3
> [  431.903459] sd 12:0:0:0: [sdb] Optimal transfer size 33553920 bytes
> [  432.064456] sd 12:0:0:0: [sdb] Read Capacity(16) failed: Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
> [  432.064459] sd 12:0:0:0: [sdb] Sense not available.
> [  432.184595] sd 12:0:0:0: [sdb] Read Capacity(10) failed: Result:
> hostbyte=DID_ERROR driverbyte=DRIVER_OK
>
> Best regards,
> Julian

Hi all,

apologies for necro-ing this thread. I have just tried this drive with
my new laptop (Asus ZenBook UM425IA) and the same quirk was needed to
get the drive to work:
options usb-storage quirks=059f:1061:u

Should we still try to get uas working with this drive or should I send
a patch hardcoding a quirk? I am on 5.13.2-300.fc34.x86_64 kernel now.
Thanks for the feedback in advance.

Best regards,
Julian