SEC.01

The playbook

The run starts read-only: the recon probes decide what happens next. The steps that follow are adapted to the distribution and state found — a real machine is rarely clean.

1. 01reconZFS already present (tools + module) + version
2. 02recondo the disks exist? consistent sizes?
3. 03reconsignature on a disk = data → NEVER overwrite
4. 04reconsystem disk to exclude; does a pool with the same name already exist?
5. 05reconstable by-id paths of the disks (to use for the pool)
6. 06recondistro and kernel; Secure Boot active (unsigned DKMS module → blocking)
7. 07reconRAM: 2 GB minimum recommended for ZFS
8. 08actPrepare the ZFS repository (Debian and RHEL only)verify
9. 09actInstall ZFSverify
10. 10actLoad the moduleverify
11. 11actSimulate the pool creationverify
12. 12actCreate the ${pool_name} pooldestructiveverify
13. 13actCheck the mountverify

SEC.02

What it verifies

Each step ships its own check. The run only moves on when the check passes, so what the recipe reports as done is what is actually on the server.

1. 01verifyPrepare the ZFS repository (Debian and RHEL only)Verified byrpm -q zfs-release 2>/dev/null || apt-cache policy zfsutils-linux | head -3
2. 02verifyInstall ZFSVerified bycommand -v zpool
3. 03verifyLoad the moduleVerified bylsmod | grep -c '^zfs '
4. 04verifySimulate the pool creationVerified byzpool list -H -o name ${pool_name} 2>/dev/null || echo absent
5. 05verifyCreate the ${pool_name} poolVerified byzpool status -x ${pool_name}
6. 06verifyCheck the mountVerified byzfs get -H -o value mounted ${pool_name}

SEC.03

Guardrails

Non-negotiable instructions the run must respect, whatever it finds on the server.

SEC.04

Variables

What you choose before launching — the recipe fills in the rest.

SEC.05

How a recipe runs in Servor

Servor is zero-knowledge: the platform cannot execute anything on its own. When you launch this recipe, a run reads the reconnaissance, plans the steps and asks for your approval. Each approved command is signed by your browser — with a key the server never sees — then relayed verbatim to the agent, which verifies the signature locally before executing.

SEC.06

Deploy on Servor button

Maintain ZFS pool or a project that needs it? Put this button in your README or on your site: one click and your users install it on their own server.

SEC.07

More storage & backup recipes

1. 01Swap fileCreates a persistent swap file of the chosen size. Destructive: modifies /etc/fstab.
2. 02restic backupsrestic + a scheduled, encrypted backup of a folder to a repository.
3. 03MinIOS3-compatible MinIO object storage via Docker, local-only. Community project archived: frozen image.
4. 04Garage (S3 storage)Garage (Deuxfleurs) S3-compatible object storage via Docker, single-node and local-only, with a first bucket and its key. Maintained alternative to MinIO.
5. 05Samba shareSamba file server (SMB). Destructive: creates a share and a user.