On 9/27/21 5:04 PM, Alan Stern wrote:
On Sun, Sep 26, 2021 at 08:14:46PM +0200, Tobias Jakobi wrote:
Hello Alan,
On 9/21/21 6:42 PM, Alan Stern wrote:
On Tue, Sep 21, 2021 at 06:06:45PM +0200, Tobias Jakobi wrote:
Hi Alan,
sorry but your analysis of the log is wrong. Nothing was disconnected or
unplugged when the device behaves this way. The enclosure is connected to
the power the entire time, and the same applies to the physical USB
connection to my system.
That may be so, but if it is then the log extract you included with the
patch is very misleading. For instance, you didn't include any part of
the log before and leading up to the line saying "usb 2-1.2: USB
disconnect, device number 4". Thus there is no way for the reader to
tell what caused this event, whether it was a physical unplug or not.
I included the part of the kernel log which shows how the issue manifests
itself. Do you think I'm so stupid as to believe I could prevent a physical
unplug of the enclosure by blacklisting UAS? Really, this is getting
ridiculous...
No, I don't believe that. However, I do believe you are so stupid as
to post a patch with a description that does not justify it and
includes a lot of irrelevant details. (Hey, you brought up the issue
of how stupid you are! :-)
To make things very clear: This happens in under five minutes after having
powered up the enclosure and starting a file transfer to the installed RAID.
After blacklisting UASP the enclosure works perfectly fine for hours. I hope
this clears things up.
You didn't answer my question about using NO_ATA_1X instead of
IGNORE_UAS. This is a perfect example of one of the dangers of
top-posting -- it makes it far too easy for people to miss important
points in the email they are replying to. (Hint: Don't top-post!)
I did not answer this question, because I didn't have the answer to it yet.
I have tested your suggestion today, but sadly I'm running into the same
type of problem with NO_ATA_1X. You can find the complete kernel log here:
https://www.math.uni-bielefeld.de/~tjakobi/archive/dmesg_VL817.log
Good, thank you. Unfortunately the log doesn't include any smoking
guns pointing to an underlying cause.
I'm open to suggestions regarding identifying the cause. As you might
guess, I'm also not happy that I had to disable UAS for the enclosure --
in particular since I selected this particular product because it was
advertised with having support.
The RAID1 is broken after such an event.
With best wishes,
Tobias
Alan Stern
With best wishes,
Tobias
On 9/21/21 5:13 PM, Alan Stern wrote:
On Tue, Sep 21, 2021 at 12:17:52PM +0200, Tobias Jakobi wrote:
The VL817 is used in the RaidSonic Icy Box IB-3740-C31 enclosure. The enclosure
is advertised as having UASP support, but appears to have problems with 4Kn
drives (test was done with two Seagate Exos X, 12TB).
Disable UAS for the VL817 as it behaves highly unstable:
I still have to wonder if the enclosure works okay with other types of
disk drive. And if it doesn't, why don't these errors show up on
Windows systems? Or on other VIA enclosures?
I only experienced this after installing the two 4Kn drives, never with
the two 512e drives that were installed first. My guess is that 4Kn
drives are still rare and if they're used, then natively attached to a
SATA port. I don't have any Windows system here to test this, and even
if, I wouldn't know how to assemble the RAID1 there anyway.
That's why I'm cautious about accepting this patch. I don't want to
slow down unnecessarily a bunch of USB disks that could work just fine
at the higher UAS transfer rates.
I understand. If that's the case, I'm just going to continue to keep the
patch in my local kernel tree.
By the way, does the enclosure have its own power source, or does it
rely entirely on power provided over the USB cable? Note that UAS can
use more power than the older mass-storage protocols, because it queues
more operations in rapid succession (which is also why it runs faster).
This is the enclosure:
https://icybox.de/product.php?id=155
It has a external power supply (quite a bulky one) and it does not work
without it. So it doesn't draw anything (significant) from the USB
cable. I first also suspected this to be a power supply related problem,
but I discarded that idea since the whole thing works as MSC. I can't
imagine the power draw to be so much different for UAS, but maybe I'm
just naive there.
With best wishes,
Tobias
Alan Stern
