This content has been marked as final. Show 3 replies
Eventually, a pool that is imported and active would be unhappy that all of its device paths had been removed.
Next time, I think I would recommend this if you are going to change controller slots on root pool devices:
1. Boot from media
2. Review the zpool import info for rpool but don't import it
3. Change the controller slot
4. Import the root pool to see if the device info has been updated
5. If something goes wrong, change the hardware back.
6. If the root pool status is okay, reboot.
For non-root pools, you can export them during multiuser mode and change the hardware and the pool should handle the device changes upon import, but I would test this first on dummy pools with your hardware.
I have seen many painful experiences changing hardware under pools.
Disks are identified both by their path and by their device ID, if available. On systems where device ID information is available, this
identification method allows devices to be reconfigured without updating ZFS. Because device ID generation and management can vary
by system, export the pool first before moving devices, such as moving a disk from one controller to another controller. A system event, such as a firmware update or other hardware change, might change the device IDs in your ZFS storage pool, which can cause the
devices to become unavailable.