Linux-USB Archive on lore.kernel.org
 help / color / Atom feed
From: Julian Sikorski <belegdol@gmail.com>
To: Oliver Neukum <oneukum@suse.com>,
	Nathan Stratton Treadway <vgerlists@nathanst.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: Lacie Rugged USB3-FW does not work with UAS
Date: Mon, 9 Sep 2019 18:18:08 +0200
Message-ID: <ed7f6cd6-b787-4876-2462-7977d69c8d4b@gmail.com> (raw)
In-Reply-To: <1568033125.365.17.camel@suse.com>

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

      reply index

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-23 13:31 Julian Sikorski
2019-08-23 13:39 ` Oliver Neukum
2019-08-23 13:43   ` Julian Sikorski
2019-08-23 14:21     ` Julian Sikorski
2019-08-23 21:23       ` Oliver Neukum
2019-08-24  7:08         ` Julian Sikorski
2019-08-29 18:33           ` Julian Sikorski
2019-09-02 11:42             ` Oliver Neukum
2019-09-02 20:10               ` Julian Sikorski
2019-09-04 15:58                 ` Nathan Stratton Treadway
2019-09-04 17:10                   ` Julian Sikorski
2019-09-09 12:45                     ` Oliver Neukum
2019-09-09 16:18                       ` Julian Sikorski [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ed7f6cd6-b787-4876-2462-7977d69c8d4b@gmail.com \
    --to=belegdol@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=oneukum@suse.com \
    --cc=vgerlists@nathanst.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-USB Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-usb/0 linux-usb/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-usb linux-usb/ https://lore.kernel.org/linux-usb \
		linux-usb@vger.kernel.org
	public-inbox-index linux-usb

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-usb


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git