From owner-freebsd-bugs  Mon Sep 23 18:01:24 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id SAA06399
          for bugs-outgoing; Mon, 23 Sep 1996 18:01:24 -0700 (PDT)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA06374
          for <freebsd-bugs@freebsd.org>; Mon, 23 Sep 1996 18:01:21 -0700 (PDT)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <16728(4)>; Mon, 23 Sep 1996 18:00:43 PDT
Received: by crevenia.parc.xerox.com id <177476>; Mon, 23 Sep 1996 18:00:33 -0700
From: Bill Fenner <fenner@parc.xerox.com>
To: darrylo@sr.hp.com, fenner@parc.xerox.com
Subject: Re: Very disturbing boot block problems..
Cc: freebsd-bugs@freebsd.org
Message-Id: <96Sep23.180033pdt.177476@crevenia.parc.xerox.com>
Date: Mon, 23 Sep 1996 18:00:19 PDT
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>     This should work (unless you have a really funky BIOS geometry,
>which is extremely unlikely -- what kind of system do you have?).

It's one of the relatively early Intel Pentium motherboards, with an
NCR SCSI controller.

>When was the last time you did an fsck on the root partition

Well, "fsck -n" claims that the filesystem is fine.  I'll try to replicate
the problem and run my new fsdb that prints out all of the block numbers &
see if that sheds any light on the problem...

  Bill