linuxmint / linuxmint/timeshift

`timeshift --restore` fails with vfat error, but restoring thru the GUI works fine???

Open
#534 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Vala
Stars
4.3k
Forks
155
PR merge metrics
No merged PRs in 30d

Description

System: Artix Linux

Today I updated from kernel 7.0.3-artix1-2 to 7.0.5.artix1-1 and this broke a ton of stuff.

  • The amdgpu kernel driver did not load, as the TTY stayed on a super low resolution.

  • There was no internet connection.

So I attempted to run timeshift --restore and was met with this error:

[05:25:38] Device: get_mounted_filesystems_using_mtab(): 2
[05:25:38] mount command: mount "/dev/nvme0n1p1" "/run/timeshift/1194/restore/boot/efi"
[05:25:38] E: Failed to mount device '/dev/nvme0n1p1' at mount point '/run/timeshift/1194/restore/boot/efi'
[05:25:38] E: mount: /run/timeshift/1194/restore/boot/efi: unknown filesystem type 'vfat'.
       dmesg(1) may have more information after failed mount system call.

Note I have using timeshift on this system for over 2 years and I never had this problem before.


I was able to start a graphical session all in super low res and using llvmpipe and start timeshift-gtk and in that case restore WORKED and I was able to save my system 🤯

How is that even possible???

I'm attaching both logs here, they include the attempt of restoring from the tty and the successful restore from the GUI.

2026-05-12_05-25-31_restore.log
2026-05-12_05-30-51_gui.log

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the attached restore.log and gui.log, starting with the timeshift --restore and timeshift-gtk restore paths and their mount commands. Determine why mounting /dev/nvme0n1p1 as vfat fails from the TTY path but succeeds through the GUI, then verify the behavior with both restore entry points.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.