public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Alban Browaeys <alban.browaeys@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: add NO_REPORT_LUNS quirk for at least a few Seagate external drives to fix smartctl with uas
Date: Tue, 11 Jun 2024 08:08:46 +0200	[thread overview]
Message-ID: <2024061133-exclaim-recovery-3a59@gregkh> (raw)
In-Reply-To: <9791b3eee4fc52b45f1ea9b9724bf977bf5c38d4.camel@gmail.com>

On Mon, Jun 10, 2024 at 09:25:54PM +0200, Alban Browaeys wrote:
> I found that for "smartctl" to work on my two Seagate Expansion
> external USB3  I had to add the "j" usb-storage quirks ie
> "US_FL_NO_REPORT_LUNS".
> (They are years apart).
> 
> 
> 
> Bus 002 Device 008: ID 0bc2:231a Seagate RSS LLC Expansion Portable
> Bus 002 Device 007: ID 0bc2:2037 Seagate RSS LLC Expansion HDD
> 
> 
> Could these be added to drivers/usb/storage/unusual_uas.h
> with the "US_FL_NO_REPORT_LUNS" quirk, after the existing
> "UNUSUAL_DEV(0x0bc2, 0x331a, 0x0000, 0x9999," for the Seagate
> "Expansion Desk"?

Sure, want to send a patch for this?

thanks,

greg k-h

  reply	other threads:[~2024-06-11  6:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-10 19:25 add NO_REPORT_LUNS quirk for at least a few Seagate external drives to fix smartctl with uas Alban Browaeys
2024-06-11  6:08 ` Greg KH [this message]
2024-06-11  8:21 ` Oliver Neukum
2024-06-12  1:39   ` Alban Browaeys
2024-06-12 15:13     ` Alban Browaeys
2024-06-14  0:18       ` Alban Browaeys
2024-06-14  1:20         ` Remove NO_ATA_1X quirk for at least a few Seagate external drives to fix smartctl with uas ? Alban Browaeys

Reply instructions:

You may reply publicly 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=2024061133-exclaim-recovery-3a59@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=alban.browaeys@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox