From owner-freebsd-bugs Mon Sep 23 12:49:08 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA15839 for bugs-outgoing; Mon, 23 Sep 1996 12:49:08 -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 MAA15816 for ; Mon, 23 Sep 1996 12:49:05 -0700 (PDT) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <15295(5)>; Mon, 23 Sep 1996 12:48:28 PDT Received: from localhost by crevenia.parc.xerox.com with SMTP id <177476>; Mon, 23 Sep 1996 12:48:22 -0700 To: Poul-Henning Kamp cc: Bill Fenner , "Chris Csanady" , freebsd-bugs@freebsd.org Subject: Re: Very disturbing boot block problems.. In-reply-to: Your message of "Mon, 23 Sep 96 12:23:16 PDT." <4314.843506596@critter.tfs.com> Date: Mon, 23 Sep 1996 12:48:10 PDT From: Bill Fenner Message-Id: <96Sep23.124822pdt.177476@crevenia.parc.xerox.com> Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <4314.843506596@critter.tfs.com> you write: >makes more sense now ? I know that the BIOS can't read tracks past 1023. The question is, when your whole disk is 1023 cylinders, and your a partition is in cylinders 0-34, why would the boot blocks print this message? (See http://www.freebsd.org/cgi/search.cgi?words=1023+%28BIOS+limit%29&source=freebsd-questions&source=freebsd-bugs&source=freebsd-hackers&source=freebsd-hardware&max=25&docnum=4) I'm planning to update fsdb to be able to print out all the data blocks that a file is in, which will presumably help diagnose why the bootblocks will fail to boot a particular file. Bill