Date: Tue, 17 Nov 2009 07:57:27 +0100 From: Stefan Bethke <stb@lassitu.de> To: Jeremy Thornhill <jeremy.thornhill@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: "corrupt or invalid GPT" when attempting to import Solaris ZFS pool (8.0-RC3) Message-ID: <1DE2E5E5-B6A4-4870-A346-ABC1CD20EE34@lassitu.de> In-Reply-To: <b77635950911162010t511ca570v32880acb5e3e25a3@mail.gmail.com> References: <b77635950911162010t511ca570v32880acb5e3e25a3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 17.11.2009 um 05:10 schrieb Jeremy Thornhill: > I've been testing the procedure with a USB drive which was allocated > as a single pool under Solaris. It's the correct filesystem version > (13). I export the pool from the Solaris box, and then attempt to > import it on the FreeBSD box. Unfortunately, I get the following > error, and the pool is not able to be imported: >=20 > GEOM: da0: corrupt or invalid GPT detected. > GEOM: da0: GPT rejected -- may not be recoverable. What error are you getting from zpool import? I believe the GEOM error is due to Solaris adding the GPT partition = table to the start of the device, but not the end. GEOM requires both = copies to be present and identical, IIRC. Since the pool fills the = device, there's no space at the end, so adding the second copy is not an = option. You could try destroying the first GPT copy by zeroing the first 34 = blocks. I'm not sure what Solaris will make of the pool after this, = though: # dd if=3D/dev/zero of=3D/dev/da0 count=3D34 However, I'd expect this to have no effect on zpools ability to import = the pool. HTH, Stefan --=20 Stefan Bethke <stb@lassitu.de> Fon +49 151 14070811
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1DE2E5E5-B6A4-4870-A346-ABC1CD20EE34>