Date: Tue, 22 Feb 2005 21:48:37 -0500 From: James Snow <snow@teardrop.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: freebsd-geom@freebsd.org Subject: Re: Hardcoding gmirror provider Message-ID: <20050223024837.GA41478@teardrop.org> In-Reply-To: <20050222235852.GW9291@darkness.comp.waw.pl> References: <16901.26814.588055.457273@satchel.alerce.com> <16902.27236.71619.138367@satchel.alerce.com> <20050206191209.GC1080@darkness.comp.waw.pl> <16902.28195.6589.299894@satchel.alerce.com> <20050211133917.GA45990@engelschall.com> <16923.20768.336451.133236@satchel.alerce.com> <86k6p0mj7x.fsf@xps.des.no> <20050222234728.GV9291@darkness.comp.waw.pl> <20050222235852.GW9291@darkness.comp.waw.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Feb 23, 2005 at 12:58:52AM +0100, Pawel Jakub Dawidek wrote: > > ...and metadata at the begining of the provider still doesn't fix 'c' > partition problem and 'a' partition which starts at sector 0, which is > the default start offset in sysinstall. Is this the C partition problem you refer to? bsdlabel: partition c doesn't cover the whole unit! bsdlabel: An incorrect partition c may cause problems for standard system utilities Could this possibly be at the root of my boot problem: disk1s1: FFS bad disklabel disk2s1: FFS bad disklabel It only seems to be a problem if I try to use slices as gmirror providers and shrink them to avoid the last sector collision with the whole disk. -Snow
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050223024837.GA41478>