* megaraid aborting problem (RHEL 3WS)
@ 2004-09-09 12:10 Stas Nikiforov
2004-09-09 12:49 ` Matt Domsch
2004-09-09 12:50 ` Matt Domsch
0 siblings, 2 replies; 4+ messages in thread
From: Stas Nikiforov @ 2004-09-09 12:10 UTC (permalink / raw)
To: linux-scsi
Hi,
I have a RHEL 3WS (RocksCluster) distribution
(kernel 2.4.21-15ELsmp) with megaraid2 2.10.3 driver.
The following is reported by dmesg.
megaraid: v2.10.3 (Release Date: Thu Apr 8 16:16:05 EDT 2004)
megaraid: [713G:G117] detected 1 logical drives.
scsi0 : LSI Logic MegaRAID 713G 254 commands 16 targs 4 chans 7 luns
blk: queue c3620e18, I/O limit 4294967295Mb (mask
0xffffffffffffffff)
scsi0: scanning scsi channel 0 for logical drives.
Vendor: MegaRAID Model: LD 0 RAID5 1192G Rev: 713G
Type: Direct-Access ANSI SCSI revision: 02
Under heavy io I get the following messages reported by dmesg.
Could somebody tell me what is going wrong and what should I do next?
Thanks in advance,
Stas.
megaraid: critical hardware error!
megaraid: aborting-1441961 cmd=2a <c=0 t=0 l=0>
megaraid: 1441961:76, driver owner.
megaraid: Waiting for 8 commands to flush: iter:0
megaraid: Waiting for 8 commands to flush: iter:1000
megaraid: Waiting for 8 commands to flush: iter:2000
...
megaraid: Waiting for 8 commands to flush: iter:60000
megaraid: critical hardware error!
megaraid: reset-1441957 cmd=2a <c=0 t=0 l=0>
megaraid: reservation reset failed.
megaraid: Waiting for 8 commands to flush: iter:0
megaraid: aborted cmd 160098[41] complete.
megaraid: aborted cmd 160099[48] complete.
megaraid: aborted cmd 16009a[75] complete.
megaraid: aborted cmd 16009b[69] complete.
megaraid: aborted cmd 16009c[4d] complete.
megaraid: aborted cmd 16009d[6b] complete.
megaraid: aborted cmd 16009e[77] complete.
megaraid: aborted cmd 16009f[47] complete.
megaraid: reset sequence successfully completed.
megaraid: reset-1441965 cmd=2a <c=0 t=0 l=0>
megaraid: reservation reset failed.
megaraid: reset sequence successfully completed.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: megaraid aborting problem (RHEL 3WS)
2004-09-09 12:10 megaraid aborting problem (RHEL 3WS) Stas Nikiforov
@ 2004-09-09 12:49 ` Matt Domsch
2004-09-09 12:50 ` Matt Domsch
1 sibling, 0 replies; 4+ messages in thread
From: Matt Domsch @ 2004-09-09 12:49 UTC (permalink / raw)
To: Stas Nikiforov; +Cc: linux-scsi
On Thu, Sep 09, 2004 at 07:10:22PM +0700, Stas Nikiforov wrote:
> Hi,
> I have a RHEL 3WS (RocksCluster) distribution
> (kernel 2.4.21-15ELsmp) with megaraid2 2.10.3 driver.
> The following is reported by dmesg.
>
> megaraid: v2.10.3 (Release Date: Thu Apr 8 16:16:05 EDT 2004)
> megaraid: [713G:G117] detected 1 logical drives.
> scsi0 : LSI Logic MegaRAID 713G 254 commands 16 targs 4 chans 7 luns
> blk: queue c3620e18, I/O limit 4294967295Mb (mask
> 0xffffffffffffffff)
> scsi0: scanning scsi channel 0 for logical drives.
> Vendor: MegaRAID Model: LD 0 RAID5 1192G Rev: 713G
> Type: Direct-Access ANSI SCSI revision: 02
>
> Under heavy io I get the following messages reported by dmesg.
> Could somebody tell me what is going wrong and what should I do next?
The hardware controller firmwre took a long long time to respond to
the driver, if it responded at all. The SCSI mid-layer started timing
out requests, and eventually tried to reset the controller (but it
can't really do that).
You may want to try the newer driver that's on ftp.lsil.com and merged
into kernel.org to see if that helps, and make sure your firmware is
completely up-to-date.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: megaraid aborting problem (RHEL 3WS)
2004-09-09 12:10 megaraid aborting problem (RHEL 3WS) Stas Nikiforov
2004-09-09 12:49 ` Matt Domsch
@ 2004-09-09 12:50 ` Matt Domsch
1 sibling, 0 replies; 4+ messages in thread
From: Matt Domsch @ 2004-09-09 12:50 UTC (permalink / raw)
To: Stas Nikiforov; +Cc: linux-scsi
Oops, I missed you were running RHEL3. Get the latest errata kernel
(2.4.21-20.EL) from Red Hat and try again.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: megaraid aborting problem (RHEL 3WS)
[not found] <7076215DFAA4574099E5CD59FE422262050538CE@pcssrv42.pcs.pc.ome.toshiba.co.jp>
@ 2004-09-17 7:55 ` Stas Nikiforov
0 siblings, 0 replies; 4+ messages in thread
From: Stas Nikiforov @ 2004-09-17 7:55 UTC (permalink / raw)
To: Tomita, Haruo; +Cc: Linux-scsi list
Hi,
Sorry for a very long delay. I try to do some things with hardware.
I have 2.4.21-20EL,
WD 6xHDD SATA DISK drive 250GB,
RAID 5, LSI firmware [713G:G117]
I've get the nvram log from the controller.
Here it is.
LOG 48356182 event 0x390 time .....
Channel 0, Targed 255, lun 0
Code: 0x390
Category: i960 Hardware Error Event
My vendor told me to re-write firmware,
check all HDDs and re-initialize RAID.
Now I do these things.
Stas.
On Fri, 2004-09-10 at 09:46, Tomita, Haruo wrote:
> Hi all
>
> > megaraid: aborting-1441961 cmd=2a <c=0 t=0 l=0>
>
> Please let me know the environment which
> the abort issue of megaraid2 driver.
>
> - vender name of HDD
> - HDD fw version
> - RAID level
> - raid controller's FW version.
>
> I used three disks of Hitachi (Daytona S28B),
> and constituted them RAID5.
> The same error is experienced by 2.4.21-15.04EL.
> megaraid2 driver is 2.10.3, raid fw is 1T23.
>
> Best regards,
> Haruo
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-09-17 7:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-09 12:10 megaraid aborting problem (RHEL 3WS) Stas Nikiforov
2004-09-09 12:49 ` Matt Domsch
2004-09-09 12:50 ` Matt Domsch
[not found] <7076215DFAA4574099E5CD59FE422262050538CE@pcssrv42.pcs.pc.ome.toshiba.co.jp>
2004-09-17 7:55 ` Stas Nikiforov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox