So this isn’t technically an issue and is strictly NON-DISTRO specific but I felt it would be the most appropriate to post the topic here.
In Timeshift, whenever I want to restore a snapshot, in the restore popup, if I select the /home and /boot directories to be kept on SUSELeap (which is my root partition) instead of the option Keep on root device , TimeShift will restore the snapshot correctly but at last , it will delete all the files.
Any clues about this behaviour ? , tried this on 3 different distros and got the same behaviour. Is this some sorta bug ? Doesn’t pester me, just feels a bit weird.
Well I did so by posting an issue shortly after the post here and now I probably see timeshift as an unreliable tool so I am now migrating all my snapshots to restic, seems one of many reasons why the developers here at Garuda have chosen btrfs and snapper over it. Will probably make bash scripts for restic to automate most of the tasks.
Concept and goal of timeshift is noice, but seems that Linux Mint devs are having a hard time fixing/polishing it.
Off topic but I have also been thinking to recommend one of my newb friends to try Garuda instead of Windows ! She doesn’t currently know how to navigate Windows properly but I am damn sure Garuda or Linux as I say will have a positive impact on her experience.
Restoring /boot to the EFI partition is incorrect, and might just fail due to insufficient space. /boot contains all your kernels and initrds; depending on the total size of those, they may not fit on your 537 MB EFI partition. If it does succeed, I would expect it will overwrite your bootloader configuration.
Similarly, restoring /boot/efi to your 66 GB ext4 root partition is also incorrect (/boot/efi is the EFI partition). I would expect this to wipe the contents of the ext4 partition, then sync over the less than 1 MB of files stored on the EFI partition (which more or less aligns with the behavior you are describing).
It seems to be a case of the tool working as expected after being misconfigured, not a bug.
Well extremely sorry that I used the incorrect screenshot and will update it now ASAP.
Correct would be ,
/ on OpenSUSELeap
/boot on OpenSUSELeap
/boot/efi on SUSE_BOOT
/home on OpenSUSELeap
I will re run the restore as I have done before with this config mentioned above and update the screenshots , although the data and results will be the same.
It attempts to mount /boot and /home at the root and ends deleting everything in the pursuit to do so. It should atleast warn at the slection screen or change this behaviour to mount /boot and /home at /.
Yes but at the very first screen , first time with it , it absolutely decimated my install as I thought it to mount it at root which is technically did but didn’t.
Anyways, I believe this to be a skill issue/misunderstanding on my side along with a slightly improper software design.
Case closed.
I might fork the repository and propose a commit to the main project adding these warnings and a nice quickstart guide in timeshift , after my exams if I learn GTK.
