Date: Thu, 29 Aug 2002 09:55:48 -0600 From: "Long, Scott" <Scott_Long@adaptec.com> To: "'Miroslav Pendev'" <miro@cybershade.us>, SCSI FreeBSD <scsi@freebsd.org> Subject: RE: Dell PERC 2/si RAID 5 - problem Message-ID: <2C7CBDC6EA58D6119E4A00065B3A24CB0464E4@btcexc01.btc.adaptec.com>
next in thread | raw e-mail | index | archive | help
> 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 This is a message from the firmware that drive 0:3:0 is having major troubles. > > The system is with RAID 5 - Dell Perc 2i/Si and so far was working > just perfect! > > dmesg shows: > aac0: <Dell PERC 2/si> mem [......] > 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 show this error: > > The following containers have missing members and are degraded: > Container#0-RAID-5 > Container status - CRITICAL This means that Container 0 contains a failed drive and is operating in 'Critical' mode, meaning that it is being forced to actively reconstruct the data for the failed drive, and any further drive failures will result in data loss. > > Obviously, something is wrong with the RAID, but all disc light are > green - no error lights! 'fsck' didn't show any errors, too! > Though, there is no any activity from one of the drives! fsck won't show any error because the RAID controller is doing it's job; i.e. it is reconstructing the data for the failed drive from the parity on all the other drives. > Is there a tool for FreeBSD that I can use to see what is problem, > or to rebuild the RAID 5? I have a replacesement HDD. > > I know PERC is actualy Adaptec SCSI RAID card, but I am not > sure for the exact > model. > > The previous post to this list was for PERC 3si, can I use the > same FreeBSD tool or it is not for this card? > Yes, as I mentioned in my previous email, the aaccli tool that I linked to will work for every aac-based raid subsystem that is available right now. > Any ideas are welcome! Replace drive 0:3:0 with a new drive. Regardless of what green lights may be lit on it, it has failed. You'll need to use either the BIOS or the aaccli tool to assign the new drive as a spare. Once you do that, the array will rebuild onto it, and everything will be back to normal. Of course, you should *always* have a spare drive available and assigned. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2C7CBDC6EA58D6119E4A00065B3A24CB0464E4>