From owner-freebsd-current Sun Mar 19 18: 4:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 159EB37B839 for ; Sun, 19 Mar 2000 18:04:42 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id B28C61C4D; Sun, 19 Mar 2000 21:04:41 -0500 (EST) Date: Sun, 19 Mar 2000 21:04:41 -0500 From: Bill Fumerola To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: AMI MegaRAID lockup? not accepting commands. Message-ID: <20000319210441.T25438@jade.chc-chimes.com> References: <200003200200.VAA11571@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003200200.VAA11571@bb01f39.unx.sas.com>; from jwd@unx.sas.com on Sun, Mar 19, 2000 at 09:00:35PM -0500 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Mar 19, 2000 at 09:00:35PM -0500, John W. DeBoskey wrote: > amr0: mem 0xf6c00000-0xf6ffffff irq 14 at device 10.1 on pci2 > amr0: firmware 1.01 bios 1p00 128MB memory > amrd0: on amr0 > amrd0: 172780MB (353853440 sectors) RAID 5 (optimal) > > The adapter does not lockup while testing with bonnie and such. > However, we have a 50Gig CVS repository sitting on the raid > volume. When we do a 'cvs co' of -HEAD, it causes it to lockup. > The following messages are repeating continuously: > > Mar 19 16:02:59 cvs /kernel: amr0: controller wedged (not taking commands) > Mar 19 16:03:00 cvs /kernel: amr0: I/O error - dead > Mar 19 16:03:00 cvs /kernel: amr0: cmd 2 ident 178 drive 0 > Mar 19 16:03:00 cvs /kernel: amr0: blkcount 12 lba 59506736 > Mar 19 16:03:00 cvs /kernel: amr0: virtaddr 0xd3089000 length 6144 > Mar 19 16:03:00 cvs /kernel: amr0: physaddr 0000c880 nsg 2 > Mar 19 16:03:00 cvs /kernel: amr0: 1abea000/4096 > Mar 19 16:03:00 cvs /kernel: amr0: 25d2b000/2048 Ditto, less the kernel messages. Every process wedged into biord and I couldn't reboot the machine or do much of anything (no DDB, grrrr). Rebooting this resulted in all the of the disks being marked 'failed' by the controller and I had to remark them 'online' and boot. A very long night(well, whatever 3am is..) of fscking followed. It was not fun. amr0: mem 0xf6c00000-0xf6ffffff irq 10 at device 10.1 on pci2 amr0: firmware 3.13 bios 1.43 16MB memory amrd0: on amr0 amrd0: 173390MB (355102720 sectors) RAID 5 (optimal) -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message