Skip to contentSkip to conversation

New: UAS keeps resetting disks

Bug 215333 [email protected] 1 participant 1 message Dec 15, 2021 SCSI

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=215333

Bug ID: 215333
Summary: UAS keeps resetting disks
Product: IO/Storage
Version: 2.5
Kernel Version: Any
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: blocking
Priority: P1
Component: SCSI
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Created attachment 300031
--> https://bugzilla.kernel.org/attachment.cgi?id=300031&action=edit
UAS Log from boot

Hi.

Not sure what the benefit of UAS should supposed to be, considering that is never works, besides breaking things. I have had issues with this using specific USB Disks with live installers in the past, and now I spent a whole day debugging boot issues on two servers, caused by UAS on a specific USB/Sata adapter.

https://superuser.com/questions/1693125/boot-loop-with-certain-sata-to-usb-adaptors/1693143#1693143

I have written in detail the issue in the above link along with other details from various testing that I have done. But in general here is the problem.

I had two different types of USB3/Sata adapters. One from Hama that seamed to work and another from DeLock that would cause boot issues due to the fact that UAS kept resetting the disks. I found that adding a quirks to usb-storage module, would stop that adapter from being used by UAS and would make it work properly. I also found that the Hama adapter was already pre-disabled within the usb-storage module, which is why it worked out-of-box. But it also means that neither of the adapters works with UAS. So if nothing works with this, but rather just produces problems for people (There are a ton of these issues across the web), why not remove it altogether. There may be some benefits from UAS (When it works), but considering how much havoc it creates, is it worth it?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.