Date: Wed, 19 Mar 2008 13:07:54 -0500 From: David Kelly <dkelly@hiwaay.net> To: Walker <zflyer@gmail.com> Cc: FreeBSD Questions <questions@freebsd.org> Subject: Re: bsdlabel, now no boot Message-ID: <20080319180754.GA5084@Grumpy.DynDNS.org> In-Reply-To: <6293ba970803190731y2ec9eca5mc5c62c52e67dd1ea@mail.gmail.com> References: <ABE0BB59-27A6-4F21-A098-EA8314133B7E@hiwaay.net> <76C6FE72-043C-4EFB-8598-98BB73E11345@hiwaay.net> <6293ba970803190731y2ec9eca5mc5c62c52e67dd1ea@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 19, 2008 at 10:31:18AM -0400, Walker wrote: > On Tue, Mar 18, 2008 at 10:26 PM, David Kelly <dkelly@hiwaay.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080319180754.GA5084>