Creating snapshot failed

[abbaty48]

System details

Omarchy 3.1.3

What's wrong?

I'm unable to update Omarchy whenever I try using the refresh button at the waybar or via the Omarchy menu (Super + Alt + Space). I get this error.

Creating a snapshot failed.
Something went wrong during the update!
Please review the output above carefully, correct the error and retry the update.

Done! Press any key to close...

Any clue please

[davemaier]

I'm having the same problem on 3.1.4, could not find any helpful logs so far.

[rliessum]

"sudo swapoff -a" did the thrick for me as well.

[codebyrashel]

Well i am also having problem to update mine, but for me its a bit different, do any of you guys have any idea about this. Any leads or help would be much appreciated, Thanks in advance
<img width="606" height="337" alt="image" src="https://github.com/user-attachments/assets/a46f0d77-d791-4d08-ac6c-8b3d1faf73c3" /

[fcsonline]

Maybe mounting the swapfile in a another brtfs subsystem, we can avoid this.

[codebyrashel]

Well, I tried many ways and even looked docs, asked help and used AI but none of them worked so I just reinstalled it and now its working fine, though now I am facing another issue which is different from this issue

[saintfts]

the issue's never been fixed, still have to disable swap for omarchy-snapshot create to work

[takiido]

this helped me:

1. verify the Snapper config and subvolume exist

sudo snapper list-configs
sudo btrfs subvolume show /home

2. create .snapshots as a Btrfs subvolume

A plain directory won't work — Snapper requires a proper Btrfs subvolume.
If a plain directory was already created by mistake, remove it first.

sudo rmdir /home/.snapshots          # only if it exists as a plain dir
sudo btrfs subvolume create /home/.snapshots

3. create the snapshot

omarchy-snapshot create

[jacksenechal]

I dug into this same issue and confirmed that, as others have said, it's because btrfs refuses to take a snapshot with an active swapfile in the target volume. The solution is to move the swapfile to its own volume.

Step 1 — find your values. Run these and note the output:

findmnt -no UUID /                  # your btrfs UUID
findmnt -no SOURCE --nofsroot /     # your root device (e.g. /dev/mapper/root or /dev/sda2)

Step 2 — move the swapfile. Substitute , , and adjust the size/path if yours differ:

# Release and delete the swapfile that's pinning the root subvolume
sudo swapoff /swapfile
sudo rm /swapfile
sudo sed -i '\#^/swapfile[[:space:]]#d' /etc/fstab   # remove the now-dead fstab entry

# Create a dedicated top-level @swap subvolume
sudo mount -o subvolid=5 <DEVICE> /mnt
sudo btrfs subvolume create /mnt/@swap
sudo umount /mnt

# Mount it at /swap (no compression — swap must be uncompressed/NOCOW)
sudo mkdir -p /swap
echo 'UUID=<UUID>  /swap  btrfs  rw,noatime,subvol=/@swap  0 0' | sudo tee -a /etc/fstab
sudo systemctl daemon-reload
sudo mount /swap

# Recreate the swapfile in its new home (mkswapfile handles NOCOW + mkswap)
sudo btrfs filesystem mkswapfile --size 16g /swap/swapfile
echo '/swap/swapfile  none  swap  defaults  0 0' | sudo tee -a /etc/fstab
sudo swapon /swap/swapfile
swapon --show

Then verify root snapshots now work — the whole point of this:

sudo snapper -c root create -c number -d "verify after swapfile move"
sudo snapper -c root list | tail -5