Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.OZ.AU!spool.mu.edu!uwm.edu!cs.utexas.edu!not-for-mail From: dhs@cs.utexas.edu (Douglas H. Steves) Newsgroups: comp.unix.bsd.bsdi.misc,comp.unix.bsd.misc Subject: Re: Custom install of BSDI Date: 23 Feb 1996 09:58:24 -0600 Organization: CS Dept, University of Texas at Austin Lines: 46 Message-ID: <4gko70$qs0@heckle.cs.utexas.edu> References: <4gi536$d8t@cronkite.seas.gwu.edu> NNTP-Posting-Host: heckle.cs.utexas.edu Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:2434 comp.unix.bsd.misc:525 In article <4gi536$d8t@cronkite.seas.gwu.edu>, Juzer T. Kopti <kopti@seas.gwu.edu> wrote: >Whilst installing BSDI I selected custom install (since express install >would automatically use /dev/hda) and erase all data there. During the >install process I indicated that BSDI should ONLY be installed on /dev/hdb >and /dev/hda would should not be touched. The install went smoothly. > >"no bsd label" highlighted in blue and a hung computer I am having a similar problem. I upgraded [sic] to Windows 95 and found out after installing it that Win95 has a fairly agressive attitude toward non-MS disk partitions (it seemed to just "allocate" the disk space in my second BSD partition) and thereupon trashed BSD/OS. So I reinstalled, and have been unable to boot BSD since. The problem seems to be related to my EIDE controller, which I installed so that I could use a bigger 2nd EIDE drive for Win95. (The EIDE controller is a Future Domain (now Adaptec) 16030). When I install wd boot blocks on wd0, I get a message when booting about no (or bad) boot blocks. When I install bios boot blocks for wd0, the system will boot just fine, but for some reason tries to chroot to sd0a and panics when it can't find init (which is good, because sd0a is /home). It also prints a message about no label on wd0. There are no BSD boot blocks on wd1 or sd0. I have 3 disk drives in my system: wd0, a WD 325M IDE drive that has a 250 Win95 partition and a 75M BSD/OS partition wd1, a Maxtor 1.6G EIDE drive that has a single Win95 partition. sd0, an IBM 1G SCSI dedicated to BSD/OS. I have used both the generic kernel and a reconfigured kernel (to support swapping on both sd0 and wd0) that explicitly sets wd0a as the root device. I have also tried both 2.0 and 2.1, with exactly the same results. When I take the EIDE controller out of the system, it works fine (but wd1 becomes a 500M drive). Any suggestions? BSDi support hasn't been able to resolve this problem. The latest is that they believe the Future Domain controller is the problem. Could be, but Win95 has no problems with it. Is anyone using BSD/OS with an EIDE controller with a similar partition scheme? Thanks, Doug