- rpool not on slice 0 but on slice 2
- bug in Solaris when doing such a mirror and “just” doing a reboot <- this is the real issue, it seems Solaris can not handle a change of the name of the underlying device for a rpool, as just moving the partitioning to slice 0 is not fixing the panic.
# boot from network (or an alternate pool which was not yet moved), import/export the pools, boot from the pools
boot net -
# go to shell
# if needed: change the partitioning so that slice 0 has the same values as slice 2 (respectively make sure the rpool is in slice 0)
zpool import ‑R /tmp/yyy rpool
zpool export rpool