Date: Fri, 30 May 1997 19:06:30 +0000 From: "Riley J. McIntire" <chaos@mail.tgci.com> To: "Brad Bates" <bab@icon.lal.ufl.edu> Cc: questions@FreeBSD.ORG Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't bo Message-ID: <199705310240.TAA23058@train.tgci.com>
next in thread | raw e-mail | index | archive | help
> From: "Brad Bates" <bab@icon.lal.ufl.edu> > To: <chaos@tgci.com> > Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't bo > Date: Fri, 30 May 1997 18:00:37 -0400 > I don't want to butt-in here, and I am not a FreeBSD > guru, but it seems that any bootloader that is setup > this way would not "see" the IDE drive correctly if > it is added to the CMOS after the initial setup for a > SCSI drive. PCs "think" the boot drive is the first > IDE drive when they are in the CMOS, and I suspect > the bootloader behaves a lot like is described below. Not butting in at all. The reason I disabled the ide drive in the first place (subject of a previous, similar help message to no avail! :( ) is that one of the first times I tried this I left the ide drive (with 2.1.7 on it) active. I used the boot floppy and disk labeled the second, scsi drive for 2.2.2. The result of that was that the system on the ide drive got trashed. It would still boot, but *lots* of errors. Luckily I had backups--it's a live, but low use mail/web server. > > Did you re-install with the IDE in place from the start, > and, if so, did that cure the problem? No, gun shy per above! > > Sorry to interrupt -- this was good to see in advance > since I may have run into similar problems in a week > or so! Thanks, and hope for nothing but SCSI in all > of our futures... You're right about a pc wanting to boot from the first ide, although I recently saw a bios that had a scsi boot option. But I don't think that's the problem here--it's more the way fbsd looks at the disks. Maybe. I'd really like someone who understands this to explain. But it is a temporary situation I can work around. At this point it's mostly curiosity. Cheers, Riley > > Brad Bates > ---------- > > From: Riley J. McIntire <chaos@mail.tgci.com> > > To: Nadav Eiron <nadav@barcode.co.il> > > Cc: questions@FreeBSD.ORG > > Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't bo > > Date: Friday, May 30, 1997 6:44 AM > > > > > Date: Thu, 29 May 1997 09:04:09 +0300 > > > From: Nadav Eiron <nadav@barcode.co.il> > > > To: chaos@tgci.com > > > Cc: questions@FreeBSD.ORG > > > Subject: Re: Can one dual boot fbsd? No? (was Re: wd0/sd0 can't > bo > > > > > Riley J. McIntire wrote: > > > > > > > [snip] > > > > > > > > > > Try giving: > > > > > 1:sd(0,a)/kernel > > > > > > > > > That worked! I did try it in a previous incarnation, but the config > > > > was differnent. > > > > > > > > Now, why doesn't the boot loader work? Not a big deal, but a theory > > > > would be nice. > > > > > > Here it goes (I may be mistaken, as I'm not the one who've written the > > > code, but still...): > > > The 1: at front hints to the boot code that the disk you're about to > > > boot is known by the BIOS as the second disk (BIOS code 0x81). > > > Otherwise, FreeBSD cannot guess what drive to ask the BIOS to boot > from, > > > and its best shot is to use the number you have on the device name, so > > > when you give it sd0 it assumes it's your first disk (#0), but in your > > > case, that's wd0. This is simply because the boot code has no sure way > > > of knowing the mapping between FreeBSD device names and BIOS disk > > > numbers. > > > > > This might explain this new behavior: I reinstalled using the > > upgrade option. Again, the IDE bus was disabled in cmos while > > installing. > > > > After the upgrade I reenabled the ide bus. > > > > Now the boot prompt F1/F2/F5 (dos/fbsd/2nddisk) works--I press F5, get > > the second disk, choose F2 (sd(0,a)--2.2.2-R), it goes through the paces, > and then > > get a "Panic--cannot mount root on sd(0,a)" (may not be the exact > > message...) > > > > Anyway, if I specify 1:sd(0,a)/kernel, it boots. Strange. > > > > Cheers, > > > > Riley > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705310240.TAA23058>