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"

2021-09-16 Thread George Michaelson
GPT has a back-of-disk structure. Is the problem here that wiping GPT only at front, leaves emergency state at back which is detected, before the ZFS initialisation system can decide you don't want to use that?

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"

2021-09-16 Thread Mark Millard via freebsd-current
On 2021-Sep-16, at 16:27, Freddie Cash wrote: > > [message chopped and butchered, don't follow the quotes, it's just to show > some bits together from different messages] > > On Thu, Sep 16, 2021 at 3:54 PM Mark Millard via freebsd-current > wrote: > > > For reference, as things now are:

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"

2021-09-16 Thread Freddie Cash
[message chopped and butchered, don't follow the quotes, it's just to show some bits together from different messages] 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: > > > > > > # gpart show > > > =>

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"

2021-09-16 Thread Mark Millard via freebsd-current
On 2021-Sep-16, at 15:16, Alan Somers wrote: > On Thu, Sep 16, 2021 at 4:02 PM Mark Millard wrote: > > > On 2021-Sep-16, at 13:39, Alan Somers wrote: > > > On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current > > wrote: > > What do I go about: > > > > QUOTE > > # zpool

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"

2021-09-16 Thread Tomoaki AOKI
On Thu, 16 Sep 2021 13:01:16 -0700 Mark Millard via freebsd-current wrote: > What do I go about: > > QUOTE > # zpool import >pool: zopt0 > id: 18166787938870325966 > state: FAULTED > status: One or more devices contains corrupted data. > action: The pool cannot be imported due to

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"

2021-09-16 Thread Mark Millard via freebsd-current
On 2021-Sep-16, at 13:26, joe mcguckin wrote: > I experienced the same yesterday. I grabbed an old disk that was previously > part of a pool. Stuck it in the chassis and did ‘zpool import’ and got the > same output you did. Mine was a single-disk pool. I use zfs just in order to use bectl,

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"

2021-09-16 Thread Alan Somers
On Thu, Sep 16, 2021 at 4:02 PM Mark Millard wrote: > > > On 2021-Sep-16, at 13:39, Alan Somers wrote: > > > On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current < > freebsd-current@freebsd.org> wrote: > > What do I go about: > > > > QUOTE > > # zpool import > >pool: zopt0 > >

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"

2021-09-16 Thread Mark Millard via freebsd-current
On 2021-Sep-16, at 13:39, Alan Somers wrote: > On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current > wrote: > What do I go about: > > QUOTE > # zpool import >pool: zopt0 > id: 18166787938870325966 > state: FAULTED > status: One or more devices contains corrupted

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"

2021-09-16 Thread Mark Millard via freebsd-current
On 2021-Sep-16, at 13:01, Mark Millard wrote: > What do I go about: > > QUOTE > # zpool import > pool: zopt0 > id: 18166787938870325966 > state: FAULTED > status: One or more devices contains corrupted data. > action: The pool cannot be imported due to damaged devices or data. > see:

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"

2021-09-16 Thread Alan Somers
On Thu, Sep 16, 2021 at 2:04 PM Mark Millard via freebsd-current < freebsd-current@freebsd.org> wrote: > What do I go about: > > QUOTE > # zpool import >pool: zopt0 > id: 18166787938870325966 > state: FAULTED > status: One or more devices contains corrupted data. > action: The pool

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"

2021-09-16 Thread joe mcguckin
I experienced the same yesterday. I grabbed an old disk that was previously part of a pool. Stuck it in the chassis and did ‘zpool import’ and got the same output you did. Since the other drives of the pool were missing, the pool could not be imported. zpool status reports 'everything ok’