Using Timeshift on Linux Mint to Snapshot Your System Before Risky Upgrades

Kernel and driver upgrades are the changes most likely to leave a Linux Mint machine unbootable or with broken graphics. Timeshift, which Mint preinstalls and integrates into Update Manager, lets you capture the state of your system files before you apply those changes and roll back in minutes if something goes wrong. This guide covers choosing the right mode, creating a snapshot, verifying it actually works, and restoring from a live USB when the desktop won't start.

What Timeshift does and does not protect

Timeshift snapshots cover the operating system: system files, installed packages, and configuration under /etc. By default it excludes user home directories, so your documents, photos, and downloads are not part of the snapshot. That is intentional — it keeps snapshots small and avoids rolling back your personal files — but it means Timeshift is not a backup tool. Keep a separate backup of /home with a tool like the Mint Backup Tool or rsync.

Timeshift also protects against bad software changes, not hardware failure. If your snapshots live only on the same disk that dies, they die with it. For disaster recovery, point RSYNC snapshots at a second internal drive or an external disk.

Prerequisites

• Linux Mint with Timeshift installed (it ships by default; check the menu under Administration).
• Root access — Timeshift requires administrative privileges.
• For RSYNC mode: a target partition with a Linux filesystem (ext4, etc.) and enough free space. The first snapshot copies the full system tree, so plan for tens of gigabytes depending on how much you have installed.
• For BTRFS mode: the system must have been installed on a BTRFS partition with the expected @ and @home subvolume layout. If you installed Mint with the default ext4 layout, BTRFS mode is not available without reinstalling.

Step 1: Choose a mode in the setup wizard

Open Timeshift from the Mint menu and the setup wizard runs on first launch. You will pick between two modes:

For most Mint installs (default ext4), RSYNC is the correct choice. Select the snapshot location — ideally a different physical disk if you have one — and confirm the default exclusion of home directories unless you have a specific reason to include them.

Step 2: Set a schedule and create the first snapshot

In the wizard's schedule step you can enable hourly, daily, weekly, monthly, or boot snapshots, each with a retention count. Retention counts matter: they cap how many snapshots are kept, so disk usage stays bounded automatically. A reasonable starting point for a desktop is daily snapshots kept for five days plus one weekly. Boot snapshots add a safety net on every startup but add a small delay.

Finish the wizard, then click Create to take the first snapshot manually. Watch it complete — for RSYNC this first run is the long one.

Step 3: Verify the snapshot before you trust it

Do not wait for a broken kernel to find out your snapshots are unusable. Verify with a harmless change:

1. Confirm the snapshot appears in Timeshift's list with a correct timestamp.
2. Install a small, easily removed package, for example run sudo apt install sl in a terminal.
3. Open Timeshift, select the snapshot, click Restore, and accept the default target partitions. Timeshift will restore and typically prompt to reboot.
4. After reboot, run which sl — it should return nothing, confirming the package is gone and the restore worked.

Also open the Settings tab and confirm the schedule and retention counts match what you configured, and check that the snapshot location still has comfortable free space.

Restoring when the system won't boot

If an upgrade leaves you at a black screen or a boot loop:

1. Boot a Linux Mint live USB (the same installer media works).
2. Open Timeshift inside the live session — it is included on the live image.
3. Timeshift should detect snapshots on the target disk. Select the snapshot taken before the upgrade.
4. Set the restore target to your installed system's root partition (double-check the device name, e.g. /dev/sda2 versus the live USB's own device — restoring to the wrong target is the main risk here).
5. Run the restore, shut down, remove the USB, and boot normally.

It is worth doing a dry run of just the detection step — boot the live USB once and confirm Timeshift lists your snapshots — so you know the offline path works before you need it.

Limitations to keep in mind

Restoring rolls back system files but not your excluded home data. If an application was downgraded by the restore but its config files in your home directory were written by the newer version, you can hit minor version-mismatch quirks; these are usually cosmetic but worth knowing about. And because RSYNC snapshots grow with every system change, check the target partition's free space occasionally — a full snapshot target silently stops protecting you.