Hi Robert, I just did another test. I have a TW VM which is stored on a different physical drive. Running in that VM /usr/lib/snapper/systemd-helper --cleanup Also produces similar errors: Failure (error.something). number cleanup for 'root' failed. And /var/log/snapper.log in the VM also contains similar errors: 2022-12-04 20:06:27 ERR libsnapper(2289) Client.cc(dispatch):1951 - caught unknown exception 2022-12-04 20:06:27 WAR libsnapper(2437) errors.cc(convert_exception):39 - CAUGHT: dbus error exception 2022-12-04 20:06:27 WAR libsnapper(2437) errors.cc(convert_exception):52 - RETHROW: dbus error exception 2022-12-04 20:06:42 MIL libsnapper(2289) Snapper.cc(~Snapper):142 - Snapper destructor 2022-12-04 20:06:57 MIL libsnapper(2289) Snapper.cc(~Snapper):142 - Snapper destructor 2022-12-04 20:07:27 MIL libsnapper(2289) snapperd.cc(main):315 - Exiting So we have similar snapper errors from different TW installs on different physical disks. Seems pretty unlikely that all my drives are falling....