Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!lll-winken.llnl.gov!uwm.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!news1.digex.net!news3.digex.net!digex.net!not-for-mail From: grina@cnj.digex.net (Peter Grina) Newsgroups: comp.unix.bsd.freebsd.misc Subject: INSTALL problem due to 2 IDE controllers? Date: 10 Oct 1995 15:18:44 -0400 Organization: Peter A. Grina - Consulting Lines: 38 Message-ID: <45eguk$h89@cnj.digex.net> NNTP-Posting-Host: cnj.digex.net I believe that I'm having a device naming problem that's preventing FreeBSD 2.0.5 from booting properly. Any help would be greatly appreciated. My son's PC has one disk on each of his two IDE controllers... the first one for his DOS/MSWIN stuff; the second for FreeBSD is on the second controller. The FreeBSD installation works just great. The post-install stuff works great. The problems appear during the post-install reboot. The boot manager fails to take control (I selected the first of the 3 boot manager choices during the install), and then DOS/MSWIN boots up from the C: drive. When I boot with the FreeBSD floppy inserted, I am able to boot (sort of) from the second IDE controller using the command: Boot: wd(1,a)/kernel The problem is that the boot fails when it tries to mount wd1a as root. During the install, I did a "df" on the Alt-F4 screen and it showed the root filesystem as /dev/wd2a. The /etc/fstab indicates root should come from /dev/wd2a... why/where is wd1a coming from? I tried playing with the boot device name, but wd(2,a)/kernel immediately spews a stream of C:0 H:0 D:0 (the letters may be wrong) messages. Is this a boot config thing? Do I have to muck with the /dev directory after the install? I could use a hint. If there is no clean solution, then I'll try configuring the second disk as a slave of the first controller. Is this the cleanest solution? Will the boot manager work then? Will my root mount up properly? HAAAAALP! Regards, Pete Grina (grina@cnj.digex.net)