SystemRescueCd guide
SystemRescueCd ZFS: Recovery Planning and Import Safety
ZFS rescue work deserves extra caution because importing a pool can change state. Before any import, identify the disks, the expected pool, the host history and the safest read-only path available.
Why ZFS recovery needs a different mindset
ZFS combines filesystem and volume-management behavior. Pool imports, feature flags and device availability can affect state, so treat discovery and recovery as separate phases.
Inventory first
Record the expected pool name, disk identifiers, controller setup, prior host configuration and whether the pool was cleanly exported. Avoid forcing an import simply because the pool does not appear immediately.
Prefer read-only inspection where possible
If your goal is data recovery, reduce unnecessary writes and avoid upgrading pool features during an emergency. A rescue environment should help you access data, not silently change compatibility.
When SystemRescueCd ZFS is not enough
Hardware RAID layers, damaged devices, encryption or missing ZFS modules may require a more specialized environment. At that point, preserve the disks and move the work to a controlled recovery setup.