Date: Thu, 29 Aug 2002 15:37:32 -0400 From: "Miroslav Pendev" <miro@cybershade.us> To: "Long, Scott" <Scott_Long@adaptec.com> Cc: "SCSI FreeBSD" <scsi@freebsd.org> Subject: Re: Dell PERC 2/si RAID 5 - problem Message-ID: <002f01c24f93$8698c1a0$c801a8c0@vsivyoung> References: <2C7CBDC6EA58D6119E4A00065B3A24CB0464E4@btcexc01.btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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 Tanks a lot, Scot! I did rebuild the RAID with the BIOS and everything is *OK* now! It is out of the topic, but can you tell me which method is the preferable: to rebuild with the BIOS or with the software tool; The BIOS rebuild takes more than a hour. If I use the tool - is it necessary to boot into SU mode or I can run it in working environment (about 30 users)? (without interrupting the work process)? Thanks once again for your help! --Miro 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?002f01c24f93$8698c1a0$c801a8c0>