From: Krzysztof Halasa <khc@pm.waw.pl>
To: Markus <M4rkusXXL@web.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Seagate Barracuda 7200.11 ST31500341AS fw SD17
Date: Wed, 03 Jun 2009 17:38:30 +0200 [thread overview]
Message-ID: <m3ab4pba4p.fsf@intrepid.localdomain> (raw)
In-Reply-To: <200906031214.39610.M4rkusXXL@web.de> (Markus's message of "Wed\, 3 Jun 2009 12\:14\:39 +0200")
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
next prev parent reply other threads:[~2009-06-03 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2009-06-03 4:10 ` Robert Hancock
2009-06-03 10:16 ` Markus
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=m3ab4pba4p.fsf@intrepid.localdomain \
--to=khc@pm.waw.pl \
--cc=M4rkusXXL@web.de \
--cc=linux-kernel@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