From owner-freebsd-stable Mon May 17 12:41: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ceia.nordier.com (c2-31-dbn.dial-up.net [196.34.155.159]) by hub.freebsd.org (Postfix) with ESMTP id C0AE515330 for ; Mon, 17 May 1999 12:40:47 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA06836; Mon, 17 May 1999 21:39:35 +0200 (SAST) From: Robert Nordier Message-Id: <199905171939.VAA06836@ceia.nordier.com> Subject: Re: disk error In-Reply-To: <199905170703.JAA29192@obsidian.noc.dfn.de> from Jens Schweikhardt at "May 17, 1999 09:03:38 am" To: schweikh@noc.dfn.de (Jens Schweikhardt) Date: Mon, 17 May 1999 21:39:23 +0200 (SAST) Cc: rnordier@nordier.com (Robert Nordier), adepoo@tamnet.com.mx, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # > I have the following error at boot up > # > > # > Disk error 0x1 (lba=0x299cd0) > # > No /boot/loader > # A disk error 0x1 indicates that at attempt was made to read above disk > # cylinder 1023 using the BIOS. > > That's an interesting and helpful bit of information. Is there enough > room in that particular stage to print a message to this effect? Even if > 0x1 is not guaranteed to be caused by exceeding the cyl limit, a hint > like "Disk error 0x1 (lba=0x299cd0), may be caused by read beyond cyl > 1023" > > With disks getting bigger almost everyday and BIOS limits cast in stone > I expect this type of error becoming ubiquitous soon... As boot2 must fit into 7168 bytes of preallocated space, there's unfortunately not room for anything less cryptic. But some discussion of the diagnostics on the man page would probably be good idea. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message