From: "Augustine Ortiz, Jr." <aortizjr@lanl.gov>
To: linux-raid@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: RE: Getting HD Serial Numbers in RAID
Date: Wed, 01 Sep 2004 08:33:45 -0600 [thread overview]
Message-ID: <1094049224.31782.11.camel@afgar.lanl.gov> (raw)
In-Reply-To: <60807403EABEB443939A5A7AA8A7458B0B4445@otce2k01.adaptec.com>
Hi...
Thank you for the very informative response. I was afraid that the
passthrough was just not supported.
Would it be possible for me to get the driver (OEM) that can report this
information (SRB Passthrough)? Or can I get the pieces to implement the
passthrough myself.
If you know anything about getting that info in Win32 that would help
greatly also, since I am in the same boat in that OS as well.
Thanks!
Augustine
On Wed, 2004-09-01 at 06:18, Salyzyn, Mark wrote:
> The aacraid module only reports the logicals and none-DASD devices to
> the scsi layer. There is no direct communication to any DASD devices.
>
> I have toyed with exporting the components of the arrays, but to please
> the (Security, RAID & OEM) gohds I need to ensure that R/W requests are
> not honored. I will look into producing a patch to MarkH for this once
> the current set (about a dozen patches pending) has finished bubbling
> through his hands ...
>
> The current mechanism for exporting this component information is via
> the applications, there is an SRB passthrough command that is in our OEM
> variant of the driver used for such a purpose. The SRB passthrough was
> rejected by the community and is not in the kernels.org driver and will
> remain a legacy requirement by the OEMs.
>
> Sincerely -- Mark Salyzyn
>
> -----Original Message-----
> From: linux-raid-owner@vger.kernel.org
> [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Augustine Ortiz,
> Jr.
> Sent: Tuesday, August 31, 2004 5:11 PM
> To: linux-raid@vger.kernel.org; linux-scsi@vger.kernel.org
> Subject: RE: Getting HD Serial Numbers in RAID
>
> Usually, most hardware RAID stuff does give software. However since this
> one (AACRAID/PERC) is such a common controller, this manufacturer didn't
> include it. We do have some for other systems, but they are in Windows,
> and I can't seem to figure out how to get the serial numbers through
> that either.
>
> Interestingly, if you have the arrays broken, you can pull the serial
> numbers just fine.
>
> Some RAID cards (ie. DAC90 chipset) will report all the disks when the
> kernel module is loaded. I figured I could just sorta re-work that stuff
> and see if I could probe it.
>
> I am having some trouble with the AACRAID module though. It looks like
> it grabs the info, but I can't tell if it does it when the drives are
> actually RAIDed.
>
> Thank you for the info, I will see if I can get it via the SMART stuff.
> I will post if I have any luck.
>
> Thanks!
>
> Augustine
>
>
> > From:
> > Derek Vadala <derek@cynicism.com>
> > You could try smartctl, but I don't know what luck you'll have
> > accessing
> > the raw devices if they are behind a hardware controller.
> >
> > http://smartmontools.sourceforge.net/
> > http://www.linuxjournal.com/article.php?sid=6983
> >
>
>
> > hddtemp will get you more info on the disk ... not sure if it works
> > on aacraid/perc etc
> >
> > c ya
> > alvin
>
>
> On Tue, 2004-08-31 at 14:36, Guy wrote:
> > When I have used hardware RAID, the vender supplies software that will
> do
> > what you want. But it is tied to the vender's hardware, not general.
> >
> > Guy
> >
> > -----Original Message-----
> > From: linux-raid-owner@vger.kernel.org
> > [mailto:linux-raid-owner@vger.kernel.org] On Behalf Of Augustine
> Ortiz, Jr.
> > Sent: Tuesday, August 31, 2004 3:45 PM
> > To: linux-raid@vger.kernel.org; linux-scsi@vger.kernel.org
> > Subject: Getting HD Serial Numbers in RAID
> >
> > Hi...
> >
> > I have been working on getting serial numbers electronically off of
> hard
> > drives for various reasons.
> >
> > I have been successful with IDE and most SCSI drives (using hdparm and
> > scsiinfo). However I am running into trouble with ones that are on
> > AACRAID/PERC3 adaptors and actually in a RAID array.
> >
> > The only serial number I can seem to grab is the one for the entire
> > volume which is just assigned.
> >
> > Are there any tools available to get the serial number off the drives
> in
> > the array? Or can I get some pointers on writing such a tool?
> >
> > Thank you.
> >
> > Augustine
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-raid"
> in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-09-01 14:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 12:18 Getting HD Serial Numbers in RAID Salyzyn, Mark
2004-09-01 14:33 ` Augustine Ortiz, Jr. [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 19:45 Augustine Ortiz, Jr.
2004-08-31 20:14 ` Alvin Oga
2004-08-31 20:26 ` Derek Vadala
2004-08-31 20:36 ` Guy
2004-08-31 21:10 ` Augustine Ortiz, Jr.
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=1094049224.31782.11.camel@afgar.lanl.gov \
--to=aortizjr@lanl.gov \
--cc=linux-raid@vger.kernel.org \
--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