From: Andrei Kartashev <a.kartashev@yadro.com>
To: James Feist <james.feist@linux.intel.com>,
Openbmc <openbmc@lists.ozlabs.org>
Subject: Re: Storage inventory on x86
Date: Fri, 11 Sep 2020 20:18:09 +0300 [thread overview]
Message-ID: <88000ada402164b69fb8e1b3b96942ecd4a914bc.camel@yadro.com> (raw)
In-Reply-To: <dc297f57-9fb9-0c10-93fa-31db32cb48db@linux.intel.com>
Aha, that is how it works!
Thank you =)
Just curious, is it some special disks with FRU or there is standard
for that? I believe, there is no smbus in SATA interface =)
On Fri, 2020-09-11 at 08:55 -0700, James Feist wrote:
> On 9/11/2020 2:19 AM, Andrei Kartashev wrote:
> > Hi,
> >
> > The question is mainly for Intel guys:
> > Is there some universal way to build inventory of storage devices
> > (SATA/SAS/NVMe)?
> > I found that on wolfpass there is hsbp-manager who responsible for
> > storage inventory, but if I get it right, there is CPLD on that
> > backplane, which somehow communicate with drives and can get the
> > basic
> > information about (model, serial, etc). Can anyone point me what
> > should
> > we have in our system to implement something like this?
>
> For model serial etc if the drives support a FRU then FRU device
> should
> be able to discover them assuming an smbus connection. Otherwise the
> CPLD on the HSBP that we have supports presence, so we can identify
> a
> drive is there, but not what model. I believe that's all we're
> supporting currently.
>
> > I guess, storage devices are not handled by smbios-mdr daemon,
> > because
> > of hotswap requirement, and not handled by PECI, because of PECI
> > have
> > no such commands. Is there any other ways to get drive inventory
> > (including RAID)?
> >
next prev parent reply other threads:[~2020-09-11 17:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 17:46 OpenBMC Learning Series Sai Dasari
2020-08-22 5:48 ` Sai Dasari
2020-08-26 19:11 ` Sai Dasari
2020-08-26 19:19 ` Vijay Khemka
2020-08-26 19:22 ` Sai Dasari
2020-08-26 19:25 ` Vijay Khemka
2020-08-27 21:10 ` Sai Dasari
2020-08-28 16:14 ` Vijay Khemka
2020-09-02 16:56 ` Sai Dasari
2020-09-03 22:16 ` Sai Dasari
2020-09-09 16:58 ` Sai Dasari
2020-09-10 18:33 ` James Feist
2020-09-10 20:49 ` Andrei Kartashev
2020-09-11 15:52 ` James Feist
2020-09-11 17:20 ` Andrei Kartashev
2020-09-11 9:19 ` Storage inventory on x86 Andrei Kartashev
2020-09-11 15:55 ` James Feist
2020-09-11 17:18 ` Andrei Kartashev [this message]
2020-09-14 16:24 ` James Feist
2020-09-10 19:49 ` OpenBMC Learning Series Sai Dasari
2020-09-16 7:36 ` Sai Dasari
2020-09-23 16:10 ` Sai Dasari
2020-09-30 17:00 ` Sai Dasari
2020-10-07 15:53 ` Sai Dasari
2020-10-14 6:48 ` Sai Dasari
2020-10-21 2:07 ` Sai Dasari
2020-10-28 16:39 ` Sai Dasari
2020-11-04 17:33 ` Sai Dasari
2020-11-05 11:37 ` Thomaiyar, Richard Marian
2020-11-05 16:58 ` Sai Dasari
2020-11-11 17:43 ` Sai Dasari
2020-12-16 17:26 ` Sai Dasari
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=88000ada402164b69fb8e1b3b96942ecd4a914bc.camel@yadro.com \
--to=a.kartashev@yadro.com \
--cc=james.feist@linux.intel.com \
--cc=openbmc@lists.ozlabs.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).