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: Thu, 25 Sep 2014 22:22:04 +0000 [thread overview]
Message-ID: <bug-85101-11613-r7FDruKxyT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-85101-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=85101
--- Comment #6 from linux-ide@crashplan.pro ---
The HP Smart Array P410 still has its issues: sometimes the diagnostics LED
turns amber, other times it works ok.
As a fall back a Marvell controller detects the HP SAS expander card fine:
# lsscsi -g | grep HP
[6:0:0:0] enclosu HP HP SAS EXP Card 2.08 - /dev/sg1
I am not able to figure out a correct sg_write_buffer command. Run from the
directory where the unpacked binary image is stored:
# sg_write_buffer --bpw=4096 -v --in=PUF21000.bin /dev/sg1
tried to read 8388608 bytes from PUF21000.bin, got 1509632 bytes
will write 1509632 bytes
sending write buffer, mode=0x0, mspec=0, id=0, offset=0, len=4096
Write buffer cmd: 3b 00 00 00 00 00 00 10 00 00
write buffer: Fixed format, current; Sense key: Illegal Request
Additional sense: Invalid field in cdb
Write buffer failed: Illegal request sense key, apart from Invalid opcode
Any suggestions for the correct sg_write_buffer statement for writing to an HP
SAS expander card?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-09-25 22: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 ` [Bug 85101] " bugzilla-daemon
2014-09-24 21:33 ` 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 [this message]
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-r7FDruKxyT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.