Date: Thu, 27 May 2010 15:58:13 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: rick-freebsd2009@kiwi-computer.com Cc: geom@freebsd.org Subject: Re: Getting useful diagnostics from geom(8) and friends Message-ID: <AANLkTincQ7kdrBMsGu0r8RKjXO2u0H7EMrhOk2_ZPK85@mail.gmail.com> In-Reply-To: <20100527225715.GE82995@kay.kiwi-computer.com> References: <AANLkTimg6CKc0RTNpd-0oI5MegjVPd0eiS5pQCj-chvV@mail.gmail.com> <20100527220241.GA82995@kay.kiwi-computer.com> <AANLkTinRhDF2XmyvvbqlhtP2gwsnOiOxv-mKTCAx4feb@mail.gmail.com> <20100527223607.GC82995@kay.kiwi-computer.com> <AANLkTinaGs2bQlAv7BLy96B4SDc0mv4J4lqS78Zg_RRs@mail.gmail.com> <20100527225715.GE82995@kay.kiwi-computer.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 27, 2010 at 3:57 PM, Rick C. Petty <rick-freebsd2009@kiwi-computer.com> wrote: > 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? =A0You need to install the boot blo= cks 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 reaso= n >> >> 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 =A0 =A0 =A0/dev/ad4s1 > > Is this the error case or the good case? =A0It looks good to me. =A0The e= rror > 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 =A0 /dev/md1s1 > % fdisk -BIq /dev/md1 > ******* Working on device /dev/md1 ******* Sorry.. yes, this was the positive case. Thanks, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTincQ7kdrBMsGu0r8RKjXO2u0H7EMrhOk2_ZPK85>