Diagnosing Missing or Failed Timeshift Snapshots in Linux Mint

The Problem: Scheduled Snapshots Stop Appearing

You open Timeshift and the snapshot list is empty, or the most recent entry is weeks old. A restore attempt fails with a snapshot-not-found message. The useful takeaway is that most missing-snapshot issues come from three areas: the snapshot target is not mounted or writable, the Timeshift systemd timer is not running, or the target filesystem is out of space or inodes. This guide walks through checks in order, ties each fix to its finding, and explains when to escalate.

This guide assumes Linux Mint 21.x or 22.x with Timeshift installed in RSYNC or BTRFS mode. Commands require root or sudo privileges.

Cause and Diagnostic Table

Recognizable condition	Likely cause	First check
No snapshots listed; scheduled snapshot never ran	Timeshift timer or service inactive	systemctl list-timers
Snapshot target missing from Timeshift window	Target device unmounted or not writable	df -h and touch test
Snapshot starts but fails partway	No free space or no free inodes	df -h and df -i
Restore fails: snapshot not found	Snapshot catalog out of sync or files manually deleted	timeshift --list and journalctl

Check 1: Verify the Snapshot Target Is Mounted and Writable

Timeshift stores snapshots on a target device you select during setup, such as an external USB drive or a separate partition. If that device is unmounted, scheduled snapshots silently fail.

Run in a terminal:

df -h | grep timeshift

Replace timeshift with the mount point or device name shown in Timeshift settings if different. You should see a line with the target mounted and available space.

Next, test writability. Run:

touch /mnt/timeshift-backup/.write-test && rm /mnt/timeshift-backup/.write-test

Use the actual path from Timeshift settings in place of /mnt/timeshift-backup. If the command returns "Read-only file system" or "No such file or directory," the target is not ready. Remount the device or correct the mount point in Timeshift, then reopen Timeshift and confirm the target appears.

Risk: Do not create test files inside an existing snapshot folder. Use the top-level target directory only.

Check 2: Confirm the Timeshift Timer and Service Are Active

Linux Mint runs scheduled Timeshift snapshots through a systemd timer. If the timer is inactive, no new snapshots are created even when the target is healthy.

Run:

systemctl list-timers --all | grep timeshift

You should see a timer such as timeshift.timer listed with a next run time. If nothing appears, check the service:

systemctl status timeshift

Enable and start the timer if it is disabled or inactive:

sudo systemctl enable --now timeshift.timer

This command requires sudo. After enabling, wait for the next scheduled window or trigger a manual snapshot to verify the timer works.

Risk: Enabling a timer does not fix a broken target or a full disk; it only restores the schedule.

Check 3: Inspect Logs, Free Space, and Inodes

If the target is mounted and the timer is active, look for runtime errors and resource limits.

Review recent Timeshift entries in the system journal:

journalctl -u timeshift --no-pager -n 50

Look for failure messages, I/O errors, or "No space left on device." Also check filesystem space:

df -h

And inode availability:

df -i

A filesystem can report free space but zero free inodes, which prevents new files from being created. This is common on partitions with many small files.

If space or inodes are exhausted, remove old snapshots through Timeshift, not by deleting files manually, or move snapshots to a larger target.

Fixes Tied to Each Finding

• Target unmounted or read-only: Remount the device, check /etc/fstab for persistent mounts, and reselect the target in Timeshift settings if the path changed.
• Timer inactive: Run sudo systemctl enable --now timeshift.timer and confirm with systemctl list-timers.
• No free space or inodes: Delete older snapshots from within Timeshift, expand the target partition, or add a larger target device.
• Catalog out of sync: Open Timeshift and let it rescan the target. Do not restore from a snapshot unless you have verified the catalog matches the files on disk.

When to Escalate

Escalate to a system administrator or hardware replacement if:

• The target disk reports I/O errors in journalctl or dmesg.
• Filesystem corruption is detected and fsck is required on the snapshot target.
• Snapshots remain missing after verifying the mount, timer, space, and inodes.

Verification After a Fix

Do not assume the schedule is fixed. Verify with these steps:

1. Open Timeshift and create a manual snapshot.
2. Confirm the new snapshot appears in the list with today's date.
3. Run timeshift --list in a terminal to verify the CLI can read the catalog.
4. Check that the next scheduled snapshot appears after its configured interval, or trigger a test run to validate the timer.

Timeshift does not back up user home data by default. Keep a separate backup of documents and personal files.

Limitations

Restoring a snapshot replaces system files and may remove packages installed after the snapshot was taken. Never delete snapshot directories manually; use Timeshift to avoid corrupting the snapshot database. If the target drive is physically failing, no software check will reliably fix scheduled snapshots.