Date: Tue, 13 Jun 1995 10:57:32 -0700 (PDT) From: Howard Lew <hlew@genome.Stanford.EDU> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: bugs@FreeBSD.org Subject: Re: 2.05R panics on boot Message-ID: <Pine.SUN.3.91.950613104904.8424A-100000@vegemite.Stanford.EDU> In-Reply-To: <199506130802.BAA09770@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Jun 1995, Rodney W. Grimes wrote: > [Please, one list ONLY! Redirected to -bugs] > > > I just tried the new (second 2.05R) boot.flp, and it still panics with > > the same message on bootup after the PCI probe is completed. > > > > panic: cannot mount root > > syncing disks... done > > Automatic reboot in 15 seconds - press a key on the console to abort > > > Stopping say hd(1,a)/kernel as you do not have both an IDE and a SCSI > disk. You are trying to boot from the second IDE disk which is > wd(1,a)/kernel. The problem you are having is ``hd'' is magic, it > says use the n'th BIOS disk to load, but pass the kernel sd(n - 1) > as the root device. Thus it is looking for sd0 on your system for > the root file system, and you don't have one... > Thanks for the help. Using wd(1,a)/kernel did solve the panic problem (gee, how much I wish this was in a faq...) Now only if the system would boot up with the boot manager. What ever happened to the boot manager that was used on the SNAPs? That one seemed to work be able to boot up even on this 850 WDC drive with Ontrack DM installed. Booteasy wasn't able to do it. They were different right? or has something changed?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SUN.3.91.950613104904.8424A-100000>