From owner-freebsd-geom@FreeBSD.ORG Thu May 27 22:57:16 2010 Return-Path: Delivered-To: geom@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BEBE11065672 for ; Thu, 27 May 2010 22:57:16 +0000 (UTC) (envelope-from rick@svn.kiwi-computer.com) Received: from svn.kiwi-computer.com (174-20-208-22.mpls.qwest.net [174.20.208.22]) by mx1.freebsd.org (Postfix) with SMTP id 45EFB8FC0C for ; Thu, 27 May 2010 22:57:15 +0000 (UTC) Received: (qmail 83417 invoked by uid 2000); 27 May 2010 22:57:15 -0000 Date: Thu, 27 May 2010 17:57:15 -0500 From: "Rick C. Petty" To: Garrett Cooper Message-ID: <20100527225715.GE82995@kay.kiwi-computer.com> References: <20100527220241.GA82995@kay.kiwi-computer.com> <20100527223607.GC82995@kay.kiwi-computer.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: geom@freebsd.org Subject: Re: Getting useful diagnostics from geom(8) and friends X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rick-freebsd2009@kiwi-computer.com List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 22:57:16 -0000 On Thu, May 27, 2010 at 03:47:50PM -0700, Garrett Cooper wrote: > >> > >> I didn't run #4 (don't want gptboot on the appliance), but all of the > >> steps failed. > > > > Then how do you boot into FreeBSD?  You need to install the boot blocks or > > the loader(8) won't boot. > > We netboot :). PXE then? I'm curious why are you using the MBR strategy and not the GPT strategy? If you're PXE-booting, why have an MBR at all? > >> fdisk doesn't like these Western Digital drives for some whacky reason > >> when I specify fdisk -BIq /dev/ad4, etc... and only after I go in and > > > > What exactly do you mean by "doesn't like"? > > Sorry... should have included that detail... it's an on-and-off issue > where sometimes the drives do properly slice themselves and sometimes > they don't. Not sure why it's so twitchy... > > %fdisk -BIq /dev/ad4 > ******* Working on device /dev/ad4 ******* > fdisk: invalid fdisk partition table found > %ls /dev/ad4* > /dev/ad4 /dev/ad4s1 Is this the error case or the good case? It looks good to me. The error is because an invalid fdisk partition table existed prior to creating the one-slice-for-entire-disk MBR: % truncate -s 1m test % mdconfig -af test md1 % ls /dev/md1* /dev/md1 % fdisk -BIq /dev/md1 ******* Working on device /dev/md1 ******* fdisk: invalid fdisk partition table found % ls /dev/md1* /dev/md1 /dev/md1s1 % fdisk -BIq /dev/md1 ******* Working on device /dev/md1 ******* -- Rick C. Petty