-
Notifications
You must be signed in to change notification settings - Fork 131
Description
I recently switched from Mint 22.2 to LMDE 7. I knew that a best practice for Timeshift would be to use a new backup drive, but the type of trouble I had might be worth a warning in the documentation or the code itself.
First off, I knew this was a different distro and package base, so I was not surprised that Timeshift made an entirely new copy of everything. The Timeshift progress bar indicated this went as expected. The problems happened after the backup appeared to be finished:
- The backup hard drive would not unmount.
- Any file operation on the backup hard drive took an extremely long time.
- Application Menu button for shutdown would only log off.
- Login screen buttons for shutdown/restart were non-existent.
- Attempting
sudo shutdownresulted in an error message. - Invoking
systemctlwas the only way to shutdown or restart the computer. - Reformatting the backup hard drive on the same device did not resolve any of these issues. However, reformatting it on a different device did.
My own problem appears resolved; I have not had further trouble with Timeshift on LMDE. I did not lose any current user data, however, I lost all previous backups.
I realize I could have avoided this with wiser decisions. However, if someone without troubleshooting skills or a second machine attempts this, they might conclude Timeshift damaged their backup drive. Possibly worth adding a warning either in the documentation or the code.
I hope this is helpful. Thanks!