From: Joshua Schmidlkofer <joshua@imrlive.com>
To: "Ju, Seokmann" <Seokmann.Ju@lsi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-scsi@vger.kernel.org,
Joshua Schmidlkofer <jms@dev.imr-net.com>,
Mike Montagne <mike@opsisarch.com>
Subject: Re: Recurring MegaRAID SCSI Errors
Date: Fri, 20 Oct 2006 06:53:18 -0700 [thread overview]
Message-ID: <4538D4CE.5040607@imr-net.com> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261932E3F9@NAMAIL3.ad.lsil.com>
Ju, Seokmann wrote:
> Hi,
>
>> [17333187.152000] megaraid: aborting-6172714 cmd=2a <c=2 t=1 l=0>
>> [17333187.152000] megaraid abort: 6172714:124[255:129], fw owner
>> [17333187.152000] megaraid: 15 outstanding commands. Max wait 300 sec
>> [17333187.152000] megaraid mbox: Wait for 15 commands to complete:300
>> [17333192.172000] megaraid mbox: Wait for 10 commands to complete:295
>> [17333197.192000] megaraid mbox: Wait for 3 commands to complete:290
>> [17333199.200000] megaraid mbox: reset sequence completed sucessfully
>>
> Above messages indicate that,
> - there are commands (mostly WRITE(10)) pending in MegaRAID F/W taking longer than given timeout period.
> - After driver waitinf for 10 seconds, all of those commands had been returned successfully.
> - So, the driver returned back to normal operation.
>
> There is NO data loss/integrity error related to this messages as driver returned back to normal successfully.
> Howerver, to get rid of those messages, I would like to ask you to check and upgrade F/W image on the controllers, first.
>
> Thank you,
>
> Seokmann
>
Seokmann,
Thank you for your reply. This makes me feel _much_ better. =). We
have verified all the firmware levels except the PowerVault 220 external
chassis. We have only hit this error with external devices, and since
we went ot the PV220 from an older chassis it has continued. (All new
controllers, system and motherboard, but the same Debian Install w/ a
newer kernel). We have scheduled outage this weekend to down the
server and then use the diagnostic tools to check/update the firmware
inside the PowerVault.
Since we have brand-new hardware all over - do you have any other
recommendations about what, if anything, further could be done, if the
firmware is confirmed up to date?
Sincerely,
Joshua
next prev parent reply other threads:[~2006-10-20 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 12:41 Recurring MegaRAID SCSI Errors Ju, Seokmann
2006-10-20 13:53 ` Joshua Schmidlkofer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 14:08 Ju, Seokmann
2006-10-20 15:07 ` Patrick_Boyd
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=4538D4CE.5040607@imr-net.com \
--to=joshua@imrlive.com \
--cc=Seokmann.Ju@lsi.com \
--cc=akpm@osdl.org \
--cc=jms@dev.imr-net.com \
--cc=linux-scsi@vger.kernel.org \
--cc=mike@opsisarch.com \
/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