Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Feb 97 15:19:07 +0100
From:      garyj@frt.dec.com
To:        Erik Manders <erik@il.ft.hse.nl>
Cc:        questions@freebsd.org
Subject:   Re: Bootblock (mis)behaviour 
Message-ID:  <9702101419.AA16556@cssmuc.frt.dec.com>
In-Reply-To: Message from Erik Manders <erik@il.ft.hse.nl>  of Mon, 10 Feb 97  13:40:33 %2B0100.

next in thread | previous in thread | raw e-mail | index | archive | help

erik@il.ft.hse.nl writes:
> Hello,
>    I recently bought a 3Gb SCSI drive to replace the IDE disks that had
> been in my machine. After I had disklabeled, installed bootblocks, moved
> the file systems and installed a new kernel, I removed the IDE and
> booted the new setup. To my amazement the new kernel continued to want
> wd0a as its root device, even though `root on sd0' had been in the
> config file.
> 
>    Things even went so far that even though I typed `sd(0,a)/kernel',
> the machine said it was booting from `wd(0,a)/kernel'. The kernel was
> still loaded from the SCSI drive. It later said `changing root device
> to wd0a'. My DOS stuff (on the same disk) was and is working perfectly.
> 
>    After some hair-pulling, I started looking at the boot block source.
> I have some theories as to why things are going wrong. It seems to me
> that the variable `maj' gets zeroed between the assignment
> `maj = devp-devs' in sys.c:openrd() and the `MAKEBOOTDEV()' macro in
> boot.c:loadprog(). It's probably before the call to loadprog(), since
> the printf() at early in loadprog() reports maj=0. Changing the `maj' in
> the MAKEBOOTDEV() macro to `4' solves the problem. So (probably) would
> an assignment `maj=4' early in loadprog. It's ugly but it works.
> 
>    Has anyone else here had similar problems? For your information, I'm
> running -current (CTM-current around 3000, IIRC) on a noname pentium
> board with an NCR PCI SCSI controller. More detailed information
> available on request.
> 

did you also remove the IDE disk from the BIOS setup ? The bootblocks
just use what the BIOS tells them. If the BIOS says that there's an
IDE disk, then the behavior you're seeing would be explained.

---
Gary Jennejohn				(work) gjennejohn@frt.dec.com
					(home) Gary.Jennejohn@munich.netsurf.de
					(play) gj@freebsd.org





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