Hi,
This is just to state that I used the SAS LTO firmware upgrade method
Douglas suggested (1 year ago) and it worked fine, upgrading an HPE
LTO-5 Ultrium 3000 internal SAS tape drive from a .frm / .E file.
Best regards,
--
Jérôme
PS: It took me a while to find a way to get the latest firmw
Hi,
On Thu, 16 Nov 2017 14:42:51 -0500 (EST)
Alan Stern wrote:
> On Wed, 15 Nov 2017, Jérôme Carretero wrote:
>
> > I performed an usbmon capture extract, centered around the event
> > (there was a few hundred MBs written for this to happen):
> >
> > Nov 15
Hi,
On Wed, 15 Nov 2017 18:17:08 -0500
Jérôme Carretero wrote:
> Hi,
>
>
> On Thu, 16 Nov 2017 07:40:08 +0900
> James Bottomley wrote:
>
> > On Wed, 2017-11-15 at 17:02 -0500, Alan Stern wrote:
> > > On Wed, 15 Nov 2017, Jérôme Carretero wrote:
&g
On Wed, 15 Nov 2017 17:02:39 -0500 (EST)
Alan Stern wrote:
> > > - It looks like (haven't tested it yet) the CONFIG_DYNAMIC_DEBUG
> > > isn't used with the USB mass storage debugging infrastructure,
> > > please confirm? If unused, are we interested to have a patch that
> > > would go back to reg
Hi,
On Thu, 16 Nov 2017 07:40:08 +0900
James Bottomley wrote:
> On Wed, 2017-11-15 at 17:02 -0500, Alan Stern wrote:
> > On Wed, 15 Nov 2017, Jérôme Carretero wrote:
> > > > Because with several of these drives / lots of activity /
> > occasional
> > &g
(Adding Tejun Heo who was assigned on still-open bugzilla #93581 which
is about SATA but seems terribly related.)
On Wed, 15 Nov 2017 16:43:14 -0500
Jérôme Carretero wrote:
> Hi Hans,
>
>
> Tests are currently undergoing with drives operating in plain USB mass
> storage class.
rôme
On Mon, 13 Nov 2017 12:38:14 -0500
Jérôme Carretero wrote:
> Hi Hans,
>
> On Mon, 13 Nov 2017 10:04:53 +0100
> Hans de Goede wrote:
>
> > Hi,
> >
> > On 13-11-17 07:14, Jérôme Carretero wrote:
> > > On Mon, 13 Nov 2017 07:01:30 +0300
> > &
Hi Hans,
On Mon, 13 Nov 2017 10:04:53 +0100
Hans de Goede wrote:
> Hi,
>
> On 13-11-17 07:14, Jérôme Carretero wrote:
> > On Mon, 13 Nov 2017 07:01:30 +0300
> > Andrey Astafyev <1...@246060.ru> wrote:
> >
> >> 13.11.2017 00:42, Jérôme Carretero пи
On Mon, 13 Nov 2017 09:16:39 +0300
Andrey Astafyev <1...@246060.ru> wrote:
> 13.11.2017 09:14, Jérôme Carretero пишет:
> > 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=0b
On Mon, 13 Nov 2017 07:01:30 +0300
Andrey Astafyev <1...@246060.ru> 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 s
On Fri, 10 Nov 2017 16:13:44 +0100
Hans de Goede wrote:
> Just like all previous UAS capable Seagate disk enclosures, this
> one needs a US_FL_NO_ATA_1X quirk.
> [...]
> +/* Reported-by: Andrey Astafyev */
Hi Andrey,
I notice that you have an external Seagate SMR drive, I am encountering
some
Hi Ching,
Context: when a drive finally failed in my JBOD array, I discovered that
the whole ARC1880X controller would timeout, disabling access to any drive,
which is kind of sad.
I've performed a firmware upgrade and added back the failing drive to see
what happens with a newer device firmware
12 matches
Mail list logo
