Date: Tue, 22 Sep 2009 17:12:18 -0700 From: Stephen Hurd <shurd@sasktel.net> To: marcel@FreeBSD.org Cc: freebsd-geom@FreeBSD.org Subject: Re: kern/138891: [geom] GEOM_PART_* fails with sliced gstripe Message-ID: <4AB967E2.8010207@sasktel.net> In-Reply-To: <200909172032.n8HKWEUG021155@freefall.freebsd.org> References: <200909172032.n8HKWEUG021155@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
marcel@FreeBSD.org wrote: > Your disk partitioning is invalid. You cannot have both a MBR and > a BSD disk label in the same place and independently of each other. > ace# fdisk /dev/stripe/raid0 > ace# bsdlabel /dev/stripe/raid0 > If you look closely, FreeBSD 7.2 will use the MBR on /dev/stripe/raid0 > and the BSD disklabel on /dev/stripe/raid0s4. However, since a BSD > disklabel also embeds a MBR, FreeBSD 8.0 will correctly prefer the > BSD disklabel on /dev/stripe/raid0. However, the BSD disk label is > not the one that should be used. > Fix the problem by wiping out the second sector on the disk. > BTW: the problem is caused by creating a dangerously dedicated > installation. It's known to be broken and should not be used. > FYI, > After wiping out the second sector or the drive (dd seek=1 count=1 if=/dev/zero of=/dev/stripe/raid0) fdisk now reports "invalid fdisk partition table found" but GEOM_PART_* still does not locate the a slice and the b/d slices will not mount. I have never had a /dev/stripe/raid0s* node, just /dev/stripe/raid0[a-d]. Is there any way to fix this short of a full backup/restore? (The reason I used DD mode here was that since the gstripe wouldn't be visible to the BIOS -- or anything other than FreeBSD -- slicing seemed silly.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AB967E2.8010207>