Date: Thu, 16 Sep 2021 17:14:42 -0700 From: Mark Millard via freebsd-current <freebsd-current@freebsd.org> To: Freddie Cash <fjwcash@gmail.com> Cc: Alan Somers <asomers@freebsd.org>, freebsd-current <freebsd-current@freebsd.org> Subject: Re: zpool import: "The pool cannot be imported due to damaged devices or data" but zpool status -x: "all pools are healthy" and zpool destroy: "no such pool" Message-ID: <18C84EC4-D7D6-4288-949B-0157F52C95D2@yahoo.com> In-Reply-To: <CAOjFWZ5OZnvniVPBaF4SfC%2BpDTqxiB5-c0sFGAAcFj86m1YVAg@mail.gmail.com> References: <C312D693-8EAD-4398-B0CD-B134EB278F80.ref@yahoo.com> <C312D693-8EAD-4398-B0CD-B134EB278F80@yahoo.com> <CAOtMX2gYXYArkU%2Bo5M-j1CYSws7mqmrbwbJLF7=JiOEnd65wzg@mail.gmail.com> <D165B6EB-F0B6-41D8-8679-D07B70F62B09@yahoo.com> <CAOtMX2gyQRd_xx_h6X%2B6Uw0W5ZO4NtUvbRq4oqAX34VvKxY%2BBQ@mail.gmail.com> <37A64EF6-C638-41A6-9304-3C11550B811E@yahoo.com> <CAOjFWZ5OZnvniVPBaF4SfC%2BpDTqxiB5-c0sFGAAcFj86m1YVAg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Sep-16, at 16:27, Freddie Cash <fjwcash at gmail.com> wrote: >=20 > [message chopped and butchered, don't follow the quotes, it's just to = show some bits together from different messages] >=20 > On Thu, Sep 16, 2021 at 3:54 PM Mark Millard via freebsd-current = <freebsd-current@freebsd.org> wrote: > > > For reference, as things now are: > > >=20 > > > # gpart show > > > =3D> 40 937703008 nda0 GPT (447G) > > > 40 532480 1 efi (260M) > > > 532520 2008 - free - (1.0M) > > > 534528 937166848 2 freebsd-zfs (447G) > > > 937701376 1672 - free - (836K) > > > . . . > =20 > > > So you just want to clean nda0p2 in order to reuse it? Do "zpool = labelclear -f /dev/nda0p2" > > >=20 > >>=20 > >> I did not extract and show everything that I'd tried but > >> there were examples of: > >>=20 > >> # zpool labelclear -f /dev/nda0p2 > >> failed to clear label for /dev/nda0p2 >=20 > The start of the problem looked like (console context, > so messages interlaced): >=20 > # zpool create -O compress=3Dlz4 -O atime=3Doff -f -tzopt0 zpopt0 = /dev/nvd0 > GEOM: nda0: the primary GPT table is corrupt or invalid. > GEOM: nda0: using the secondary instead -- recovery strongly advised. > cannot create 'zpopt0': no such pool or dataset > # Sep 16 12:19:31 CA72_4c8G_ZFS ZFS[1111]: vdev problem, zpool=3Dzopt0 = path=3D/dev/nvd0 type=3Dereport.fs.zfs.vdev.open_failed >=20 > The GPT table was okay just prior to the command. > So I recovered it. >=20 > It looks like you're trying to use a disk partition for a ZFS pool = (nda0p2), but then you turn around and use the entire drive (nvd0) for = the pool which clobbers the GPT. I'd not noticed my lack of a "p2" suffix. Thanks. Explains how I got things messed up, with GPT and zfs conflicting. (Too many distractions at the time, I guess.) > You need to be consistent in using partitions for all commands. Yep: dumb typo that I'd not noticed. > You're also mixing up your disk device nodes for the different = commands; while they are just different names for the same thing, it's = best to be consistent. Once I had commands failing, I expectly tried alternatives that I thought should be equivalent in case they were not in some way. Not my normal procedure. > GEOM is built out of layers (or more precisely, "containers" as it = specifies a new start and end point on the disk), which is very = powerful. But it's also very easy to make a mess of things when you = start accessing things outside of the layers. :) And ZFS labelclear = option is the nuclear option that tends to remove everything = ZFS-related, and everything GPT-related; although I've never seen it = used on a partition before, usually just the disk. > Best bet in this situation is to just zero out the entire disk (dd = if=3D/dev/zero of=3D/dev/nda0 bs=3D1M), and start over from scratch. = Create a new GPT. Create new partitions. Use the specific partition = with the "zpool create" command. I ended up writing something less than a full 480 GiByte of writes. It preserved /dev/nda0p1 . =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18C84EC4-D7D6-4288-949B-0157F52C95D2>