Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Dec 95 20:02:01 PST
From:      Ben Jackson <bjj@sequent.com>
To:        Don Yuniskis <dgy@rtd.com>
Cc:        freebsd-hackers@freefall.freebsd.org (FreeBSD hackers)
Subject:   Re: boot from sd1? 
Message-ID:  <199512300402.UAA17605@eng4.sequent.com>
In-Reply-To: Your message of "Fri, 29 Dec 95 19:45:04 PST." <199512300245.TAA06357@seagull.rtd.com> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <199512300245.TAA06357@seagull.rtd.com> , you wrote:
> wd0 -- MS-DOG
> wd1 -- FBSD 2.1.0R
> sd0 -- *more* MS-DOG stuff
> sd1 -- FBSD 2.1.0R (a *different* filesystem hierarchy)
>     How do I manage to boot from sd1?  It seems that wd1 intercepts
> whatever incantation I use (sd1, hd1, etc.)

The bios boot code recognizes hd0..hdN based on the order of the BIOS
probes.  That should make your sd1 show up as hd3.

Question:  I have wd0, sd0, sd1, and I boot from sd0 (from before I had
the wd0 drive).  When I was running 2.0.5, I patched the boot code to
default to hd1 so that after getting the secondary boot block off of
wd0, it would actually boot from sd0.  After I installed 2.1.0, I made
the same change.  Now, however, after successfully booting from sd0,
the kernel panics because it isn't pointing at sd0a as the root device.
What did I miss?

--Ben



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512300402.UAA17605>