From owner-freebsd-current Thu Jul 20 8:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id D89C437BDA1; Thu, 20 Jul 2000 08:46:42 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e6KFkaV03018; Thu, 20 Jul 2000 08:46:36 -0700 (PDT) Date: Thu, 20 Jul 2000 08:46:36 -0700 (PDT) From: Doug White To: Doug Barton Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: No /boot/loader In-Reply-To: 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, 19 Jul 2000, Doug Barton wrote: > > Disk geometry stuffup, or a 'real' disk error. > > Well, I put my money on real disk error, but only because it > vindicates my position that we shouldn't have switched to this new kind of > disk in the first place. > > As for geometry, I tried both with and without "dangerously > dedicated." My understanding was that if I used the dos partition entry > method that we should be able to pick up the geometry correctly, but > should I try the old dos fdisk trick as well? Also, would the adaptec > setting to translate >1G be affecting this? It's on currently, which it is > on all my other motherboards of similar vintage. Your boot disk is now *required* (or will be very very soon) to have a proper slice table in -CURRENT; dedicated disks are deprecated in order to get a smarter boot0. Speaking of boot0 you might try using boot0cfg to force packet mode. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message