SOLVED Is the entire integrity of a RAIDz2 pool contingent upon the persistence of a SLOG ..?

[TrumanHW]

I thought my SLOG was bad per reporting -- pulled it out when I was installing a new CPU and RAM ... upon restarting ZFS, it no longer saw any pool.

What's more -- it not only sees no pool, but even searching for a pool finds no results. Granted, this was from the GUI.

Would CLI commands potentially force mount the pool .. ?

 

[Etorix]

In the event of an unclean shutdown, the SLOG is indeed required for data integrity.
ZFS cannot import a pool is a non-redundant member is absent.
Put the SLOG back in, remove it from the pool through the GUI, and then physically remove the SLOG.

If ZFS cannot detect and import the pool with the SLOG back in place, or you've already reformatted the SLOG drive, you're in trouble…

 

[sretalla]

You can tell zfs to import a pool with missing devices (L2ARC or SLOG)... zpool import -m poolname

from https://illumos.org/man/1M/zpool :

Code:

             -m      Allows a pool to import when there is a missing log device.
                     Recent transactions can be lost because the log device will
                     be discarded.

It may be that you also need the -f switch to make that work (although the documentation says not).

After importing via CLI, the pool will not be visible in the GUI, so you'll need to export it in the CLI and then import from the GUI to put it back to normal.

 

[TrumanHW]

That was exactly what I'd needed, sretalla.
I should've updated this thread ... as I found a post by (a Moderator, Ericloewe) which also suggested using:
zpool import -m pool name

...which promptly mounted the pool in perfect condition. :)

Greatly appreciated both of your replies as well.