From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 18 14:52:45 2004 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F82A16A4D2 for ; Wed, 18 Feb 2004 14:52:45 -0800 (PST) Received: from mail.bronskill.com (mail.bronskill.com [206.47.145.35]) by mx1.FreeBSD.org (Postfix) with SMTP id C369C43D2D for ; Wed, 18 Feb 2004 14:52:44 -0800 (PST) (envelope-from oliver@bronskill.com) Received: (qmail 25931 invoked from network); 18 Feb 2004 22:39:52 -0000 Received: from 206-47-145-36.ip.tor.radiant.net (HELO bronskill.com) (206.47.145.36) by mail.bronskill.com with SMTP; 18 Feb 2004 22:39:52 -0000 Message-ID: <4033ED82.4030405@bronskill.com> Date: Wed, 18 Feb 2004 17:56:02 -0500 From: Oliver Neubauer User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Mylex DAC1180 booting problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: oliver@bronskill.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2004 22:52:45 -0000 Hello all, I'm having a tough time getting a new FreeBSD 5.2 installation to boot off of a RAID system drive (Mylex DAC1180, two RAID 5 system disks defined, 2G mode). Essentially, I have done a standard install, creating a FreeBSD slice on the smaller (5G) system drive (using the whole disk, non-dd mode) and even created a separate partition on that slice for /boot (200M). When I reboot the system, the boot screen says it can't find /boot or kernel. I suspect this is largely due to the fact that it seems to be looking on ad0a instead of mlxd0d since it's displaying something like 0:(ad,0)/boot I hate to sound like such a newb, but my attempts to change the loader's default is falling well short of producing any results. So I guess my direct questions are: How can I use the (horribly crippled, it seems) virtual shell from the installer to modify the boot loader's behavior via boot.conf (mounting the disk is the problem here). and/or How can I make it look for /boot on another device at boot time? Anyone have any helpful advice? Thanks Oliver