Synex 13-u12: Snapshots Meet ZFS and GRUB Recovery
Synex 13-u12: Snapshots Meet ZFS and GRUB Recovery
Table of contents
Synex, the Argentine Debian-based desktop distribution, has released version 13-u12, and this is one of those updates that quietly reshapes how the whole system behaves rather than simply refreshing a version number. The headline act is Synex Snapshots reaching its 0.5.0 milestone, bringing native ZFS support alongside the existing Btrfs backend, plus proper recovery hooks straight from the GRUB boot menu. The installer has also been retooled to match. Let's walk through what's actually changed.
Synex Snapshots 0.5.0 — recovery built in, for Btrfs and ZFS alike
Synex Snapshots started life a few months back as a fairly modest tool for creating and restoring Btrfs snapshots on the project's semi-rolling branch. The idea behind that branch has always been the same: new tools get tested there first, and once they've proven themselves in real-world use, they graduate to the stable line. With 13-u12, Snapshots has made that jump, and it's arrived looking rather different from where it started. What began as a snapshot utility has grown into something closer to a full recovery layer woven into the operating system itself.
The application now works out which filesystem your root partition is running on and quietly routes itself to the matching backend. Btrfs and ZFS users see the same interface, but underneath, each filesystem is handled on its own terms rather than being forced into a shared mould. That's a sensible design call, because the two filesystems really don't work alike, and pretending otherwise tends to cause headaches down the line.
On the Btrfs side, the fundamentals were already there: Single snapshots of one subvolume, Full snapshots covering everything managed, and a restore process with proper safety nets — a preflight check, an automatic pre-restore snapshot in case things go sideways, and a transactional swap of subvolumes that always ends with a mandatory reboot. What's new in 0.5.0 is automation, with configurable frequency and retention, and — this is the genuinely exciting bit — integration with grub-btrfs. Snapshots containing your root filesystem now show up directly in GRUB, meaning you can boot into an earlier state even if your current installation has stopped working entirely. During testing, the developers went as far as deleting core system files, including the entire /etc directory, just to confirm recovery still holds up under genuinely nasty conditions. A Single snapshot restores using your current /home and logs, while a Full snapshot can boot its bundled subvolumes through OverlayFS, giving you a temporary writable layer without touching the original read-only snapshot underneath. If /boot lives on its own ext4 partition, that gets safely archived and restored too, so you're not left repairing a boot partition by hand from a live session.
ZFS gets the equivalent treatment, built from the ground up rather than bolted onto the Btrfs logic. Synex Snapshots detects your running ZFS root dataset and maps out the managed dataset tree from there, so it adapts to whatever layout your system actually has rather than assuming a fixed structure. Snapshots are genuine native ZFS snapshots, tagged with their own metadata through ZFS properties, and the interface neatly separates what Synex created from what you or another tool made manually. Restoring uses zfs rollback, and if rolling back to an older snapshot would destroy newer history, the tool warns you plainly before doing anything destructive. Root dataset restores force a reboot before you can restore again; child datasets don't need that. There's also careful handling of snapshot clones — ZFS lets a snapshot spawn dependent datasets, and deleting the wrong thing can cascade further than you'd expect, so Synex checks those dependencies twice, once when you confirm and again right before it acts, and refuses to proceed if anything's changed in between. Automation on ZFS runs entirely independently of the Btrfs side, with hourly, daily, weekly, monthly and custom-interval policies available per dataset, systemd-driven execution, and a dry-run mode for previewing what would happen without touching anything.
Then there's grub-zfs, a brand-new tool built specifically for this release. ZFS already creates a writable clone automatically when you boot a snapshot, and rather than fighting that native behaviour, grub-zfs works with it. It organises GRUB entries into three groups: snapshots Synex manages, external snapshots created outside the tool, and the writable clones that spring up once you've booted one. That last category is a nice touch — boot a snapshot, tinker with it, and you can keep returning to that same writable state for as long as the clone exists, effectively giving you a disposable test environment on demand.
For anyone wanting more advanced control over ZFS boot environments, Synex has also packaged synex-zfsbootmenu, an integration wrapper around the well-regarded ZFSBootMenu project. It's a deliberately cautious implementation: it only works on UEFI systems running ZFS, fetches the pinned official ZFSBootMenu 3.1.0 image directly from upstream, verifies its checksum before use, and installs it alongside GRUB rather than replacing it — so your existing boot entry survives as a fallback regardless. Uninstalling it simply removes its NVRAM entry and restores GRUB as the default. Notably, it doesn't rewrite any of your existing ZFS dataset properties to make itself work, which speaks to a fairly conservative, non-invasive approach to what is otherwise quite a powerful tool.
Taken together, the project describes this as three distinct layers doing three distinct jobs: Synex Snapshots for day-to-day snapshot management and restoration, grub-btrfs and grub-zfs for quick recovery straight from the boot menu, and ZFSBootMenu sitting alongside for anyone who wants deeper boot-environment control. It's worth being clear-eyed about what this isn't, too — snapshots aren't a replacement for proper backups, since they still live on the same storage as everything else. What they do offer is a genuinely accessible way to roll back a bad update or a fat-fingered configuration change without needing to already be fluent in Btrfs, ZFS, initramfs or GRUB internals.
A leaner installer and a refreshed package base
The installer, calamares-settings-synex, moves to version 1.0.30, and the changes here follow directly from the snapshot work above. The most consequential change is that the separate /boot partition has been dropped from automatic partitioning. That partition previously existed purely to accommodate LUKS2 encryption, since GRUB can't read a LUKS2 volume directly — but it meant every installation carried an extra partition just to cover a minority use case. With /boot folded into the root filesystem, root snapshots on both Btrfs and ZFS now cover it automatically, without any special handling required.
The trade-off is that LUKS2 encryption is now only available through manual partitioning, where you can set up your own ext4 /boot partition as that scheme requires anyway. If you do end up with a separate /boot partition through manual partitioning, Synex Snapshots still looks after it, archiving its contents safely as part of any recovery. The installer also does some tidying up behind the scenes: install without ZFS and the ZFS packages and their orphaned dependencies get removed; skip Btrfs and grub-btrfs goes with it; choose neither and Synex Snapshots itself isn't installed at all. So an EXT4 or XFS installation doesn't end up carrying tools it has no use for. ZFS pools created by the installer also get autotrim switched on by default.
Under the hood, Synex 13-u12 rolls in the cumulative package updates available from the Debian Trixie repositories at build time. That means Linux kernel 6.12.107, systemd 257.13, OpenSSL 3.5.7, ZFS 2.3.9, btrfs-progs 6.14, Mesa 25.0.7, PipeWire 1.4.2 with WirePlumber 0.5.8, Firefox ESR 140.15.0 and Flatpak 1.16.6. Every edition also ships Synex Package Manager 1.2.3, Synex Snapshots 0.5.0, grub-btrfs 4.14+git20260805-1synex1 and grub-zfs 0.1.0 as standard. Poking around the package manager on a test installation shows these appearing exactly as described, alongside synex-zfsbootmenu, confirming the recovery toolkit is genuinely bundled rather than an optional add-on.
Eight desktop editions are available: KDE Plasma 6.3.6 with KDE Applications 25.04.3, GNOME 48.7 with GDM3 48.0 and Nautilus 48.3, XFCE 4.20, MATE with Marco 1.26.2 and Caja 1.26.4, LXDE 13.0 with PCManFM 1.4.0, IceWM 3.7.4, Openbox 3.6.1 with tint2, and COSMIC Epoch 1.3.0.
Speaking of COSMIC, the team caught and fixed a slightly awkward dependency chain during this release cycle: the wallpaper package on that edition was pulling in GNOME Shell components it didn't actually need, which has since been replaced with a leaner, unified wallpaper package. That fix also exposed the Calamares launcher relying on xhost for display access on COSMIC, which is now resolved by running Calamares as a native Wayland client on that edition instead.
Getting Synex 13-u12 onto your machine
All eight desktop editions of Synex 13-u12 are ready for download now, and installation still runs through Calamares, the same graphical installer used across many independent distributions, so the process should feel familiar if you've installed a Debian or Arch-based system before. Automatic partitioning offers a choice between Btrfs, XFS, EXT4 or ZFS as the root filesystem, with Btrfs remaining the default. Worth flagging if you're weighing up ZFS: Secure Boot needs to be switched off during installation on that filesystem, though the official documentation explains how to enrol the DKMS key afterwards if you want Secure Boot re-enabled once the system is up and running.
Having a poke around a couple of test installs in a virtual machine is a good way to get a feel for what's actually changed. Fire up Synex Snapshots on a Btrfs system and you'll see subvolumes, snapshots and automation settings laid out clearly across separate tabs, with manual snapshot creation just a click away. Do the same on a ZFS installation and the interface looks nearly identical at a glance, but the underlying language shifts to datasets rather than subvolumes, reflecting that separate backend under the surface. Reboot afterwards and the GRUB menu tells its own story too — an "Advanced options" entry reveals a Synex Snapshots submenu on Btrfs, or a Synex ZFS Snapshots one when ZFS is in play, each listing available restore points with a timestamp alongside them.
Whichever edition you fancy — and lighter options like Openbox, LXDE and IceWM are genuinely worth a look if you want something snappier on older hardware — the official installation guide walks through every step of the process, from the initial GRUB language selection through partitioning, user setup and the final reboot.
A final word
Synex 13-u12 is a release with a clear sense of purpose. Rather than chasing a long list of unrelated changes, the team has focused squarely on making recovery genuinely accessible, whether you're running Btrfs or ZFS, and backed that up with an installer that's been quietly tidied to match. It's the kind of update that matters more the day something goes wrong than the day you install it — which, honestly, is exactly when you want a distribution to have your back.
Disclaimer
Synex, its logos, and any other trade names, trademarks or registered marks mentioned in this article belong to their respective owners, including the Synex project and Linus Torvalds' Linux® trademark, and are referenced here purely for identification and informational purposes. Every effort has been made to ensure the accuracy of the information presented, drawing solely from official Synex sources at the time of writing, though software projects evolve quickly and readers are encouraged to verify details against the official channels before acting on them. As always, please use open-source software responsibly and in accordance with its respective licence terms.
References
🔄❤️🩹🔁🛡️⚙️
Comments
Post a Comment
Hello and welcome to The Distrowrite Project! We appreciate your engagement and value diverse perspectives. Our community thrives on respectful and constructive discussions. Please ensure your comments align with our guidelines: no hate speech, personal attacks, or spam. Let us foster a positive environment where everyone feels comfortable to share their thoughts and insights. Kindly direct any complaints and suggestions for any software/hardware directly, clearly and politely to the respective developer(s). Thank you for being a part of our community!