Date: Wed, 3 Dec 1997 01:03:56 +0100 From: J Wunsch <j@uriah.heep.sax.de> To: Archie Cobbs <archie@whistle.com> Cc: freebsd-questions@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG Subject: Re: 2.2.5 problems Message-ID: <19971203010356.13078@uriah.heep.sax.de> In-Reply-To: <199712020023.QAA21293@bubba.whistle.com>; from Archie Cobbs on Mon, Dec 01, 1997 at 04:23:38PM -0800 References: <199712020023.QAA21293@bubba.whistle.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As Archie Cobbs wrote: > Problem #2: booteasy can't boot SCSI disk > ---------- > > I have an IDE and a SCSI disk, with Adaptec 2940W + BIOS. Upon > booting, the booteasy on the IDE is run: > > F1: DOS (Windows 95) > F2: BSD (empty partition) > F5: Disk 2 > > My root is on the SCSI disk, so I press F5... > > F1: BSD > F5: Disk 1 > > Pressing F1 here *should* boot the SCSI disk, but it doesn't. > Booteasy just comes back with the same menu and "F?". Typical geometry problem. The geometry you've been using to install this BSD slice (fdisk partition) is different than what your SCSI controller is actually using as its translation. The best solution is probably to create a partition and a filesystem on the BSD slice you've got on drive 0, and create a file /boot.config in that partition containing just 1:sd(1,a)kernel All other solutions are more complicated (reinstall, or manually fixup the fdisk table on disk 1). Of course, i know i'm sounding like a broken record with this: using `dangerously dedicated' mode on the second disk would have avoided the entire problem from the beginning (with the minor exception that booteasy from drive 0 would then immediately boot BSD when hitting F5, since you can't have a boot selector on disk 1 in this case). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971203010356.13078>