From owner-freebsd-stable Mon Jul 30 17:24:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from server1.wallnet.com (server1.wallnet.com [208.225.162.8]) by hub.freebsd.org (Postfix) with ESMTP id 34B8B37B40B for ; Mon, 30 Jul 2001 17:24:29 -0700 (PDT) (envelope-from timothyk@server1.wallnet.com) Received: from localhost (timothyk@localhost) by server1.wallnet.com (8.9.0/8.9.0) with SMTP id UAA19060; Mon, 30 Jul 2001 20:24:26 -0400 (EDT) Date: Mon, 30 Jul 2001 20:24:26 -0400 (EDT) From: Tim Kellers To: Kevin Oberman Cc: stable@FreeBSD.ORG Subject: Re: PERC 3 Dell 2500 and FreeBSD 4.3 stable In-Reply-To: <200107302018.f6UKI6b28543@ptavv.es.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thanks for the reply. The PERC is a PERC 3 Di. I did set up the container before I tried booting the CD-ROM (4.2), when that didn't work, I took a look through the archive at FreeBSD.org and found that the PERC 3 drivers (aac, anyway) weren't MFC'd until some days after 4.3 RELEASE. I checked the GENERIC kernel file on one of my other FreeBSD boxes (a PE 2400, no raid) and found that the PERC 2/3 options were in the kernel; that box was cvsuped and a full build was done on July 22. I downloaded the kern.flp and MFS.flp from FreeBSD.org and made disk images to make sure I was booting (I think) the latest disk. But even though I had configured the container (RAID 5, 3 36 GB harddrives) and reconfigured the container (1 big 108 GB drives), the OS FreeBSD 4.3 boot disks, couldn't find a hard drive. I went into the Bios, changed the RAID from the default to SCSI, and the OS saw the 3 36 Gig drives. Good old (yech) NT 4.0 on the Dell Management software boot CD, saw the RAID just fine, so I still think something is odd with the drivers. I'm not certain how to create a boot floppy with the Generic compiled kernel in it, so some guidance on how to do it, or further pointers on my folly in the PERC configuration, would be much appreciated. Tim On Mon, 30 Jul 2001, Kevin Oberman wrote: > > Date: Mon, 30 Jul 2001 15:58:41 -0400 (EDT) > > From: Tim Kellers > > Sender: owner-freebsd-stable@FreeBSD.ORG > > > > > > Has anyone gotten the PERC 3 RAID controller to work using FreeBSD 4.3? > > > > It looks like I might have to build a boot disk (a la kern.flp) with a > > precompiled kernel with the appropriate PERC 2/3 OPTIONS. > > > > I haven't done this before and was wondering if there is any documentation > > for building a custom boot floppy? > > Tim, > > The standard boot floppies should handle the PERC, but at least 4.3 > floppies are needed as most of the RAID stuff came after 4.2 was > released. > > Also you need to go in at boot time and set up the containers before > ANY OS can deal with them. I believe you need to type CTRL-A at the > correct time during the boot to get to the config utility. > > The model PERC 3 is really not adequate to identify the card and PERC > is the name DELL sticks on all of it's RAID controllers, regardless of > who made them or whether they are integrated onto the mobo or > external. > > I run Dell PowerEdge servers with PERC3/Si RAID controllers running as > RAID 1. > > If you have the complete model number, it's possible to tell who made > it and which driver should be used. Should be either ami or aac. (The > former for American Megatrends and the latter for Adaptec.) > > Here is a summary of PERC hardware from Mike Smith who did most (all) > of the driver work for them: > The PERC, PERC 2/SC, PERC 2/DC and PERC 3/D* are AMI designs. > > The PERC 2/Si, PERC 2/Di, PERC 3/Si and PERC 2/QC are Adaptec designs. > > "PERC" means "this is a Dell-branded RAID controller". > "2" and "3" refer to 40MHz vs 80MHz SCSI support. > "S" "D" and "Q" are single, dual and quad channel designations. > "i" means it's integrated onto the server motherboard. > "C" means it's an addin card. > "L" means it's the low-cost version. > > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message