Date: Wed, 14 Feb 1996 09:00:49 -0800 (PST) From: Bora Akyol <bora@wireless.stanford.EDU> To: Greg Lehey <lehey.pad@sni.de> Cc: hackers@freebsd.org, FreeBSD Documenters <freebsd-doc@freebsd.org>, mollers.pad@sni.de Subject: Re: Confused!!!! (fwd) Message-ID: <Pine.BSF.3.91.960214085733.201A-100000@lightning.Stanford.EDU> In-Reply-To: <199602141531.QAA17350@nixpbe.pdb.sni.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Here is what I did when I had the same setup. I used os-bs beta version that is on the Walnut Creek CDROM. I made sure that the SCSI drive is seen by dos (does not need to be formatted). Then, I used os-bs beta version to create a boot menu. When it was done , everything worked. ONe thing that needs to be done is to hard wire the device id for the scsi drive for the kernel. Otherwise, it automatically assigns an ID at boot time to the scsi drive and it can't find the root partition when it comes to fsck at boot. After you do hard wire the drive in the kernel config DO not forget the change the fstab file. Hope this helps, if anyone has specific questions email me at akyol@leland.stanford.edu Bora On Wed, 14 Feb 1996, Greg Lehey wrote: > Forwarded message: > > > From: Frank J Estremera <festremera@shell.monmouth.com> > > > > I am so confused as to how to boot FreeBSD from a boot manager, while on a > > second drive. I have an internal IDE drive running Windows95. I also have a > > secondary SCSI drive (device 0), totally devoted to FreeBSD. I do have > > FreeBSD loaded on it, but when I installed FreeBSD, and selected BootEasy > > as the boot manager, The operating system could not be found when booting to > > Windows95 (primary drive). I deinstalled BootEasy and installed System > > Commander as my boot manager. It recognized the SCSI drive as having FreeBSD > > loaded on it, but when selected, System Commander tells me that the boot block > > is missing on this device. The only way that I can boot FreeBSD is to insert > > the install diskette in the A drive, boot from it, and when the BOOT prompt > > appears, pointing it to hd(1,a)/kernel (I think). Just for laughs I did a > > disklabel -B sd0 to maybe try to force a boot block on the SCSI device, but > > to no avail (unless I am totally out in left field, which is likely). What > > am I missing??? Why is my operating system under Windows95 being clobbered?? > > (I then have to do an fdisk from diskette to activate my C: partition again). > > Please shine a flashlight on my face and enlighten me! > > Could it be that the lack of replies to this message is the result of > everybody else being confused as well? I currently can't get near a > running FreeBSD system, and I honestly don't know a good answer, but I > get the feeling that we have a bug which manifests itself when using > booteasy when FreeBSD is not on the first drive. I've had another > report of this kind of problem here at SNI, and in this case I'm > pretty sure it wasn't user error. Any comments from others? > > Greg > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960214085733.201A-100000>