Managing the ACRECOVERY Partition

User-facing behavior documented in The AcreetionOS Recovery Environment; this page is the operator view.

Provisioning recap

Created during install when unpartitioned space allowed (~800 MiB target, guards never touch existing partitions/filesystems):

  • Self-contained ext4 labeled ACRECOVERY

  • Own GRUB install + gzipped kernel/initramfs payloads

  • Main GRUB chainloads it: F9 hotkey entry + recordfail auto-failover

Inspect yours:

lsblk -f | grep -i acrecovery
sudo blkid | grep -i acreetion
cat /boot/grub/grubenv | grep recordfail

Sync mechanics

A pacman hook refreshes partition copies whenever linux/kernel-related packages change — zero-maintenance by design. Manual trigger after exotic operations (hand-built kernel etc.):

sudo acreetion-recovery-setup --sync-kernels

Modes available: --auto (standard provision) · --device <part> (explicit target) · --sync-kernels (refresh payloads only).

Retrofit onto existing installs

Live ISO or running system:

sudo acreetion-recovery-setup --auto

Requires contiguous free space (it carves, never shrinks existing FS). No space? The ISO-based Recovery Environment remains fully available as fallback tooling.

Space-constrained machines

Skip provisioning freely — it’s insurance, not requirement. Existing one can be removed like any partition afterwards (update GRUB config; failover entries vanish cleanly).

Verification drill (quarterly)

  1. Boot it deliberately once via F9/menu

  2. Run its Network setup → confirm online capability

  3. Timeshift browse → see your snapshot list

  4. Reboot normally; grub-editenv /boot/grub/grubenv list → expect no stuck recordfail

Untested recovery = decorative recovery.