From owner-freebsd-questions@FreeBSD.ORG Wed Mar 19 18:07:59 2008 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 509B5106564A for ; Wed, 19 Mar 2008 18:07:59 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id BEB1B8FC21 for ; Wed, 19 Mar 2008 18:07:58 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: (qmail 29916 invoked by uid 0); 19 Mar 2008 18:07:56 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (216.186.148.249) by smtp3.knology.net with SMTP; 19 Mar 2008 18:07:56 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 88B9928425; Wed, 19 Mar 2008 13:07:54 -0500 (CDT) Date: Wed, 19 Mar 2008 13:07:54 -0500 From: David Kelly To: Walker Message-ID: <20080319180754.GA5084@Grumpy.DynDNS.org> References: <76C6FE72-043C-4EFB-8598-98BB73E11345@hiwaay.net> <6293ba970803190731y2ec9eca5mc5c62c52e67dd1ea@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6293ba970803190731y2ec9eca5mc5c62c52e67dd1ea@mail.gmail.com> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Questions Subject: Re: bsdlabel, now no boot X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Mar 2008 18:07:59 -0000 On Wed, Mar 19, 2008 at 10:31:18AM -0400, Walker wrote: > On Tue, Mar 18, 2008 at 10:26 PM, David Kelly wrote: > > > > System is now booting ad0 by starting at ad4 and hopping to ad6, > > then to ad0. > > Yes, you've discovered a "feature" of the 400SC (I have 3). If you > have PATA and SATA disks installed: > > SATA disabled in BIOS -> PATA boots > SATA enabled in BIOS -> SATA boots, and stops if it can't (PATA never > attempted) > > The best work around is to install a boot loader on your SATA HD to > point to the PATA HD. Yes, thats what is running now. Sadly I've already recycled the two SATA drives that came out and don't remember how they were configured that the PATA drive booted. Know I have used boot0cfg(8) in the past but don't recall if it was on this system. Using boot0cfg one can set the timeout to 0 so that the drive immediately hops to the next. However I'm thinking the Dell BIOS ignores the SATA drives during boot if the MBR is zeroed. With virgin SATA drives installed and enabled but not yet labeled the system booted off the PATA drive. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.