From owner-freebsd-questions Thu Aug 22 6:54:57 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED51837B400 for ; Thu, 22 Aug 2002 06:54:53 -0700 (PDT) Received: from CPE0004761ac738-CM00109515bc65.cpe.net.cable.rogers.com (CPE0004761ac738-CM00109515bc65.cpe.net.cable.rogers.com [24.103.39.131]) by mx1.FreeBSD.org (Postfix) with SMTP id 0C34843E3B for ; Thu, 22 Aug 2002 06:54:53 -0700 (PDT) (envelope-from miro@cybershade.us) Received: (qmail 34343 invoked from network); 22 Aug 2002 13:54:55 -0000 Received: from unknown (HELO vsivyoung) (66.46.21.253) by cpe0004761ac738-cm00109515bc65.cpe.net.cable.rogers.com with SMTP; 22 Aug 2002 13:54:55 -0000 Message-ID: <006c01c249e3$77b79900$c801a8c0@vsivyoung> From: "Miroslav Pendev" To: Subject: RAID 5 on PowerEdge 2400 problem Date: Thu, 22 Aug 2002 09:54:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi guys, I have a problem with Dell PowerEdge 2400 running FreeBSD 4.6 RELEASE - four SCSI 16.9GB HDD Seagate drives as RAID 5. I got this error today: aac0: **Monitor** ID (0:03:0); Timeout Detected (Sync) [Aborting Command 0x03]Srb: )xa0668cf0, Status: 0x00 The system is with RAID 5 - Dell Perc 2i/Si and so far was working just perfect! dmesg shows: aac0: i960RX 100MHz, 54 MB cache memory, no batery support aac0: Kernel 2.1-3, Build 2939, S/N 880ad0 At boot time the RAID BIOS shows: the following containers have missing members and are degraded: Container#0-RAID-5 Container status - CRITICAL Obviously, something is wrong with the RAID, but all disc light are green - no error lights! 'fsck' didn't show any errors, too! Any ideas are welcome! Is there any way to find out which HDD (from the four) is the reason for this, or is there a tool to *correct* the CRITICAL status? -Miro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message