CentOS - Sep 2009 - qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.

hi All,

Re below - thanks for the replies to the fsck question.

I have run fsck -r /data and this eventually completed with several changes
made.

Now I am getting the following error from the qla2xxx driver on boot

.
.
.
qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort.
.
etc
.


It looks like some administration of the HSV controlled SAN device layer itself
is required - we
are now not even getting the boot process as far as the filesystem layer.

(Anybody know exactly what that message indicates - e.g. whether a hardware
fault or
HSV SAN config issue ?)

googling this , somebody suggested  a media scan from my storage array firmware,
then backing up the array and reinitializing logical disks and started
fresh....however
if anybody has some more specific info than that, that would be great. (I
don't
have administrative access to these devices in any case)

Looks like may have fsck'd on top of a wobbly device layer which probably
does not
bode well :-(

(I will summarise all of this to the list at some stage )

Cheers

AMcC


(Original post : )
>A fault on our SAN dropped us down to a read-only filesystem and after
reboot,
>we have an "Unexpected Inconsistency" and I am being instructed by
the boot to run fsck manually
>without -a or -p  (this was after I think processing around 15% of the
filesystem)
>The specific message is  "inode 27344909 has illegal blocks"
>I recall running fsck some years ago on smaller and simpler systems - am
broadly
>familiar with what it is but have no expertise in using it to repair a
filesystem.
>Would be grateful for advice on whats the quickest / usual way to get us
back up from
>this. We do have a good backup for restoring unrecoverable files - i.e. I
assume I am going
>to end up  asking fsck to repair the filesystem itself and then clean up any
mess that
>results.
>This is fsck 1.39 , Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42
>thanks for any tips.
>Cheers
>AMcC
>Bioinformatics Software Engineer
>AgResearch NZ





======================================================================Attention:
The information contained in this message and/or attachments
from AgResearch Limited is intended only for the persons or entities
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipients is prohibited by AgResearch
Limited. If you have received this message in error, please notify the
sender immediately.
======================================================================--------------
next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.centos.org/pipermail/centos/attachments/20090914/7f9cc1a3/attachment.html>

McCulloch, Alan wrote:
> Now I am getting the following error from the qla2xxx driver on boot
If your not using an official qlogic driver try an official
one and see if that fixes it, if not send the info to
qlogic support, took only a few seconds of searching to find
this out..

nate