From owner-freebsd-current Wed Jul 5 15:30:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E93BD37B7CF; Wed, 5 Jul 2000 15:30:33 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA09483; Wed, 5 Jul 2000 15:30:31 -0700 Date: Wed, 5 Jul 2000 15:28:57 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: current@freebsd.org Subject: Re: subtle problem du jour.... In-Reply-To: <200007052218.PAA13242@mass.osd.bsdi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Jul 2000, Mike Smith wrote: > > > > This really bit me- it shouldn't have- but it did.... > > > > I had a i386 system with a 4GB disk -- root partition ~1GB.... but the > > motherboard was setting up BIOS as a CHS instead of an LBA arrangement. > > > > The only time this showed up as problem was that when I reinstalled the > > loader (and related forth files), loader silently was not able to read /boot > > or /modules- the key word here is "silently". > > > > There ought to be a warning in loader(8) maybe about this? > > The loader used to bitch if it couldn't find its startup files, but this > got turned off because people didn't like it. There would be a couple of > ways to deal with the problem you're seeing (in addition to the very > worthwhile documentation) - > > a) bitch if the loader.rc file can't be found/read. > > b) bitch in the BIOS disk driver if an illegal read is attempted. > > Both of these might have given you enough clue to help find the problem > more quickly. Any comments, folks? both would have been helpful To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message