TL;DR
Pool will not import after power loss: zpool import -f, then -F if you must rewind txgs, then zpool scrub.
After a power cut the pool is often still on the disks but zpool status is empty: it was left dirty-exported, or the host booted without it. Do not zpool create on those disks.
See what is there
| |
Lists importable pools by name (VOL1 below) and whether they are FAULTED / UNAVAIL.
Import
| |
-f means “I know it might still look imported elsewhere”. That is the usual crash case: ZFS thinks the other side still holds it.
If -f is not enough because the last txgs were half-written:
| |
-F rewinds to an earlier consistent txg. You can lose the last seconds of writes. That is better than a pool that will not mount.
Dry-run:
| |
Afterwards: scrub
| |
Scrub confirms the rewind did not leave checksum errors. Let it finish before you delete “just in case” snapshots.
Do not
zpool createon the samesdXdevices wipes the labels.-Fis not the first knob: try-ffirst.- If the pool is the root (
rpool/ Proxmoxbpool), import from live media, not from the system that will not boot.
See also: replacing disks, basic commands.