MX 21/3 error with MX Snapshot

[rod178]

I also have had an issue with MX Snapshot over the last few days. I creates a Snapshot (MX21.3 xfce) which seems to consists of only a generic MX21.3, is no desktop, data or panel etc Only detected when I noticed that the snapshot was only about 6.3GB, instead of about the previous 54GB. Have not yet had time to investigate further.

[thebookkeeper]

54GB? Are you using Flatpak or backing up with Timeshift? I don't have either in the MX system. Remastersys wasn't designed for such large ISO files anyway. My MX snapshot files are only 5.5GB.

[Adrian]

I also have had an issue with MX Snapshot over the last few days. I creates a Snapshot (MX21.3 xfce) which seems to consists of only a generic MX21.3, is no desktop, data or panel etc Only detected when I noticed that the snapshot was only about 6.3GB, instead of about the previous 54GB. Have not yet had time to investigate further.

Please provide logs.

[rod178]

Adrian, Snapshot log attached

PS I do not use timeshift, although a limited few Flatpaks.

My usual snapshot contains about 49GB data, which I use as a live USB (tiny encrypted Sandisk 128GB on a keyring) whilst travelling, as well was being another level of data recovery else an asteroid hits the house when I'm out. Up to a few days ago all has been working (better than) fine for years.

If I discovered a more attractive version of Linux, with the exception that it did not have a tool such as MX Snapshot, it would be dismissed as I have such a reliance on the tool.

[Adrian]

I see you excluded Documents, Music, Pictures, etc. was that intended? This is all the stuff that's excluded:

2023-11-17 10:00:26.646 DBG default: du -sxc {/.bind-root/.config,/.bind-root/.fehbg,/.bind-root/lost+found,/.bind-root/tmp,/.bind-root/dev/,/.bind-root/media/,/.bind-root/mnt/,/.bind-root/sys/,/.bind-root/proc/,/.bind-root/run/,/.bind-root/etc/bcm-ckd,/.bind-root/etc/defaultdomain,/.bind-root/etc/crypttab,/.bind-root/etc/ioctl.save,/.bind-root/etc/live/protect,/.bind-root/etc/machine-id,/.bind-root/etc/mailname,/.bind-root/etc/resolv.conf,/.bind-root/home/snapshot,/.bind-root/home/*/.config/MX-Linux/xdg_check,/.bind-root/var/cache/apt/archives/*.deb,/.bind-root/var/cache/apt/archives/partial/,/.bind-root/var/cache/apt/*.bin,/.bind-root/var/cache/debconf/*-old,/.bind-root/var/cache/lightdm,/.bind-root/var/cache/samba/browse.dat,/.bind-root/var/lib/apt/lists/,/.bind-root/var/lib/apt/periodic/,/.bind-root/var/lib/dbus/machine-id,/.bind-root/var/lib/dhcp/,/.bind-root/var/lib/dpkg/*-old,/.bind-root/var/lib/NetworkManager/,/.bind-root/var/lib/sudo/,/.bind-root/var/lib/urandom/,/.bind-root/var/log/,/.bind-root/var/log/samba/,/.bind-root/var/mail/,/.bind-root/var/spool/mail/,/.bind-root/var/spool/anacron/,/.bind-root/var/tmp/,/.bind-root/home/*/.cache/mozilla/firefox/*/cache2/,/.bind-root/home/*/.cache/mozilla/firefox/*/thumbnails/,/.bind-root/home/*/.cache/thumbnails/,/.bind-root/home/*/.dbus,/.bind-root/home/*/.local/share/Trash/,/.bind-root/home/*/.bash_history,/.bind-root/home/*/.local/share/recently-used.xbel,/.bind-root/home/*/.xsession-errors,/.bind-root/home/*/Documents/,/.bind-root/home/*/Documents/.,/.bind-root/home/*/Music/,/.bind-root/home/*/Music/.,/.bind-root/home/rod//,/.bind-root/home/rod//.,/.bind-root/home/*/Downloads/,/.bind-root/home/*/Downloads/.,/.bind-root/home/*/Pictures/,/.bind-root/home/*/Pictures/.,/.bind-root/home/*/Videos/,/.bind-root/home/*/Videos/.,/.bind-root/home/rod//,/.bind-root/home/rod//.}

Please upgrade mx-snapshot since I see it's the the last one with the /home fix and make sure you don't exclude anything you might want to keep and check the log again to if it was excluded or not, if it was excluded another thing to check would /etc/mx-snapshot-exclude.list see if you don't have them excluded there. I just took a snapshot and the excluded file list looked OK on my system.

Otherwise, at a first look I don't see anything obviously wrong in the log.

[rod178]

The exclusion list is correct.
I noted that there is an new MX Update today. I will run it and let you know the result

[Adrian]

The exclusion list is correct.
I noted that there is an new MX Update today. I will run it and let you know the result

So what is actually missing?

[rod178]

Missing are
Desktop, as well as two created data directories in /Home, UserData and UserDataArchieve are on the OS SSD

Also the exclude list does not seem to have retained my old settings, although accessing remotely rather inconvenient at present.
I will test again after I return home

thanks for your attention to this matter

PS Looking back the last successful snapshot was performed 30Oct2023, all retained in depth on HDD and Flash Drives.

Is it possible to revert to an older version of Snapshot? I do an MX Update whenever available ie daily, Snapshots less so as I obviously also backup Data independently, so all is not lost if the OS SSD goes to SSD Heaven.

[Adrian]

You could use 23.10 for example:
https://github.com/MX-Linux/mx-snapshot ... _amd64.deb

I think I figured out where things are going wrong for you, I see your home is excluded (twice):

Code: Select all

/.bind-root/home/rod//,/.bind-root/home/rod//.

I wonder if there's something wrong in your XDG user settings, can you post here the content ~/.config/user-dirs.dirs ?

Not sure where that /home/rod// comes from I cannot really replicate that, I think one of your exclusion could be translated as /home/rod// instead of /home/rod/Downloads/ (let's say), but I cannot figure out which.
Also please do me a favor and check /etc/mx-snapshot-exclude.list to see if there's any such exclusion, look for one terminated with a slash, normally exclusion there should not have a slash at the end.

[Adrian]

I think I fixed it, please try this last .deb: https://github.com/MX-Linux/mx-snapshot ... _amd64.deb
If this doesn't fix it, I still need the info that I requested in the previous post.

BTW, do you guys on Bullseye get multiple root prompts when the snapshot finishes or this happens only on my testing machine?