From: Eric Mudama <edmudama@gmail.com>
To: jklaas <jklaas@comcast.net>
Cc: linux-scsi@vger.kernel.org
Subject: Re: firmware help
Date: Fri, 10 Sep 2004 10:20:57 -0600 [thread overview]
Message-ID: <311601c9040910092061681de5@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0409081347100.27903@shenandoah>
On Wed, 8 Sep 2004 14:51:42 -0400 (EDT), jklaas <jklaas@comcast.net> wrote:
> From everything I've read about firmware on SCSI drives, it appears to be
> impossible to extract the firmware from a drive. I was hoping that there
> was some sort of SCSI programming judo to make this drive divulge this
> information. Would I be better off trying to extract the firmware
> directly from the flash chip somehow?
>
> I was hoping to find some firmware for some EMC Symmetrix/Seagate drives.
> These are Elite 47 drives labelled with Seagate model #ST446452W, and
> a "non-Seagate" part number 9K7001-021. These drives were apparently only
> ever sold to EMC and were designed by Seagate for EMC specifically. (Is
> this true of all the Elite drives?)
>
> Seagate said "The part number you provided for us indicates that the drive
> is OEM. Please contact your vendor to receive the proper firmware
> upgrade." Unfortunately, EMCs support site is impenetrable.
>
> Thank you for your help.
I'm sure there is hidden judo to extract that data, but those who know
it aren't allowed to reveal it because we either 1) work for a drive
manufacturer and would get fired or 2) work for a data recovery
company and make our living with that judo.
What exactly do you hope to accomplish with a binary firmware image
anyway? The firmware is liable to be a binary image from a custom
architecture... which'd be a LOT of work to try to decode into
something meaningful...
--eric
next prev parent reply other threads:[~2004-09-10 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-08 18:51 firmware help jklaas
2004-09-10 16:20 ` Eric Mudama [this message]
2004-09-10 16:29 ` Nathan Bryant
2004-09-10 16:32 ` Eric Mudama
2004-09-10 16:50 ` jklaas
2004-09-11 13:14 ` Douglas Gilbert
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=311601c9040910092061681de5@mail.gmail.com \
--to=edmudama@gmail.com \
--cc=jklaas@comcast.net \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).