Timeshift (after a year of use) today has lost contact to backup device and snapshots

I’ve been using timeshift for over a year. Today timeshift has lost contact with external drive and timeshift backups on it. It keeps saying there is no “linux partition on drive”. Same drive in use for a year. Device is /dev/sdb6
Verified that the external drive is mounted has not lost any partitions on it or the partition table. In fact, I did a successful rsync restore using the timeshift files on the external drive to see if going to earlier system would fix timeshift. It did not.

What I have done.
1 Reinstalled timeshift from zypper multiple times
2 Compiled timeshift fresh and installed
3 Added external drive linux partition to fstab
4 Checked drive and partition table in gparted
5 Restored a file from “backintime” that is located on the same drive.

For reference, see below:

(base) tom@mydesktop: ~ $ sudo fdisk -l
Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: TOSHIBA HDWE140 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 04F040ED-92C0-4D0B-B201-2192DE39FD0C

Device          Start        End    Sectors   Size Type
/dev/sda1          34         34          1   512B unknown
/dev/sda2          35         35          1   512B unknown
/dev/sda3          36         36          1   512B unknown
/dev/sda4          37         37          1   512B unknown
/dev/sda5   946567168  948310015    1742848   851M Microsoft basic data
/dev/sda6   948310016  952530943    4220928     2G Linux swap
/dev/sda7   952530944 1259751423  307220480 146.5G Linux filesystem
/dev/sda8  1259751424 7814035455 6554284032   3.1T Linux filesystem
/dev/sda9        2048     923647     921600   450M Windows recovery environment
/dev/sda10     923648    1128447     204800   100M EFI System
/dev/sda11    1128448    1161215      32768    16M Microsoft reserved
/dev/sda12    1161216  946565864  945404649 450.8G Microsoft basic data

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
Partition table entries are not in disk order.


Disk /dev/sdb: 3.64 TiB, 4000786153472 bytes, 7814035456 sectors
Disk model: My Book 25ED    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4610E1A9-71AF-4B43-884D-9720E5D0E70F

Device          Start        End    Sectors  Size Type
/dev/sdb1          34         34          1  512B unknown
/dev/sdb2          35         35          1  512B unknown
/dev/sdb3          36         36          1  512B unknown
/dev/sdb4          37         37          1  512B unknown
/dev/sdb5        2048 1453412351 1453410304  693G Microsoft basic data
/dev/sdb6  1453412352 7814033407 6360621056    3T Linux filesystem

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.
Partition 3 does not start on physical sector boundary.
Partition 4 does not start on physical sector boundary.
(base) tom@mydesktop: ~ $ 

nano /etc/fstab

UUID=be8570c4-cde5-4c16-afb7-4c71118bbed9  /          ext4  defaults                     0  1
UUID=e748b401-3a8f-4152-a9ea-ef540efb0230  /home      ext4  data=ordered,acl,user_xattr  0  2
UUID=C93A-C87E                             /boot/efi  vfat  defaults                     0  2
UUID=732223f6-b4fa-4fa0-9d5a-78ced9984c72  swap       swap  defaults                     0  0
UUID=ED4CBA99-D0B7-4320-91DC-5ACFFC51A178 /run/media/tom/WD_book_linux ext4 defaults,nofail 0 2

(base) tom@mydesktop: ~ $ sudo blkid
/dev/sdb4: PARTLABEL="EasyRE volume attributes protection" PARTUUID="a2dd91d0-3226-47d4-8ccc-bd75c4c7fde5"
/dev/sdb2: PARTLABEL="EasyRE volume attributes protection" PARTUUID="75641740-cd71-44ec-8111-1830b030a1ea"
/dev/sdb5: LABEL="WD_book_windows" BLOCK_SIZE="512" UUID="394DB398420355FF" TYPE="ntfs" PARTLABEL="WD_book_windows" PARTUUID="061d6392-39ab-477f-88a5-c523e8821de1"
/dev/sdb3: PARTLABEL="EasyRE volume attributes protection" PARTUUID="fc498acf-eae6-4dd2-ad58-7ee6f3fe4762"
/dev/sdb1: PARTLABEL="EasyRE volume attributes protection" PARTUUID="b762325c-1adc-0068-95e2-55de7f3c19f0"
**/dev/sdb6: LABEL="WD_book_linux" UUID="3fe3c45f-e738-43a3-9642-bffa759074f4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="WD_book_linux" PARTUUID="ed4cba99-d0b7-4320-91dc-5acffc51a178"**
/dev/sda4: PARTLABEL="EasyRE volume attributes protection" PARTUUID="0749e399-d356-491f-94b5-85d02ecf8477"
/dev/sda2: PARTLABEL="EasyRE volume attributes protection" PARTUUID="c7bb88d3-9b14-46c2-a8af-da1a224480df"
/dev/sda12: LABEL="Windows 10" BLOCK_SIZE="512" UUID="6ABE22FBBE22BF85" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d32c7d2d-0674-43a5-98b9-2b4327787708"
/dev/sda9: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C9C1F589C1F3BE0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="3868f79f-be91-4232-afda-cf3036549c08"
/dev/sda10: SEC_TYPE="msdos" UUID="C93A-C87E" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="62a93150-d01f-4f32-b4fd-c24a31f3e258"
/dev/sda7: LABEL="Linux - Root" UUID="be8570c4-cde5-4c16-afb7-4c71118bbed9" BLOCK_SIZE="4096" TYPE="ext4" PTTYPE="dos" PARTLABEL="root" PARTUUID="e052dc80-65b7-11f0-a00f-80a58916e18e"
/dev/sda5: BLOCK_SIZE="512" UUID="7C80FB8780FB45E4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e052dc7e-65b7-11f0-a00f-80a58916e18e"
/dev/sda3: PARTLABEL="EasyRE volume attributes protection" PARTUUID="bf625028-7a64-4e89-992e-b7eab2990238"
/dev/sda1: PARTLABEL="EasyRE volume attributes protection" PARTUUID="0ea6d7d6-5c61-00b2-95d2-5fc4e9758443"
/dev/sda11: PARTLABEL="Microsoft reserved partition" PARTUUID="1734fefa-4e75-482b-b151-3f56d9560a27"
/dev/sda8: LABEL="Linux - Home" UUID="e748b401-3a8f-4152-a9ea-ef540efb0230" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="home" PARTUUID="e052dc81-65b7-11f0-a00f-80a58916e18e"
/dev/sda6: UUID="732223f6-b4fa-4fa0-9d5a-78ced9984c72" TYPE="swap" PARTLABEL="swap" PARTUUID="e052dc7f-65b7-11f0-a00f-80a58916e18e"
(base) tom@mydesktop: ~ $ 

Did you forget that you opened another thread 5 hours ago?

no I didn’t forget it, that thread was closed I thought when you found my uuid error and corrected me on it.

so, I thought a more specific question on timeshift needed a new thread.

I request to close or delete first thread but don’t know how to do it.

tom kosvic

I saw a thread that said timeshift gets device info from lsblk command… If lsblk output format changes timeshift can misinterpret device info. There are some changes a year or so ago where this happened. I will look at lsblk for versions and updates.

tom kkosvic

I restored an lsblk from a “backintime” a week ago when timeshift was working. No change, still says no linux partititon which is not accurate.

In fact timeshift now says that my main hardrive has no linux partition.

When starting commandline version of timeshift I get an error message. An initial search says that this message as been associated with missing partition search bug in timeshift. This sounds like a similar bug to what I have had occurred. Looks like some fedora version was the culprit. Need more searching.

(base) tom@mydesktop: ~ $ sudo timeshift --list
Device : Not Selected


** (process:675234): CRITICAL **: 21:37:05.014: gee_abstract_collection_get_size: assertion 'self != NULL' failed
No snapshots found
(base) tom@mydesktop: ~ $ 

@tckosvic did you check for selinux errors?

As far as I know I not using selinux but using apparmor. I do no configuration of either of them.

I am reporting my experience as an issue on the timeshift github to see if that raises any attention

@tckosvic what does cat /proc/cmdline show for security?

Shows apparmor.

(base) tom@mydesktop: ~ $ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-7.0.6-1-default root=UUID=be8570c4-cde5-4c16-afb7-4c71118bbed9 splash=silent resume=/dev/disk/by-uuid/732223f6-b4fa-4fa0-9d5a-78ced9984c72 quiet mitigations=auto security=apparmor rd.driver.blacklist=nouveau
(base) tom@mydesktop: ~ $

It is NOT closed. And you never said there that you now understand that your idea about UUIDs was a dead end.

I apologize for not acknowledging it.

tom kosvic

I found many threads on similar issues couple of years ago.

I ran timeshift debug. See below:

(base) tom@mydesktop: ~ $ sudo timeshift-gtk --debug
D: Main()
D: 
D: Running Timeshift-gtk v25.12.4
D: 
D: Session log file: /var/log/timeshift/2026-05-17_07-42-44_gui.log
D: Distribution: 
D: DIST_ID: 
D: Main: check_dependencies()
D: Checking btrfs-progs version and determining capabilities...
D: -- btrfs-progs version 6.19.x
D: -- btrfs subvolume recursive delete: supported
D: Main: add_default_exclude_entries()
D: Main: add_default_exclude_entries(): exit
D: update_partitions()
D: df -T -B1
D: Device: get_disk_space_using_df(): 0
D: Device: get_mounted_filesystems_using_mtab(): 0
D: Device: get_filesystems(): 37
D: partition list updated
D: detect_system_devices()
D: / is mapped to device: /dev/sda7, UUID=
D: /home is mapped to device: /dev/sda8, UUID=
D: /boot/efi is mapped to device: /dev/sda10, UUID=
D: Searching subvolume for system at path: /
D: Users: tom root
D: Encrypted home users: 
D: Encrypted home dirs:

D: Encrypted private dirs:

D: Main: load_app_config()
D: Member not found in JSON object: snapshot_size
D: Member not found in JSON object: snapshot_count
App config loaded: /etc/timeshift/timeshift.json
D: IconManager: init()
D: found images directory: /usr/share/timeshift/images
D: Main(): ok
D: Main: initialize_repo()
D: backup_uuid=3fe3c45f-e738-43a3-9642-bffa759074f4
D: backup_parent_uuid=
D: Setting snapshot device from config file
D: Main: initialize_repo(): exit
D: MainWindow: MainWindow()
D: SnapshotListBox: SnapshotListBox()
D: SnapshotListBox: SnapshotListBox(): exit
D: MainWindow: MainWindow(): exit
D: MainWindow(): init_delayed()
D: SnapshotRepo: available()
D: is_available: false
D: SnapshotRepo: available()
D: is_available: false
D: SnapshotRepo: check_status()
D: SnapshotRepo: available()
D: is_available: false
D: Snapshot device: ' UNKNOWN'
D: Snapshot location: 
D: Snapshot device not available
D: Device not found: UUID='3fe3c45f-e738-43a3-9642-bffa759074f4'
D: Status: NOT_AVAILABLE
D: 
D: SnapshotRepo: check_status(): exit
D: SnapshotRepo: has_snapshots()

** (timeshift-gtk:110834): CRITICAL **: 07:42:45.771: gee_abstract_collection_get_size: assertion 'self != NULL' failed
D: MainWindow(): init_delayed():

But blkid show differently.

(base) tom@mydesktop: ~ $ sudo blkid
/dev/sdb4: PARTLABEL="EasyRE volume attributes protection" PARTUUID="a2dd91d0-3226-47d4-8ccc-bd75c4c7fde5"
/dev/sdb2: PARTLABEL="EasyRE volume attributes protection" PARTUUID="75641740-cd71-44ec-8111-1830b030a1ea"
/dev/sdb5: LABEL="WD_book_windows" BLOCK_SIZE="512" UUID="394DB398420355FF" TYPE="ntfs" PARTLABEL="WD_book_windows" PARTUUID="061d6392-39ab-477f-88a5-c523e8821de1"
/dev/sdb3: PARTLABEL="EasyRE volume attributes protection" PARTUUID="fc498acf-eae6-4dd2-ad58-7ee6f3fe4762"
/dev/sdb1: PARTLABEL="EasyRE volume attributes protection" PARTUUID="b762325c-1adc-0068-95e2-55de7f3c19f0"
/**dev/sdb6: LABEL="WD_book_linux" UUID="3fe3c45f-e738-43a3-9642-bffa759074f4" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="WD_book_linux"** PARTUUID="ed4cba99-d0b7-4320-91dc-5acffc51a178"
/dev/sda4: PARTLABEL="EasyRE volume attributes protection" PARTUUID="0749e399-d356-491f-94b5-85d02ecf8477"
/dev/sda2: PARTLABEL="EasyRE volume attributes protection" PARTUUID="c7bb88d3-9b14-46c2-a8af-da1a224480df"
/dev/sda12: LABEL="Windows 10" BLOCK_SIZE="512" UUID="6ABE22FBBE22BF85" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d32c7d2d-0674-43a5-98b9-2b4327787708"
/dev/sda9: LABEL="Recovery" BLOCK_SIZE="512" UUID="8C9C1F589C1F3BE0" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="3868f79f-be91-4232-afda-cf3036549c08"
/dev/sda10: SEC_TYPE="msdos" UUID="C93A-C87E" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="62a93150-d01f-4f32-b4fd-c24a31f3e258"
/dev/sda7: LABEL="Linux - Root" UUID="be8570c4-cde5-4c16-afb7-4c71118bbed9" BLOCK_SIZE="4096" TYPE="ext4" PTTYPE="dos" PARTLABEL="root" PARTUUID="e052dc80-65b7-11f0-a00f-80a58916e18e"
/dev/sda5: BLOCK_SIZE="512" UUID="7C80FB8780FB45E4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="e052dc7e-65b7-11f0-a00f-80a58916e18e"
/dev/sda3: PARTLABEL="EasyRE volume attributes protection" PARTUUID="bf625028-7a64-4e89-992e-b7eab2990238"
/dev/sda1: PARTLABEL="EasyRE volume attributes protection" PARTUUID="0ea6d7d6-5c61-00b2-95d2-5fc4e9758443"
/dev/sda11: PARTLABEL="Microsoft reserved partition" PARTUUID="1734fefa-4e75-482b-b151-3f56d9560a27"
/dev/sda8: LABEL="Linux - Home" UUID="e748b401-3a8f-4152-a9ea-ef540efb0230" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="home" PARTUUID="e052dc81-65b7-11f0-a00f-80a58916e18e"
/dev/sda6: UUID="732223f6-b4fa-4fa0-9d5a-78ced9984c72" TYPE="swap" PARTLABEL="swap" PARTUUID="e052dc7f-65b7-11f0-a00f-80a58916e18e"
(base) tom@mydesktop: ~ $ 

I added that device (/dev/sdb6) to fstab using both UUID and PARTUUID and tested each but no change. I have since commented that item out of fstab.

tom kosvic

Additionally, mount shows /dev/sdb6 mounted:

(base) tom@mydesktop: ~ $ mount
/dev/sda7 on / type ext4 (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=16200356k,nr_inodes=4050089,mode=755,inode64)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64,usrquota)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=600,ptmxmode=000)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot,memory_hugetlb_accounting)
none on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
bpf on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=6553876k,nr_inodes=819200,mode=755,inode64)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=40,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=6511)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,nosuid,nodev,relatime,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
none on /run/credentials/systemd-journald.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=16384688k,nr_inodes=1048576,inode64,usrquota)
/dev/sda10 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sda8 on /home type ext4 (rw,relatime,data=ordered)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=3276936k,nr_inodes=819234,mode=700,uid=1000,gid=100,inode64)
none on /run/credentials/getty@tty1.service type tmpfs (ro,nosuid,nodev,noexec,relatime,nosymfollow,size=1024k,nr_inodes=1024,mode=700,inode64,noswap)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
portal on /run/user/1000/doc type fuse.portal (rw,nosuid,nodev,relatime,user_id=1000,group_id=100)
Joplin.AppImage on /tmp/.mount_JoplinvAB3rn type fuse.Joplin.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=100)
/dev/sdb5 on /run/media/tom/WD_book_windows type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
**/dev/sdb6 on /run/media/tom/WD_book_linux type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)**
(base) tom@mydesktop: ~ $ 

Here is an old successful timeshare log showing where the same UUID was used to successful make a snapshot.

[15:00:00] Main: check_dependencies()
[15:00:00] Checking btrfs-progs version and determining capabilities...
[15:00:00] -- btrfs-progs version 6.19.x
[15:00:00] -- btrfs subvolume recursive delete: supported
[15:00:00] Main: add_default_exclude_entries()
[15:00:00] Main: add_default_exclude_entries(): exit
[15:00:00] update_partitions()
[15:00:00] Device: get_disk_space_using_df(): 5
[15:00:00] Device: get_mounted_filesystems_using_mtab(): 5
[15:00:00] Device: get_filesystems(): 37
[15:00:00] partition list updated
[15:00:00] detect_system_devices()
[15:00:00] Searching subvolume for system at path: /
[15:00:00] Users: tom root
[15:00:00] Encrypted home users: 
[15:00:00] Encrypted home dirs:

[15:00:00] Encrypted private dirs:

[15:00:00] Main: load_app_config()
[15:00:00] IconManager: init()
[15:00:00] found images directory: /usr/share/timeshift/images
[15:00:00] Main(): ok
[15:00:00] AppConsole: parse_arguments()
[15:00:00] Main: initialize_repo()
[15:00:00] backup_uuid=3fe3c45f-e738-43a3-9642-bffa759074f4
[15:00:00] backup_parent_uuid=
[15:00:00] Setting snapshot device from config file
[15:00:00] repo: creating from uuid
[15:00:00] SnapshotRepo: from_uuid(): RSYNC
[15:00:00] uuid=3fe3c45f-e738-43a3-9642-bffa759074f4
[15:00:00] SnapshotRepo: init_from_device()
[15:00:00] 
[15:00:00] SnapshotRepo: unlock_and_mount_devices()
[15:00:00] device=/dev/sdb6
[15:00:00] SnapshotRepo: unlock_and_mount_device()
[15:00:00] device=/dev/sdb6
[15:00:00] Device: get_mounted_filesystems_using_mtab(): 5
[15:00:00] ------------------
[15:00:00] arg=3fe3c45f-e738-43a3-9642-bffa759074f4, device=/dev/sdb6
[15:00:00] /run/media/tom/WD_book_linux
[15:00:00] ------------------
[15:00:00] Device: get_mounted_filesystems_using_mtab(): 5
[15:00:00] mount command: mount "/dev/sdb6" "/run/timeshift/29473/backup"
[15:00:00] Mounted '/dev/sdb6' at '/run/timeshift/29473/backup'
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] SnapshotRepo: unlock_and_mount_device(): exit
[15:00:00] Selected snapshot device: /dev/sdb6
[15:00:00] Free space: 2.5 TB
[15:00:00] SnapshotRepo: check_status()
[15:00:00] SnapshotRepo: available()
[15:00:00] is_available: ok
[15:00:00] SnapshotRepo: has_snapshots()
[15:00:00] SnapshotRepo: has_space() - 0 required (0 B)
[15:00:00] Device: get_disk_space_using_df(): 1
[15:00:00] SnapshotRepo: check_status(): exit
[15:00:00] SnapshotRepo: init_from_device(): exit
[15:00:00] SnapshotRepo: from_uuid(): exit
[15:00:00] Main: initialize_repo(): exit
[15:00:00] AppConsole: start_application()
[15:00:00] Main: create_snapshot()
[15:00:00] SnapshotRepo: has_space() - 0 required (0 B)
[15:00:00] Device: get_disk_space_using_df(): 1
[15:00:00] Daily snapshots are enabled
[15:00:00] Last daily snapshot is 4 hours old
[15:00:00] Weekly snapshots are enabled
[15:00:00] Last weekly snapshot is 1 days old
[15:00:00] Monthly snapshot are enabled
[15:00:00] Last monthly snapshot is 17 days old
[15:00:00] ------------------------------------------------------------------------------
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] SnapshotRepo: auto_remove()
[15:00:00] Maximum backups exceeded for backup level 'daily'
[15:00:00] SnapshotRepo: remove_untagged()
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] SnapshotRepo: load_snapshots()
[15:00:00] loading snapshots from '/run/timeshift/29473/backup/timeshift/snapshots': 9 found
[15:00:00] exit_app()
[15:00:00] crontab -l
[15:00:00] crontab -l
[15:00:00] Cron task exists: /etc/cron.d/timeshift-hourly
[15:00:00] unmount_target_device()
[15:00:00] clean_logs()
[15:00:00] cleanup_unmount_devices()
[15:00:00] Device: get_disk_space_using_df(): 5
[15:00:00] Device: get_mounted_filesystems_using_mtab(): 5
[15:00:00] Device: get_filesystems(): 37
[15:00:00] 
Found stale mount for device '/dev/sdb6' at path '/run/timeshift/29473/backup'
[15:00:00] Unmounted successfully

A fix was found from post on

from: https://github.com/erykjj

I had this too on my openSUSE system after a recent system upgrade (tumbleweed snapshot/build of May 11 worked fine, more recent ones don't). The issue is that lsblk (which Timeshift uses to get your partitions, etc.) can't get complete filesystem info from udev, and this is because of some recent AppArmor profile update affecting /usr/bin/lsblk.

The fix is to create a local AppArmor profile allowing lsblk to read the root file system so that it can get to /run/udev/data/:

**sudo mkdir -p /etc/apparmor.d/local**
**echo "/ r," | sudo tee /etc/apparmor.d/local/lsblk**
**sudo apparmor_parser -r /etc/apparmor.d/lsblk**

I tried it and now login opens to timeshift snapshot directory and I see my old snapshots. I assume all is back to normal.

thanks, tom kosvic

1 Like

timeshift looks to be working. I can’t see how he figured out it was an apparmor problem. I never saw anything leading that direction.

thanks, tom kosvic

Since apparmor affected operation of lsblk that caused my loss of timeshift issue, I was thinking of changing to selinux. If I do, need I be cautious of the same problem with lsblk on selinux? Do I need to do anything special in the change to selinux? I don’t want to lose timeshift again.

If this is considered a new issue, let me know and I will post it separately.

thanks, tom kosvic

I did change to selinux using steps from:

https://en.opensuse.org/Portal:SELinux/Setup

All seemed to go well and timeshift still works and is not affected by the lsblk issues that occurred on apparmor.

tom kosvic

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.