Date: Wed, 19 Mar 2008 20:35:31 -0400 From: Walker <zflyer@gmail.com> To: "David Kelly" <dkelly@hiwaay.net>, freebsd-questions@freebsd.org Subject: Re: bsdlabel, now no boot Message-ID: <6293ba970803191735h17c8c417g63f28858db752853@mail.gmail.com> In-Reply-To: <20080319180754.GA5084@Grumpy.DynDNS.org> References: <ABE0BB59-27A6-4F21-A098-EA8314133B7E@hiwaay.net> <76C6FE72-043C-4EFB-8598-98BB73E11345@hiwaay.net> <6293ba970803190731y2ec9eca5mc5c62c52e67dd1ea@mail.gmail.com> <20080319180754.GA5084@Grumpy.DynDNS.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 19, 2008 at 2:07 PM, David Kelly <dkelly@hiwaay.net> wrote: > 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. Thanks for that info. IIRC, when I first installed a SATA with a PATA HD I got an 'operating system not installed' message when the bios attempted to boot off SATA, and it stops there. The next time I need to rebuild at 400SC I'll try zeroing out the MBR.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6293ba970803191735h17c8c417g63f28858db752853>