From owner-freebsd-current@FreeBSD.ORG Sun Jun 29 23:35:15 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 072C037B401 for ; Sun, 29 Jun 2003 23:35:15 -0700 (PDT) Received: from water-ox.its.caltech.edu (SteeleMR-loadb-NAT-49.caltech.edu [131.215.49.69]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68C7443FAF for ; Sun, 29 Jun 2003 23:35:14 -0700 (PDT) (envelope-from jd@its.caltech.edu) Received: from fire-dog (fire-dog [192.168.1.4]) by water-ox-postvirus (Postfix) with ESMTP id B5C4026AC4B for ; Sun, 29 Jun 2003 23:35:13 -0700 (PDT) Received: from water-ox ([192.168.1.10]) by fire-dog (MailMonitor for SMTP v1.2.2 ) ; Sun, 29 Jun 2003 23:35:12 -0700 (PDT) Received: from sue.its.caltech.edu (sue.its.caltech.edu [131.215.48.175]) by water-ox.its.caltech.edu (Postfix) with ESMTP id 2A0B326AC4B for ; Sun, 29 Jun 2003 23:35:12 -0700 (PDT) Received: (from jd@localhost) by sue.its.caltech.edu (8.12.9/8.12.8) id h5U6ZBRD015532 for freebsd-current@freebsd.org; Sun, 29 Jun 2003 23:35:11 -0700 (PDT) Date: Sun, 29 Jun 2003 23:35:11 -0700 From: Systems Engineering To: freebsd-current@freebsd.org Message-ID: <20030630063511.GB13663@sue.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, hits=-5.0 tagged_above=-100000.0 required=5.0 tests=FROM_CALTECH X-Spam-Level: Subject: Disk Geometry Error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jun 2003 06:35:15 -0000 I am attempting an installation via the 5.1-R iso. During the partitioning process, fdisk reports that the detected disk geometry is probably incorrect. Subsequently, I attempt to specify the geometry reported by bios (CSH:19158,255,16). This geometry is, however, rejected. I have tried some variations, including the "sane" proposal that fdisk makes after it reports that the detected disk geometry is invalid. fdisk accepts them but this does not produce a bootable system (not surprising). Any ideas? Thanks.