Date: Mon, 19 Jun 1995 10:08:46 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: bde@zeta.org.au (Bruce Evans) Cc: bde@zeta.org.au, bugs@FreeBSD.org Subject: Re: 2.05R panics on boot Message-ID: <199506191708.KAA01402@gndrsh.aac.dev.com> In-Reply-To: <199506191631.CAA09759@godzilla.zeta.org.au> from "Bruce Evans" at Jun 20, 95 02:31:08 am
next in thread | previous in thread | raw e-mail | index | archive | help
> > >From rgrimes@gndrsh.aac.dev.com Tue Jun 20 02:09:41 1995 > >Received: from gndrsh.aac.dev.com ([198.145.92.241]) by godzilla.zeta.org.au (8.6.9/8.6.9) with ESMTP id CAA09000 for <bde@zeta.org.au>; Tue, 20 Jun 1995 02:08:16 +1000 > >Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id JAA01169; Mon, 19 Jun 1995 09:07:30 -0700 > >From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> > >Message-Id: <199506191607.JAA01169@gndrsh.aac.dev.com> > >Subject: Re: 2.05R panics on boot > >To: bde@zeta.org.au (Bruce Evans) > >Date: Mon, 19 Jun 1995 09:07:30 -0700 (PDT) > >Cc: bugs@FreeBSD.org > >In-Reply-To: <199506191255.WAA02612@godzilla.zeta.org.au> from "Bruce Evans" at Jun 19, 95 10:55:16 pm > >X-Mailer: ELM [version 2.4 PL24] > >MIME-Version: 1.0 > >Content-Type: text/plain; charset=US-ASCII > >Content-Transfer-Encoding: 7bit > >Content-Length: 1611 > > >> > >> >Okay.... here is the output if I let the Ontrack DM load the dynamic > >> >overlay and then use the option to boot from the boot.flp. > >> > >> >If I choose wd(1,a)/kernel.GENERIC -v > >> > >> >FreeBSD 2.0.5-RELEASE #0: Sat Jun 10 10:46:56 1995 > >> >... > >> >wd0: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S > >> >... > >> >wd1: 518MB (1061424 sectors), 1053 cyls, 16 heads, 63 S/T, 512 B/S > >> >... > >> >changing root device to wd1a > >> >BIOS Geometries: > >> > 0:03391f3f 825 cyl, 31 heads, 63 sects > >> > 1:03fd0f3f 1021 cyl, 15 heads, 63 sects > >> > 0 accounted for > >> >wd1s1: type 0xa5, start 63, end = 1061423, size 1061361 : OK > >> > >> This all seems OK. > >> > >> >------------ > >> >Notice that no where in the boot process does it mention about the > >> >Ontrack DM. > >> > >> This is OK. wd0 isn't looked at since your'e not trying to boot > >> from it, so Ontrack isn't seen to be on it. It would be seen when the > >> DOS partition is mounted if you got that far. > >> Now if I use hd(1,a)/kernel.GENERIC -v (which I know I am > >> >not supposed to)... > >> > >> >It shows these extra lines after the "0 accounted for" > >> >wd0: Found "Ontrack Disk Manager" on this disk. > >> >wd0s1: type 0x1, start 126, end=1665278, size 1665153 : OK > >> >panic: cannot mount root > >> > >> This is normal. hd(1,a) becomes wd0a, which you don't have, but > >> Ontrack gets noticed when wd0 is looked at in the failed attempt to > >> open wd0a. > > >I think you really meant to say ``hd(1,a) becomes sd0a, which...'' > > I meant what I said. It can't have become sd0a because then wd0 > wouldn't have been looked at. It only becomes sd0a if the disklabel > type is DTYPE_SCSI. sd(0,a) becomes wd0a for the same reason. > sysinstall sets the disklabel type correctly under the assumption that > scsi disk names start with 's'. Typing hd(*, *) has no effect on the > FreeBSD major device. It only forces the FreeBSD unit number to 0. Then something has been changed in what is going on in the boot code with respect to hd(X,a), as this *DID* cause bootdev to be set to sd(X-1,a). And these comments are now need of updating: README.386BSD:use device 'hd' README.386BSD:hd is special in that the kernel is always told to use unit 0, README.serial: Use hd(1,a)/kernel to boot sd0 when wd0 is also installed. boot.c: "Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.\n" > > Bruce > -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506191708.KAA01402>