Date: Mon, 19 Jun 1995 22:55:16 +1000 From: Bruce Evans <bde@zeta.org.au> To: bde@zeta.org.au, hlew@genome.Stanford.EDU Cc: bugs@FreeBSD.org, terry@cs.weber.edu Subject: Re: 2.05R panics on boot Message-ID: <199506191255.WAA02612@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>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. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199506191255.WAA02612>