Hi,
On 13-11-17 07:14, Jérôme Carretero wrote:
On Mon, 13 Nov 2017 07:01:30 +0300
Andrey Astafyev <1@xxxxxxxxx> wrote:
13.11.2017 00:42, Jérôme Carretero пишет:
Nov 12 16:20:59 Bidule kernel: sd 22:0:0:0: [sdaa] tag#2
uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
[...]
Do you see such things?
Hi, I've seen dmesg output like this so I've added my device to
quirks list like any other Seagate USB drive.
Hi Andrey, Hans,
For my devices, adding US_FL_NO_ATA_1X to unusual_uas.h didn't
change anything, and while adding US_FL_IGNORE_UAS (using
quirks=0bc2:ab34:u,0bc2:ab38:u) there are still device resets,
but they cause shorter hangs in system activity (~1 second when
UAS was more like ~20).
The errors you are seeing are write errors. If you're seeing these
errors with both the usb-storage and uas drivers then there likely
is something wrong with your setup / hardware.
Does the drive in question use an external power-supply or is it
USB bus-powered? If it is the latter then that is likely the problem.
Anyways things I would check and try to swap are both the cable
used, the power-supply used (if any), the USB-port used as well
as trying the disk on a completely different computer.
I've the feeling something is busted with your hardware, it
could be the disk itself. Did you mention that this was the first
release of a new higher capacity ? Those often have some kinks
which are worked out in later revisions.
Regards,
Hans
