public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Seagate Barracuda 7200.11 ST31500341AS fw SD17
@ 2009-06-02 10:58 Markus
       [not found] ` <4A250B6A.6030904@grupopie.com>
  2009-06-03  4:10 ` Robert Hancock
  0 siblings, 2 replies; 9+ messages in thread
From: Markus @ 2009-06-02 10:58 UTC (permalink / raw)
  To: lkml

Hello!

I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
use the firmware SD17.
They time out at the flush write cache and sometimes on the identify 
command.
I know that sounds suspicious so I wrote to seagate but they told me my 
drives are ok. (Although I dont think so.)

This drive+fw is blacklisted in the kernel, but there is no firmware 
upgrade for these drives. (Only very few serial numbers are able to 
upgrade.)

Now I want to know after what period of the time the kernel timeouts at 
these commands!? And if this timeout can be increased (manually, small 
patch for the kernel) and the min/max/avg time could somehow be 
messured. Every timeout kicks the drives off the raid, so I disabled 
the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a bad 
workaround.

Its a amd64 system with the 2.6.29.4 on an AM3 board with AMDs 790GX + 
SB750 Chipsets running in ahci mode.

Thanks for your time and support!

Markus

PS: Please CC me!

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
       [not found] ` <4A250B6A.6030904@grupopie.com>
@ 2009-06-02 11:37   ` Markus
  2009-06-02 12:14     ` Kay Diederichs
  0 siblings, 1 reply; 9+ messages in thread
From: Markus @ 2009-06-02 11:37 UTC (permalink / raw)
  To: lkml

Rui Santos wrote:
>> I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
>> use the firmware SD17.
> Seagate recommends firmware SD1A for that HD.
> However, I do not know if it will solve your problem. Jut try it...

>> This drive+fw is blacklisted in the kernel, but there is no firmware 
>> upgrade for these drives. (Only very few serial numbers are able to 
>> upgrade.)

I cant upgrade the firmware because the flash-utility will abort due 
to "not affected serial number". I tried SD1B, the very newest version.
Cant find the SD1A for my drives.

Markus

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-02 11:37   ` Markus
@ 2009-06-02 12:14     ` Kay Diederichs
  2009-06-02 12:38       ` Markus
  0 siblings, 1 reply; 9+ messages in thread
From: Kay Diederichs @ 2009-06-02 12:14 UTC (permalink / raw)
  To: Markus; +Cc: lkml

Markus schrieb:
> Rui Santos wrote:
>>> I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
>>> use the firmware SD17.
>> Seagate recommends firmware SD1A for that HD.
>> However, I do not know if it will solve your problem. Jut try it...
> 
>>> This drive+fw is blacklisted in the kernel, but there is no firmware 
>>> upgrade for these drives. (Only very few serial numbers are able to 
>>> upgrade.)
> 
> I cant upgrade the firmware because the flash-utility will abort due 
> to "not affected serial number". I tried SD1B, the very newest version.
> Cant find the SD1A for my drives.
> 
> Markus

I think you might have tried the wrong firmware file.
ST31500341AS needs 
http://www.seagate.com/staticfiles/support/downloads/firmware/Brinks-4D8H-SD1B.ISO

HTH,

Kay


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-02 12:14     ` Kay Diederichs
@ 2009-06-02 12:38       ` Markus
  2009-06-02 14:03         ` Krzysztof Halasa
  0 siblings, 1 reply; 9+ messages in thread
From: Markus @ 2009-06-02 12:38 UTC (permalink / raw)
  To: linux-kernel; +Cc: Kay Diederichs

Kay Diederichs wrote:
> Markus schrieb:
> > Rui Santos wrote:
> >>> I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. 
They 
> >>> use the firmware SD17.
> >> Seagate recommends firmware SD1A for that HD.
> >> However, I do not know if it will solve your problem. Jut try it...
> > 
> >>> This drive+fw is blacklisted in the kernel, but there is no 
firmware 
> >>> upgrade for these drives. (Only very few serial numbers are able 
to 
> >>> upgrade.)
> > 
> > I cant upgrade the firmware because the flash-utility will abort due 
> > to "not affected serial number". I tried SD1B, the very newest 
version.
> > Cant find the SD1A for my drives.
> > 
> > Markus
> 
> I think you might have tried the wrong firmware file.
> ST31500341AS needs 
> 
http://www.seagate.com/staticfiles/support/downloads/firmware/Brinks-4D8H-SD1B.ISO

I tried that one (compared md5sum). It does not work. It only works 
for "ST31500341AS,  9JU138-300 or -336, SD15 through SD1A ONLY!"
So the utility fails and says the specific model could not be found.

Markus

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-02 12:38       ` Markus
@ 2009-06-02 14:03         ` Krzysztof Halasa
  2009-06-03 10:14           ` Markus
  0 siblings, 1 reply; 9+ messages in thread
From: Krzysztof Halasa @ 2009-06-02 14:03 UTC (permalink / raw)
  To: Markus; +Cc: linux-kernel, Kay Diederichs

Markus <M4rkusXXL@web.de> writes:

> http://www.seagate.com/staticfiles/support/downloads/firmware/Brinks-4D8H-SD1B.ISO
>
> I tried that one (compared md5sum). It does not work. It only works 
> for "ST31500341AS,  9JU138-300 or -336, SD15 through SD1A ONLY!"

Did you try to contact them?
-- 
Krzysztof Halasa

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-02 10:58 Seagate Barracuda 7200.11 ST31500341AS fw SD17 Markus
       [not found] ` <4A250B6A.6030904@grupopie.com>
@ 2009-06-03  4:10 ` Robert Hancock
  2009-06-03 10:16   ` Markus
  1 sibling, 1 reply; 9+ messages in thread
From: Robert Hancock @ 2009-06-03  4:10 UTC (permalink / raw)
  To: Markus; +Cc: lkml

Markus wrote:
> Hello!
> 
> I have some Seagate Barracuda 7200.11 ST31500341AS 1.5TB drives. They 
> use the firmware SD17.
> They time out at the flush write cache and sometimes on the identify 
> command.
> I know that sounds suspicious so I wrote to seagate but they told me my 
> drives are ok. (Although I dont think so.)
> 
> This drive+fw is blacklisted in the kernel, but there is no firmware 
> upgrade for these drives. (Only very few serial numbers are able to 
> upgrade.)
> 
> Now I want to know after what period of the time the kernel timeouts at 
> these commands!? And if this timeout can be increased (manually, small 
> patch for the kernel) and the min/max/avg time could somehow be 
> messured. Every timeout kicks the drives off the raid, so I disabled 
> the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a bad 
> workaround.

I believe the timeout for commands like these is usually 30 seconds. 
Normally if it doesn't respond after that length of time, it never will. 
Even if it eventually did, I don't think you'd be happy with disk access 
delays of over 30 seconds..

> 
> Its a amd64 system with the 2.6.29.4 on an AM3 board with AMDs 790GX + 
> SB750 Chipsets running in ahci mode.
> 
> Thanks for your time and support!
> 
> Markus
> 
> PS: Please CC me!


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-02 14:03         ` Krzysztof Halasa
@ 2009-06-03 10:14           ` Markus
  2009-06-03 15:38             ` Krzysztof Halasa
  0 siblings, 1 reply; 9+ messages in thread
From: Markus @ 2009-06-03 10:14 UTC (permalink / raw)
  To: linux-kernel

Krzysztof Halasa wrote:
> Markus <M4rkusXXL@web.de> writes:
> 
> > 
http://www.seagate.com/staticfiles/support/downloads/firmware/Brinks-4D8H-SD1B.ISO
> >
> > I tried that one (compared md5sum). It does not work. It only works 
> > for "ST31500341AS,  9JU138-300 or -336, SD15 through SD1A ONLY!"
> 
> Did you try to contact them?

Of course I did. They told me, my drives are not affected and drives 
with "good" serial numbers will not be upgraded.
And they now told me I have OEM drives (???) which they do not provide 
firmware upgrades for, although my drives are ok. I dont understand 
those support-people.

Markus

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-03  4:10 ` Robert Hancock
@ 2009-06-03 10:16   ` Markus
  0 siblings, 0 replies; 9+ messages in thread
From: Markus @ 2009-06-03 10:16 UTC (permalink / raw)
  To: linux-kernel; +Cc: Robert Hancock

Robert Hancock wrote:
> Markus wrote:
> > Now I want to know after what period of the time the kernel timeouts 
at 
> > these commands!? And if this timeout can be increased (manually, 
small 
> > patch for the kernel) and the min/max/avg time could somehow be 
> > messured. Every timeout kicks the drives off the raid, so I disabled 
> > the write cache (hdparm -W0 /dev/sdx) but thats no solution, just a 
bad 
> > workaround.
> 
> I believe the timeout for commands like these is usually 30 seconds. 
> Normally if it doesn't respond after that length of time, it never 
will. 
> Even if it eventually did, I don't think you'd be happy with disk 
access 
> delays of over 30 seconds..

Ok thats definitly bad. Will reask at the support...

Markus

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
  2009-06-03 10:14           ` Markus
@ 2009-06-03 15:38             ` Krzysztof Halasa
  0 siblings, 0 replies; 9+ messages in thread
From: Krzysztof Halasa @ 2009-06-03 15:38 UTC (permalink / raw)
  To: Markus; +Cc: linux-kernel

Markus <M4rkusXXL@web.de> writes:

>> > I tried that one (compared md5sum). It does not work. It only works 
>> > for "ST31500341AS,  9JU138-300 or -336, SD15 through SD1A ONLY!"
>
> Of course I did. They told me, my drives are not affected and drives 
> with "good" serial numbers will not be upgraded.
> And they now told me I have OEM drives (???) which they do not provide 
> firmware upgrades for, although my drives are ok. I dont understand 
> those support-people.

Well, they might be right. Or the drives may be affected but they don't
support OEM versions anyway and may not know.

Obviously one could try updating anyway (I'm sure a simple hack in
version/SN checking routine would do). It may be risky.
You should, in theory, contact the OEM partner, not the manufacturer.
Could be hard.

OTOH I think the update fixes unrelated problem (a drives failing to
start), that would need checking.
-- 
Krzysztof Halasa

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2009-06-03 15:38 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-02 10:58 Seagate Barracuda 7200.11 ST31500341AS fw SD17 Markus
     [not found] ` <4A250B6A.6030904@grupopie.com>
2009-06-02 11:37   ` Markus
2009-06-02 12:14     ` Kay Diederichs
2009-06-02 12:38       ` Markus
2009-06-02 14:03         ` Krzysztof Halasa
2009-06-03 10:14           ` Markus
2009-06-03 15:38             ` Krzysztof Halasa
2009-06-03  4:10 ` Robert Hancock
2009-06-03 10:16   ` Markus

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox