From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 85101] hpsa + P410 does not show connected HP SAS port expanders
Date: Wed, 24 Sep 2014 18:22:25 +0000 [thread overview]
Message-ID: <bug-85101-11613-jK5RZ9LkvH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85101-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85101
Robert Elliott <elliott@hp.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |elliott@hp.com
--- Comment #1 from Robert Elliott <elliott@hp.com> ---
Smart Array P410 is a RAID controller that does not expose anything about the
SAS fabric (expanders or physical drives) to the OS; it just presents logical
drives. You need to use HP management tools to download firmware to expanders
and drives behind the controller.
If you attach the expander to an HBA, then you can use sg_write_buffer to
download microcode. Version 1.39 added a --bpw option to download in small
chunks - an expander might require a small chunk size like 4 KiB (see
http://sg.danny.cz/sg for the latest sg3_utils code).
Although they sound like DOS programs, .scexe files from HP are really linux
executable scripts that you can view in a text editor (at least the first
part). You can do this to extract the files:
mkdir tmp
./CPxyzzy.scexe --unpack=tmp
One of those is the binary image that can be sent with sg_write_buffer.
BTW, use lsscsi -g to see the /dev/sgNN paths for all the devices presented by
the LLD, including expanders.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-09-24 18:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:46 [Bug 85101] New: hpsa + P410 does not show connected HP SAS port expanders bugzilla-daemon
2014-09-24 18:22 ` bugzilla-daemon [this message]
2014-09-24 21:33 ` [Bug 85101] " bugzilla-daemon
2014-09-24 22:32 ` bugzilla-daemon
2014-09-25 10:48 ` bugzilla-daemon
2014-09-25 10:49 ` bugzilla-daemon
2014-09-25 14:05 ` bugzilla-daemon
2014-09-25 22:22 ` bugzilla-daemon
2014-09-25 22:35 ` bugzilla-daemon
2014-09-25 22:42 ` bugzilla-daemon
2014-10-01 21:59 ` bugzilla-daemon
2023-11-08 9:42 ` bugzilla-daemon
2025-09-18 9:57 ` bugzilla-daemon
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=bug-85101-11613-jK5RZ9LkvH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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