Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!library.ucla.edu!europa.eng.gtefsd.com!MathWorks.Com!yeshua.marcam.com!usc!news.service.uci.edu!beamlab!bob From: bob@beamlab () Newsgroups: comp.os.386bsd.questions Subject: Booting sd1 Date: 4 Aug 1994 01:50:21 GMT Organization: University of California, Irvine Lines: 31 Distribution: world Message-ID: <31phgt$h93@news.service.uci.edu> NNTP-Posting-Host: beamlab.ps.uci.edu Summary: Do I have to use new bootblocks? Keywords: bootblocks, installation, second disk, sd1 X-Newsreader: Tin 1.1 PL4 Hello all, What's the trick to installing FreeBSD 1.1.5.1 on SCSI disk one (instead of zero)? The system in question uses a BT445s host adapter with one Quantum 105 and one Seagate ST4767 The motive is a desire to run Windows NT, which must be on SCSI ID 0, using Booteasy to select the desired OS. At present Freebsd is on the Seagate disk and NT is on the Quantum. It seemed easiest to install on sd0, build a new kernel, and change disk ID number. Initial installation with the disk set to ID 0 worked fine and I was able to build a new kernel with root and swap on sd1. However, when I reset the SCSI ID to 1 and tried to reboot (with the freebsd disk alone on the controller) the bootprocess reported it as sd0! (yes, I did toggle power on the disk after changing the ID setting 8-) ) The system came up just fine, in spite of the discrepancy. When disk 0 was connected booteasy took over correctly and allowed me to boot the disk containing FreeBSD, but the process stopped with "/386bsd not found". This leads me to suspect the bootblocks need to be changed. What's the best way to proceed? thanks for reading bob