ZFS faulted zfs pool from nowhere

Hello

FreeBSD 12.2
There were 2 pools. zroot on ada0 vdev and zdata on da0 vdev.
da0 is a hardware raid.

Nobody changed anything in zfs pools configuration. And when ordinary reboot of server I got this view.
I don't know how 13003137893086410532 pool appeared with the same name.
I can boot using bootonly flash disk and import real zroot and zdata pools and files are not damaged. I checked it by scrubbing. Hardware is worked correctly. Of course, when I try to import pool by id 13003137893086410532 I get error even with -f flag.

Early system booted from zroot and now it cannot boot correctly.

The question is how to remove 13003137893086410532 this not-pool without damaging da0 and zdata pool and why this happened?

Code:
pool: zroot
     id: 13003137893086410532
  state: FAULTED
 status: The pool was last accessed by another system.
 action: The pool cannot be imported due to damaged devices or data.
        The pool may be active on another system, but can be imported using
        the '-f' flag.
   see: [URL]http://illumos.org/msg/ZFS-8000-EY[/URL]
 config:

        zroot        FAULTED  corrupted data
          da0        ONLINE

   pool: zdata
     id: 9903107894708964808
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

        zdata       ONLINE
          da0p1     ONLINE

   pool: zroot
     id: 457627818049971507
  state: ONLINE
 action: The pool can be imported using its name or numeric identifier.
 config:

        zroot       ONLINE
          ada0p3    ONLINE
[

this is partition configuration from gpart backup
Code:
[root:/home/ip]# cat gpart.ada0.backup
GPT 128
1            efi        40      1600
2   freebsd-swap      2048  33554432 zfsswap
3    freebsd-zfs  33556480 943216640 zfssys
[root:/home/ip]# cat gpart.da0.backup
GPT 128
1   freebsd-zfs        2048 46871322624 zfsdata
 
I've already zpool destroy system zroot pool with id 457627818049971507. "Magic" pool zroot with id 13003137893086410532 is still in list of zpool import

Where located information about pools? I'll find and remove this manually in disk editor.
 
from man zpool
cachefile=path | none

Controls the location of where the pool configuration is cached.
Discovering all pools on system startup requires a cached copy of the
configuration data that is stored on the root file system. All pools
in this cache are automatically imported when the system boots. Some
environments, such as install and clustering, need to cache this
information in a different location so that pools are not
automatically imported. Setting this property caches the pool
configuration in a different location that can later be imported with
"zpool import -c". Setting it to the special value "none" creates a
temporary pool that is never cached, and the special value '' (empty
string) uses the default location.
 
from man zpool
cachefile=path | none

Controls the location of where the pool configuration is cached.
Discovering all pools on system startup requires a cached copy of the
configuration data that is stored on the root file system. All pools
in this cache are automatically imported when the system boots. Some
environments, such as install and clustering, need to cache this
information in a different location so that pools are not
automatically imported. Setting this property caches the pool
configuration in a different location that can later be imported with
"zpool import -c". Setting it to the special value "none" creates a
temporary pool that is never cached, and the special value '' (empty
string) uses the default location.

I can boot using bootonly flash disk and import real zroot and zdata pools and files are not damaged. I checked it by scrubbing. Hardware is worked correctly.
 
I can boot using bootonly flash disk and import real zroot and zdata pools and files are not damaged.

Is there any other device?

zpool-labelclear.8 — OpenZFS documentation

FreeBSD 12.2

<https://www.freebsd.org/cgi/man.cgi?query=zpool-labelclear&manpath=FreeBSD+12.2-RELEASE> finds no equivalent in FreeBSD 12.2.

I checked it by scrubbing. Hardware is worked correctly.

There may be part of a device that's error-prone but not found by scrubbing.
 
Back
Top