Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Dec 1996 11:03:19 -0800
From:      Dan Yergeau <yergeau@gloworm.Stanford.EDU>
To:        "Hr.Ladavac" <lada@ws2301.gud.siemens.co.at>
Cc:        hackers@freebsd.org
Subject:   Re: 2.1.5-R kernel root on sd0 fails 
Message-ID:  <199612131903.LAA05307@antonios.Stanford.EDU>
In-Reply-To: Your message of "Thu, 12 Dec 1996 19:19:07 %2B0100." <199612121819.AA221754747@ws2301.gud.siemens.co.at> 

next in thread | previous in thread | raw e-mail | index | archive | help
"Hr.Ladavac" writes:
>Hi all,
>
>I know that 2.1.5 is last year's snow, but:
>
>I had a happy installation with one SCSI disk and then had to add
>a wd0--don't ask why.
>
>Subsequently I went to generate a new kernel in order to be able to
>boot from sd0 without manual keyboard intervention every time.

There doesn't appear to be a way to convince the biosboot to pass
the "correct" information to the kernel (after all, both are bios
drives).  Just putting "root on sd0" in the kernel config does not
appear to work (the kernel still tries what it got from biosboot,
sd1), but the following worked for me.

Put "root on sd1" and wire the SCSI drive to be sd1 (e.g. "disk sd1
at scbus0 target 0").  You may also need to wire scbus0 to a
particular controller (e.g. "controller scbus0 at ahc0").  See the
LINT kernel config if you need more information on how to wire disk
and controller targets.

Before you boot with the new kernel, make sure that you've updated
/etc/fstab and created the needed slice devices for sd1s?[a-h] in
/dev (if they don't already exist).  AND, have a fixit floppy handy!


Dan






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