Mirrored ZPOOL with ZFS Boot on Root FAIL … and Fix

Mirrored ZPOOL with ZFS Boot on Root FAIL … and Fix

iX SpecOps: MIRRORED ZPOOL ROOT/BOOT FIX

Description: SINGLE VDEV BOOT ZPOOL FOR PRODUCTION SYSTEM

The problem with Prometheus is that ada4 had another pool on it, tank1. Hence the tank2 zpool name, I suspect. Since somebody did not destroy this root zpool with bootcode when bootcode & gpt partitioning
was done on the Intel ada0/1 pair, when the Intel RAID broke or was not discovered first, the system booted from the broken ada3s2 partition.

In fact, chances are that this occured many times & nearly every device in the system, which is full of unmatched drives of various sizes with no apparently plan.

zpool import
pool: tank1
id: 13323130829716330915
state: ONLINE
status: The pool was last accessed by another system.
action: The pool can be imported using its name or numeric identifier and
the '-f' flag.
see: http://illumos.org/msg/ZFS-8000-EY
config:
tank1 ONLINE
ada4p2 ONLINE

The Fix:

It was a correct assumption to attempt adding the device to the existing 30GB zpool, called tank2. Various permutations of this approach were executed.

In addition, several methods were used to copy the existing partitions onto the second disk. This failed in the same fashion as directly attaching the drive to the existing zpool.