OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
apps-services high common DISPUTE

Get a working rollback safety net when the boot menu has no snapshot entries

archomarchyendeavouroscachyosmanjarodesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

Checked against this Omarchy 4 workstation (omarchy 4.0.2-1, snapper 0.13.1-3, limine-snapper-sync 1.31.0-1, kernel 7.1.9) and against the cited Snapper and Timeshift wiki pages plus the Limine wiki page, all fetched as raw wikitext. The generic structure held and I kept it: recover first with pacman -U from /var/cache/pacman/pkg then build the net, the filesystem triage, grub-btrfs plus grub-btrfsd.service for GRUB, rsync-mode Timeshift for non-btrfs, snap-pac for automatic pre/post snapshots, and the closing point that a system rollback is not a /home backup. Timeshift's hard cronie dependency is confirmed from pacman -Si timeshift, matching the wiki note. The Omarchy branch was wrong. yay -S limine-snapper-sync does not apply here: I confirmed with pacman -Qi that limine-snapper-sync 1.31.0-1 is installed from the omarchy repo (Server = https://pkgs.omarchy.org/stable/$arch in /etc/pacman.conf), not the AUR, and the whole net is already configured. I read /usr/share/omarchy/install/config/snapper.sh, which installs /etc/snapper/configs/root from /usr/share/omarchy/default/snapper/root and enables snapper-cleanup.timer and limine-snapper-sync.service while disabling snapper-timeline.timer. systemctl is-enabled on this machine confirms enabled, enabled, disabled. limine-list printed a live Snapshots submenu with two real entries, so the symptom as written cannot occur on a stock Omarchy 4 and I rewrote it to send the reader to limine-list first. I read /usr/share/omarchy/bin/omarchy-snapshot (create and restore, the latter calling limine-snapper-restore) and confirmed /usr/bin/omarchy-update line 36 calls omarchy-snapshot create, so the snap-pac claim needed an Omarchy exception: pacman -Q snap-pac reports the package is not installed. The sudo mkinitcpio -P line is correct where it stands, in the plain-Arch GRUB branch, but it needed labelling, because /etc/mkinitcpio.d/ is empty here and /usr/bin/mkinitcpio line 986 dies with No presets found in /etc/mkinitcpio.d. I added the wiki caveat the record omitted, that grub-btrfs-overlayfs is a runtime hook with no systemd unit and is incompatible with a systemd initramfs (Snapper wiki, Booting into read-only snapshots), which matters because the stock /etc/mkinitcpio.conf on this machine ships systemd in HOOKS. I also recorded that Omarchy already solves the overlay problem: btrfs-overlayfs from limine-mkinitcpio-hook is the last hook in /etc/mkinitcpio.conf.d/omarchy_hooks.conf, which is what the Limine wiki tells you to add after filesystems. The pacman -U recovery step is safe on Omarchy and I said so, having read /usr/bin/omarchy-update-pacman-guard, which aborts only when both sync and sysupgrade flags are present. NOT exercised: I have no sudo, so I ran no snapper command, took no snapshot, restored nothing, and did not boot a snapshot entry. The GRUB, rEFInd and Timeshift branches could not be tested on this machine at all and rest on the wiki. The danger field was left unchanged because both of its claims, the subvolid trap after a restore and Timeshift btrfs mode ignoring the exclude list, are confirmed in the Snapper and Timeshift wikis respectively. All three cited sources resolve and support what the record draws from them, so nothing is removed.

The cause above was rewritten on 2026-09-11 to match this note; the fix was corrected by the audit itself.
RISK

Converting an existing installation to a snapshot-friendly btrfs layout means moving subvolumes and reinstalling/reconfiguring the bootloader. Get it wrong and the machine does not boot. In particular, if genfstab wrote a subvolid= option for / or /home, remove it or you will be unable to boot *after* restoring a snapshot. Do that work from a live ISO with a full backup already taken, never on a machine you need working in an hour. timeshift --restore overwrites system files in place. Read the excluded/included paths in /etc/timeshift/timeshift.json before running it, and note that Timeshift in btrfs mode ignores the exclude list entirely.

Symptom

An update broke the desktop and every guide says "boot the snapshot from the boot menu", but there are no snapshot entries: the machine uses GRUB or systemd-boot, or the root filesystem is ext4, or it is a plain Arch/EndeavourOS install that was never set up for snapshots. snapper -c root list errors with Unknown config, or snapper is not installed at all.

On a stock Omarchy 4 install this should not happen. snapper and limine-snapper-sync are installed and configured out of the box and limine-snapper-sync writes a Snapshots submenu into the Limine menu, so run limine-list and sudo snapper -c root list before concluding you have no safety net.

Cause

Bootable snapshot rollback is not one kernel feature. It needs three things together: btrfs subvolumes, a snapshot tool (snapper), and a bootloader integration that writes menu entries for those snapshots. Miss any one of them and there is nothing to boot.

Omarchy 4 ships all three. snapper and limine-snapper-sync come from Omarchy's own pacman repo at https://pkgs.omarchy.org/stable/$arch, /usr/share/omarchy/install/config/snapper.sh installs /etc/snapper/configs/root from the /usr/share/omarchy/default/snapper/root template (root subvolume only, NUMBER_LIMIT="5", TIMELINE_CREATE="no"), and it enables snapper-cleanup.timer and limine-snapper-sync.service while disabling snapper-timeline.timer. omarchy update calls omarchy-snapshot create before it upgrades anything, and omarchy-snapshot restore hands off to limine-snapper-restore. The read-only-snapshot problem is handled too: the btrfs-overlayfs hook from limine-mkinitcpio-hook is the last entry in /etc/mkinitcpio.conf.d/omarchy_hooks.conf.

Everywhere else you have to build it. On GRUB you need grub-btrfs, on rEFInd refind-btrfs, on Limine limine-snapper-sync from the AUR. On a non-btrfs root none of it applies and you need file-level backups instead.

Fix

**Recover first, then build the net.** With no snapshot to boot, roll back the specific breakage from the pacman cache:


ls /var/cache/pacman/pkg/ | grep <package>
sudo pacman -U /var/cache/pacman/pkg/<package>-<older-version>-x86_64.pkg.tar.zst

Omarchy's ALPM guard does not block this. /usr/bin/omarchy-update-pacman-guard aborts a transaction only when the pacman command line carries both a sync and a sysupgrade flag, so pacman -U and pacman -S --needed run normally while pacman -Syu is refused in favour of omarchy update.

If the system will not boot at all, boot the Arch or Omarchy ISO, mount and arch-chroot in, and do the same from there.

**On Omarchy 4, check what you already have before installing anything:**


pacman -Q snapper limine-snapper-sync
sudo snapper -c root list
limine-list
systemctl is-enabled limine-snapper-sync.service snapper-cleanup.timer

limine-list prints the boot menu tree, including a Snapshots submenu once entries exist. Take one and roll back with Omarchy's own wrappers:


omarchy-snapshot create
omarchy-snapshot restore     # runs limine-snapper-restore

If snapper -c root list really does say Unknown config on Omarchy, the config was never written. Re-run Omarchy's setup rather than hand-rolling one, so you get its retention settings:


sudo bash -euo pipefail /usr/share/omarchy/install/config/snapper.sh

**Everywhere else, the path depends on the filesystem:**


findmnt -no FSTYPE /
cat /proc/cmdline | tr ' ' '\n' | grep -E 'rootflags|subvol'
bootctl status 2>/dev/null | head -5

*btrfs root plus GRUB, not Omarchy.* Snapshots in the GRUB menu:


sudo pacman -S --needed snapper snap-pac grub-btrfs inotify-tools
sudo snapper -c root create-config /
sudo systemctl enable --now grub-btrfsd.service
sudo grub-mkconfig -o /boot/grub/grub.cfg
sudo snapper -c root list

Snapper's snapshots are read-only, and many services need a writable /var, so booting one straight up often fails. Boot them through an overlay instead:


# add grub-btrfs-overlayfs to the END of HOOKS in /etc/mkinitcpio.conf
sudo mkinitcpio -P

Two traps there. grub-btrfs-overlayfs is a runtime hook with no systemd unit, so it does nothing in a systemd-based initramfs, and Arch's stock /etc/mkinitcpio.conf now ships systemd in HOOKS. Use the busybox hooks (base udev autodetect microcode modconf kms keyboard keymap consolefont block filesystems fsck) or the overlay silently has no effect. And sudo mkinitcpio -P is the plain-Arch rebuild only: on Omarchy 4 /etc/mkinitcpio.d/ is empty and mkinitcpio -P exits with No presets found in /etc/mkinitcpio.d, writing no boot image. The Omarchy rebuild is sudo limine-mkinitcpio followed by sudo limine-update.

*btrfs root plus Limine, built by hand on plain Arch.* This is what Omarchy already has, so do this only on a system you assembled yourself:


yay -S limine-snapper-sync
sudo pacman -S --needed snapper snap-pac

Then add limine-mkinitcpio-hook's overlay hook after filesystems in HOOKS: btrfs-overlayfs with the busybox hooks, or sd-btrfs-overlayfs with the systemd hooks, because btrfs-overlayfs is incompatible with a systemd initramfs.

*Non-btrfs root (ext4, xfs).* Snapshots are not possible. Use rsync-mode Timeshift, which works on any filesystem. The timeshift package hard-depends on cronie, so enable it:


sudo pacman -S --needed timeshift cronie
sudo systemctl enable --now cronie.service
sudo timeshift-gtk        # choose RSYNC mode, pick a target device
sudo timeshift --create --comments "baseline"
sudo timeshift --list

Restore later with:


sudo timeshift --restore --snapshot "<snapshot>"

Either way, snapshot *before* risky changes, not after:


omarchy-snapshot create                                   # Omarchy 4
sudo snapper -c root create --description "before upgrade" # plain Arch
sudo timeshift --create --comments "before upgrade"        # non-btrfs

On plain Arch, installing snap-pac makes pacman take pre/post snapshots around every transaction automatically. Omarchy does not ship or use snap-pac. /usr/bin/omarchy-update calls omarchy-snapshot create itself, which runs snapper create -c number followed by snapper cleanup number for every configured snapper config.

Note that neither approach protects /home unless you configure it separately. A system rollback leaves your data as it is, which is usually what you want but is not a backup. Pair it with restic or borg for actual data backup.

Verify

On Omarchy 4: pacman -Q snapper limine-snapper-sync returns both, systemctl is-enabled limine-snapper-sync.service snapper-cleanup.timer reports enabled for both, sudo snapper -c root list lists snapshots, and limine-list prints a Snapshots submenu under the Omarchy entry. Elsewhere: sudo snapper -c root list (or sudo timeshift --list) shows snapshots, and for the btrfs paths a reboot presents a snapshot submenu in the bootloader that actually boots.

Sources

no-snapshot-rollback-without-limine-btrfs