Page 1 of 1
MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 11:27 am
by monamtb
Hi all,
I tried to make a snapshot of my 50 GB root and my complete home directory of 640 GB and it always fails.
I learned through a previous discussion that my 1TB USB ssd is not big enough for the snapshot because it seems to need about double the GB of the current data - so no wonder it failed every time.
I want to migrate my complete system from my Dell precision laptop to my new HP pavilion laptop.
For me some questions remain based on the discussion I followed:
1) If I make a redistribute snapshot, will all installed apps be used/ copied by the snapshot and will all of these apps be available to the new user account to be created after the snapshot install on the new laptop?
2) I created a backup of my /home directory with Lucky Backup. How do I restore all of the files into my home directory of the new HP laptop without running in to the scenario ( I once had) that all files were automatically assigned to a different ownership and I couldn't use any of the files restored since I couldn't work on my files based on a "missing ownership".
3) How do I use Lucky Backup to create incremental backups of the /home folder backup I created, once the files have moved to the new HP laptop?
I tried timeshift and lucky backup, but there are so many terms and options that I get lost on what to choose and how to do what I want to do because I am not familiar with the terminology.
I guess I need a "Backup for Dummies" for either of these programs - any links for maybe such an existing manual or step-by-step instruction article will be much appreciated.
4) Should the snapshots be used as a backup tool for my data and my running system as a whole since some mx experts deem it not useful as a data backup tool?
I really want to say I love this community and the help that is provided here - simply stellar.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 12:03 pm
by CharlesV
There are a number of posts in the forum that talk about backups, but basically three tools handle things differently - different needs really, and all three can help you maintain it all.
Timeshift - left to its purpose, is like a "system save and restore"... and this works for your existing system to do just that. (not data, unless you include your home, but be VERY careful there!) On a daily, weekly schedule, this can save you on a running system that just borked.
MX Snapshot - think of this as THE method to create your system 'save' on to bare metal. This can provide you with limited data save, but its really meant to set your system down onto different hardware and 'boot' a new machine into your old setup, but move you into the NEW hardware too, making some adjustments so that it can work there.
Backup Apps - BackInTime (my favorite), Lucky Backup, Deja-Dup and many more , backup data and should restore data as needed.
Once you get data over a 30gb size, then MX snapshot really doesnt provide the 'one stop' backup to handle it all. And you need at least two things to move over to a new machine or recover a machine. AND when moving over to a new machine, you have to adjust for that new machine hardware, so restoring config's can be an issue too.
Your best scenario for a new machine, ( imo ), when your keeping the same MX version, is to do the following:
1) Create an MX Snapshot of your system, keeping preserve data, but making sure your excludes are enough so that your ISO will fit on your USB drive AND boot! ( ie you may need to exclude most all of your data to do this!)
Example: I have ALL of my data on my big machine on another partition, and I only shortcut to it, so MX Snapshot can run with no excludes... but on my laptop.. I have to exclude: Downloads, Video and my Data folders in order to make a snapshot. )
Test this Snapshot to make sure you can boot and run from it.
2) Backup software: I use BackInTime, so once my new machine is all loaded from my Snapshot, I restore all of my files , to my ~/home/Backup folder. Then I adjust ALL rights here, making sure I have any adjustments or movements to data done here, and then I move all of this (except .config ) into the proper areas I want to end up with. Then, individually, I save the new and then copy the old .config's over to my new machine, making sure they dont break anything.
3) Once I have my new machine setup, then I immediately setup TimeShift and create the first save. (and set for daily in the schedule.)
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 12:04 pm
by DukeComposed
monamtb wrote: Mon Sep 02, 2024 11:27 am
2) I created a backup of my /home directory with Lucky Backup. How do I restore all of the files into my home directory of the new HP laptop
3) How do I use Lucky Backup to create incremental backups
I guess I need a "Backup for Dummies" for either of these programs - any links for maybe such an existing manual or step-by-step instruction article will be much appreciated.
Lucky Backup has
extensive documentation you can use to get started and a little birdie tells me they even have
their own support forum. Lucky Backup is, basically, a sophisticated wrapper around rsync, so it's going to approach copying data around in the same way that rsync does.
If you aren't familiar with how rsync behaves when synchronizing two file trees, Lucky Backup is probably not going to make a lot of sense to you. It might make things easier to run, but it isn't likely to make anything easier to understand. There are tutorials like
How to Use Rsync in Linux: A Step-by-Step Guide for Beginners and a handy
rsync cheatsheet that can help here.
In general, the best way to precisely clone a large system is with a tool specifically designed to perform that function. I like Clonezilla for things like this because it makes a transferable image of the entire system. It is not, in the traditional sense, a backup utility. It doesn't even necessarily know or care about files or mountpoints. It just makes copies of partitions and their contents. You may have better luck setting up the new laptop next to the old laptop and cloning from one to the other across the network with Clonezilla than trying to split this particular baby into apps-and-configs and user data.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 1:00 pm
by Kermit the Frog
monamtb wrote: Mon Sep 02, 2024 11:27 am
1) If I make a redistribute snapshot, will all installed apps be used/ copied by the snapshot and will all of these apps be available to the new user account to be created after the snapshot install on the new laptop?..
Yes.
Just the desktop, wallpaper, panel, window manager settings and such customizations will turn to defaults for the new user(s).
The installed and removed programs will stay as they are, just the preferences about them will normally turn back to defaults, too.
Also the drivers will be picked automatically according to those machines (hardware).
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 2:55 pm
by atomick
Yes Snapshot will do what you want to Image and then deploy onto your new Laptop; Prime cmos/bios make sure secure boot is turned off or set to a "Standard" boot and not a custom option (asus strix moboz confuse this optn).
Snapshot is unique to MX and to me is one Superb feature. Recent updated all hardwarez to top AMD 78/7950/7954 3 items and play lots with MX snapshot. My day driver is AMD7800x3D 32g ddr and various drive configs. nvme0 = 1T all out w/swap.
I just since kernel 6.10.6-2 created new snapshot of this 7800 and deployed onto MX23.2 system that update seemed not to touch being my 7950x3D 64g ddr. So I Over-wrote installed MX23.3 kernel 6.10.6-2 onto this system perfectly and was installed to 1st boot in about 3min. :: Snapshot without going into chapters of finger dance will back up your MX-Linux OS File system as is the OS part. Thinking it will take everything in /home/yourAcct/*.* yes and no, so this is where you must limit exclude what is not necessary. Like everything exclude all the sub folders and "Edit" via its own edit and look closely thru top-bottom the structure of how it "Excludes" all the series of FS parts. and in Home. I snapshot then usually install the ISO image into VBox Guest, to which ~/home/MYact/VboxVMs home directory and subdir: nothing gets copied into the snapshot. (only OS-fs files)
or all my guest image loads. For VirtualBox.ova bkups are on 2nd disc. here is ex: where by home is set to exclude: some entry examples to exclude outside the common listing to exclude.
example:
home/*/VBoxVMs/*
home/*/Virtual Box VMs/*
home/*/.cache/*
home/*/bin/*
home/*/myBig/* as examples, and everything else Downloads/Documents/Picz etc. nothing subfolders all checked.
if you have a large dir to another large dir with big files follow the manual entry to the Edit Exclusions - and add it to this list -- button left middle of opening the 2nd page of options for where snapshot is going to go when copy built. (I do this onto a 2nd Drive nvme1 dir result.) [ not into my ~/home folder/snapshot ] wish not to creating a bkup loop scenario.
Snapshot copies all from BM (bare-metal) install thru to what all my additional apps you add in to now. All additional accts etc. I have few other test accts Make sure all sub folders in Your Acct shown in pg 2 of snapshot are all checked and any you added to the exclusions list pg 2, all additional space size critical entry.
try 1 with preserve accnts for bkup and one for resetting accounts for sharing (hint meaning copy of ) this is more slim by result not by much though. of my 1st install at BM I clean tweak add fair number apps clean /var/log cache dirs then Snapshot. Once completed takes like 1.33 sec to image I load to install to a VBox guest and test.
All my apps /usr/share/bg's are all incl'd in snapshot. not any Archive or additional space consuming files. myBig I would scp over to the 2nd machine Laptop etc. and sync there, One chap incld'd some rsync link info 'thx' or use other means to copy archive.n.large file content to laptop. usb-sata adaptor maybe as option.
That sums it up play practice be blessed. MX snapshot is true mind blow. (saves ghost like backups or anything clonezilla else mentioned. alone MX-snapshot should be gold ribbon award) for sysAdmins. anyone with patience to learn this coolie.
okay so some stats. my end result snapshot are about 3.67g total for kernel 6.10.6-2 and 3.95g for most recent 6.10.7-1 w/o accounts ( I also USB-create a copy to a 64g flash stick - I install from) above mention!.
snapshot has undergone good corrections since MX23.3 was out instl to vbox I'd setup 32 gig disc space at 1st it reqd 58-60g spc that is corrected now as just mention.
I script hack in vbox and also my guest backups also go same backup dir with bkup/snapshot as sub folder where snapshots go both contained onto a 2nd nvme or ssd or spinners i wish off the main m2 nvme0 drive.
easy to recreate account names or change up stuff by Snapshot. It really is a marvel tool. OH Important note: Snapshot if you do 'No Account' resetting allow to share?. this does not set, but blanks out sudo account entry allowance in /etc/group
so once you install to new hardware chg root passwd : sudo passwd root : and issue usermod -aG sudo NewAcctName eg: as root or sudo usermod -aG sudo JohnSmith grep John /etc/group to verify it is set, sudo cat /etc/shadow to actually test it is set. Add to /etc/sudoers and set a file 010_newUser-passwd in to /etc/sudoers.d and visudo this is a nano like editor with cautions. (might be adv to many reader). OSI req is not necessary.
I set zstd best compromise 3rd compress option. (snapshots take about 1-2 less minutes to complete) install to VBox about 4 mins give or take. Wicked cool trik - create a zip of scripts or small stuff you may use for start setting up your new load, copy this file into /var/cache eg: myTolz.zip chmod it 600 and do this before starting a snapshot. This will be copied into the snapshot result so when you deploy to new hardware you have your tool.zip right there without any other need. How cool is that. !
the Exclusion file itself is held in /etc/mx-snapshot-exclude.list is the actual file. be careful with this less edit expert use only in snapshot tool itself. also creates a ts file /etc/snapshot_created which is when you executed the snapshot to commit time.
(maybe a new entry to the MX-UsersGuide might command a future like entry). hope this helps all reader. Simply know to learn and learn to know.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 3:18 pm
by fehlix
monamtb wrote: Mon Sep 02, 2024 11:27 am
I tried to make a snapshot of my 50 GB root and my complete home directory of 640 GB and it always fails.
I learned through a previous discussion that my 1TB USB ssd is not big enough for the snapshot because it seems to need about double the GB of the current data - so no wonder it failed every time.
Seems, you got lot's of advices so far.
What I would suggest, try exclude during snapshot creation as much "data" directories as you can.
( There is a exclude button. You will get the syntax when viewing the exclude.list)
And save/store/backup those data outside from the snapshot generated iso.
Do a personal snapshot, so all other data and setting related would be available,
on the snapshot and later also on the install system (created from the snapshot.)
Note the max size of snapshot is about 400 GiB, b/c the used tool xorriso
to generate the iso has set a fixed max size limit of the iso of: 400GiB -200KiB)
But in your case it would fit b/c the big linuxfs squashfs would be highly compressed
if using zstd or xz compression.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 3:25 pm
by jj 5117
If this is your list of needs:
a. Installing the same OS with all of the same applications.
b. Transfer GUI interface settings.
c. Transfer Application settings.
d. Transfer all User files.
e. Worry about a sane backup plan later, now that toes are wet.
Then:
Using MX Snapshot and MX Live USB worked GREAT for me with a pretty large system.
I had Snapshot build its image, with ALL files, onto a hard drive. Then Live USB for a bootable portable from that.
It was great. The hard drive took a little time... But it was OK. It was the slickest OS transfer I ever did.
I don't know why larger system copies with MX Snapshot wouldn't work for some people, except for drive space.
Edit: Aaaand, Felix answered that.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 02, 2024 3:34 pm
by jj 5117
OR, you could use MX's Snapshot and LiveUSB to install Root, and then do a copy/paste of your Home directory without needing to learn any backup programs.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Thu Sep 05, 2024 12:08 pm
by monamtb
Hi all,
Thanks to everybody for the advice given and the suggestions made.
I did a personal snapshot with only my desktop and download folder data included because I wanted my home folder to be present.
I had the snapshot saved on an external USB SSD. The final iso of the USB ssd I copied back to my home folder and saved it there. I then connected another USB ssd disc und used USB maker to install the iso on it to make it bootable. I then booted the new laptop with it and installed the system.
The peculiar thing though is - on my old laptop the /root partition had 60 GB.
Now it wanted a minimum of 260 GB on the new laptop to install and wouldn't go below that.
Both systems have a 1TB ssd.
Did something go wrong there or does that make sense to you??
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Thu Sep 05, 2024 12:39 pm
by Kermit the Frog
monamtb wrote: Thu Sep 05, 2024 12:08 pm... did a personal snapshot with only my desktop and download folder data included because I wanted my home folder to be present...
With a personal snapshot your desktop (panel, customizations etc.) will already be present. You could exclude all, later manually copy them.
Also if there's still any problem: Right after the installation (when it gets stuck) you can post /var/log/minstall.log
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Thu Sep 05, 2024 4:55 pm
by fehlix
monamtb wrote: Thu Sep 05, 2024 12:08 pm
The peculiar thing though is - on my old laptop the /root partition had 60 GB.
Now it wanted a minimum of 260 GB on the new laptop to install and wouldn't go below that.
Both systems have a 1TB ssd.
Did something go wrong there or does that make sense to you??
When running the installer from the booted LiveUSB made with the
personal snapshot-iso, you can set within the installer the size of root as you like.
That's just the same procedure as installing from the released ISO
or the official monthly snapshot ISO.
The difference with a personal snapshot you would not
being asked to create a user during install as
it would take the existing user from the snapshot.
At least that's the way the installer is currently setup.
Whether a 260 GB "/"-root partition makes sense or not, that's another matter,
as it really depends what else you want to put onto the "/"-root partition.
E:g you could assign within the installer a separate /home partition,
instead of having /home in the "/"-root partition, so in case
the big-data lives on the /home partition you have those on
a separate partition.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 07, 2024 3:17 am
by monamtb
Hello Fehlix,
When running the installer from the booted LiveUSB made with the
personal snapshot-iso, you can set within the installer the size of root as you like.
That is what I was referring to when I said I can't get the /root size lower that the 260GB because the installer slider wouldn't allow me and blocked me at 260GB.
I had a 60GB /root and a 930 GB home in the old laptop.
That is why I don't understand what is going on.
I thought the personal iso will copy the /root and /home as it was on the old laptop.
Or did I miss to modify any parameters while building the snapshot,???
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 07, 2024 7:38 am
by DukeComposed
monamtb wrote: Sat Sep 07, 2024 3:17 am
I had a 60GB /root and a 930 GB home in the old laptop.
That is why I don't understand what is going on.
I thought the personal iso will copy the /root and /home as it was on the old laptop.
You're mistaking a snapshot of files in a file system for a block level backup of one or more partitions. MX Snapshot wouldn't be very useful if it only made a duplicate of the machine on which is was run. It would never be able to install onto a larger hard disk. When you make a snapshot with MX Snapshot you're creating a customized copy of the file system as it existed on the machine where you ran MX Snapshot. And Linux, in general, really doesn't care about how your machine is partitioned as long as the important files are accessible when it needs them. So MX Snapshot doesn't bother remembering partition sizes.
If you want to duplicate the exact partition sizes onto a second disk without using a cloning utility designed to handle exactly that kind of thing, you can either do it by hand like how you set up the first machine or use a partitioning utility that can export and import configuration data. I believe sgdisk is good at this.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 07, 2024 7:45 am
by fehlix
monamtb wrote: Sat Sep 07, 2024 3:17 am
Hello Fehlix,
When running the installer from the booted LiveUSB made with the
personal snapshot-iso, you can set within the installer the size of root as you like.
That is what I was referring to when I said I can't get the /root size lower that the 260GB because the installer slider wouldn't allow me and blocked me at 260GB.
I had a 60GB /root and a 930 GB home in the old laptop.
That is why I don't understand what is going on.
I thought the personal iso will copy the /root and /home as it was on the old laptop.
Or did I miss to modify any parameters while building the snapshot,???
Maybe, but we need some more data to understand what's going on.
Perhaps show the size usage with the generated snapshot iso.
e.g. this way:
Open terminal as normal user, within the same directory the snapshot.iso is located:
Now let's "mount" the iso this way:
replace "snapshot.iso" with the iso-name used for your snapshot.iso.
The command will "open" the iso and mount the content at
two newly created directories under
/mnt/iso/iso1
and
/mnt/iso/sq1
We are only interested into the content of linuxfs mounted at /mnt/iso/sq1
Now we get the size used with:
Code: Select all
sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
which looks in may personal snapshot example like this:
Code: Select all
sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
236M /mnt/iso/sq1/./boot
24M /mnt/iso/sq1/./etc
327M /mnt/iso/sq1/./home
609M /mnt/iso/sq1/./opt
450K /mnt/iso/sq1/./root
7.0G /mnt/iso/sq1/./usr
703M /mnt/iso/sq1/./var
8.9G /mnt/iso/sq1/.
with last line as the total size used of the linux file system
at top/root dir "/" here mounted at /mnt/iso/sq1/.
Perhaps post the commands used and the output.
To unmount the iso and clear the mount points run:
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 09, 2024 2:07 am
by monamtb
Hello Fehlix,
What I get when I follow your steps is this:
Code: Select all
monamtb@mxlinuxmona:~/Templates
$ sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
433M /mnt/iso/sq1/./boot
24M /mnt/iso/sq1/./etc
195G /mnt/iso/sq1/./home
1.6G /mnt/iso/sq1/./opt
68M /mnt/iso/sq1/./root
9.2G /mnt/iso/sq1/./usr
411M /mnt/iso/sq1/./var
207G /mnt/iso/sq1/.
Am I correct that it seems that the snapshot iso put the /root and the /home directory in the new root directory???
If so, how can I avoid that when making a snapshot or when installing the personal iso???
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 09, 2024 5:07 am
by DukeComposed
monamtb wrote: Mon Sep 09, 2024 2:07 am
Code: Select all
195G /mnt/iso/sq1/./home
207G /mnt/iso/sq1/.
Am I correct that it seems that the snapshot iso put the /root and the /home directory in the new root directory???
If so, how can I avoid that when making a snapshot or when installing the personal iso???
I think you're not taking into consideration that directories are hierarchical: if you have a tree of files, say a, b, and b/c/d, then c will contain d, and its size will reflect that. b will contain c and d, and its size will reflect that. and / will contain everything and its size will reflect that. /mnt/iso/home has size x, so /mnt/iso will have size greater than x. The files all exist under one mount point.
File trees are not disk partitions, don't confuse the two. You don't make partition decisions with MX Snapshot. That's a choice you make at installation time.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 09, 2024 6:11 am
by davidy
You're going to have separate the majority of whatever you can off that disc in order to get the snapshot down to a working size or be forced to reinstall clean. Don't you have a secondary drive so that your "OS", the main bootable disc, isn't carrying the entire workload? An external USB-c nvme drive transfers between 150-450 MB/s and is a great choice for quickly moving stuff around. Also with such a large setup you should think about using partition schemes. It would be much more manageable and then you could use something like clonezilla to backup each partition separately. No matter what you need to get the actual bootable OS disc down to as small a size as you can period. Makes backups much quicker and if the drive fails completely you only lose the OS and not everything as seems to be in your case.
I'm pretty sure clonezilla will not clone a vm but it will clone your entire drive.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 09, 2024 6:45 am
by DukeComposed
davidy wrote: Mon Sep 09, 2024 6:11 am
I'm pretty sure clonezilla will not clone a vm but it will clone your entire drive.
Cloning a VM is probably best done through the specific virtualization platform on which it exists, and most if not all VM platforms support that functionality in one way or another. All clonezilla really does is make images from a system. If you can boot the clonezilla ISO on that VM, clonezilla can make an image of it, or apply an existing image to it, regardless of what that VM already contains.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Sep 09, 2024 11:19 am
by fehlix
monamtb wrote: Mon Sep 09, 2024 2:07 am
Hello Fehlix,
What I get when I follow your steps is this:
Code: Select all
monamtb@mxlinuxmona:~/Templates
$ sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
433M /mnt/iso/sq1/./boot
24M /mnt/iso/sq1/./etc
195G /mnt/iso/sq1/./home
1.6G /mnt/iso/sq1/./opt
68M /mnt/iso/sq1/./root
9.2G /mnt/iso/sq1/./usr
411M /mnt/iso/sq1/./var
207G /mnt/iso/sq1/.
Am I correct that it seems that the snapshot iso put the /root and the /home directory in the new root directory???
If so, how can I avoid that when making a snapshot or when installing the personal iso???
Looks all good. Except of course I would personally not create a 200++ GB iso snapshot,
but rather exclude all data directory and backup data differently.
To "/root": Seems to me you got bit confused . The linux filesystem hierarchy has a top-directory "/",
underneath of the top-directory other sub-directories exist, where either files/directories exist within those sub-directories,
or some of those sub-directories are just empty directories, where other partition-filesystems get mounted on.
E.g if home lives on another partition, the "/home" directory is an empty mountpoint-directory,
where the filesystem of the home-partition get mounted on during boot-up.
The filesystem hierarchy is sometimes also represented as a tree (but upside-down)
The top-directory of the filesystem is sometimes called root-directory of the filesystem tree.
Now, within the top "/"-directory you have one special "/root" directory, which is just
the home directory of the system-user "root", this "/root" directory has nothing todo,
when we talk about "/"-top directory. Sometimes the top-directory is also referred to as "/"-root directory,
where "root" is now referring to the "root" of the tree, not to the home directory of the system user "root".
uff...
Now back to the issue, perhaps try again to install and move the "slider" to assign space for "/"-top and "/home".
If that does not work. Do post the log file of the installer to be found within the QSI-tool (also as /var/log/minstall.log)
It may well be you encountered a "bug", or something else.
Normally I do always prepare partitions manually, either before running the installer,
e.g. using Gparted or from within the installer itself.
Good luck.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Sep 17, 2024 10:54 am
by monamtb
Hello Fehlix,
I manually partitioned the new laptop ssd with 78 GB / - and 920 GB /home.
I created a new snapshot with all /home files excluded
Upon install the installer now wants 390 GB for /root - and again won't install my /root directory into the / partition I want to use with the 78 GB / partition - even more than last time: with some /home data included it was 226 GB.
QSI gives me that output:
Code: Select all
[CODE]2024-09-16 23:38:38.355 DBG default: Installer version: 24.05.01mx23
2024-09-16 23:38:38.394 DBG default: << void MInstall::startup() >>
2024-09-16 23:38:38.394 DBG default: Detect EFI: 64
2024-09-16 23:38:38.395 DBG default: Exec #1: uname -m
2024-09-16 23:38:38.403 DBG default: Exit #1: 0
2024-09-16 23:38:38.403 DBG default: Detect arch: "x86_64"
2024-09-16 23:38:38.403 DBG default: Live boot: BOOT_IMAGE=/antiX/vmlinuz quiet splash lang=en_IE kbd=us tz=Europe/Berlin
2024-09-16 23:38:38.409 DBG default: Check MD5: /live/boot-dev/antiX/initrd.gz
2024-09-16 23:38:38.445 DBG default: Check MD5: /live/boot-dev/antiX/vmlinuz
2024-09-16 23:38:38.471 DBG default: Check MD5: /live/boot-dev/antiX/linuxfs
2024-09-16 23:38:45.744 DBG default: -- Check halted --
2024-09-16 23:38:45.750 DBG default: Exec #2: du -scb /live/aufs/boot
2024-09-16 23:38:45.796 DBG default: Exit #2: 0
2024-09-16 23:38:45.797 DBG default: Basic image: 389831884800 true "/live/boot-dev/antiX/linuxfs.info"
2024-09-16 23:38:45.797 DBG default: Source inodes: 760992 Assumed block size: 4096
2024-09-16 23:38:45.797 DBG default: Minimum space: 540548339 (boot), 392948908032 (root)
2024-09-16 23:38:45.825 DBG default: Exec #3: find -L /usr/share/zoneinfo/posix -mindepth 2 -type f -printf %P\n
2024-09-16 23:38:45.840 DBG default: Exit #3: 0
2024-09-16 23:38:45.840 DBG default: Bash #4: guess-hwclock
2024-09-16 23:38:47.009 DBG default: Exit #4: 0
2024-09-16 23:38:47.010 DBG default: Bash #5: locale -a | grep -Ev '^(C|POSIX)\.?' | grep -E 'utf8|UTF-8'
2024-09-16 23:38:47.021 DBG default: Exit #5: 0
2024-09-16 23:38:47.022 DBG default: Bash #6: ls -1 /home | grep -Ev '^(lost\+found|demo|snapshot)$' | grep -q '[a-zA-Z0-9]'
2024-09-16 23:38:47.030 DBG default: Exit #6: 0
2024-09-16 23:38:47.030 DBG default: check for possible snapshot: true
2024-09-16 23:38:47.031 DBG default: Bash #7: dpkg -s samba | grep '^Status.*ok.*' | sed -e 's/.*ok //'
2024-09-16 23:38:47.058 DBG default: Exit #7: 0
2024-09-16 23:38:47.061 DBG default: Exec #8: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,PTTYPE,PARTTYPENAME,FSTYPE,FSVER,LABEL,MODEL,PARTFLAGS
2024-09-16 23:38:47.082 DBG default: Exit #8: 0
2024-09-16 23:38:47.082 DBG default: Exec #9: parted -lm
2024-09-16 23:38:47.132 DBG default: Exit #9: 0
2024-09-16 23:38:47.132 DBG default: Bash #10: lsblk -T -bJo TYPE,NAME,PATH,UUID,ROTA,DISC-GRAN,SIZE,PHY-SEC,FSTYPE,LABEL /dev/mapper/*
2024-09-16 23:38:47.139 DBG default: SErr #10: "lsblk: /dev/mapper/control: not a block device\n"
2024-09-16 23:38:47.139 DBG default: Exit #10: 32
[/code]
What is happening here that makes that install into / impossible and why does my 68 GB /root now need 390 GB??
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Sep 17, 2024 11:21 am
by fehlix
monamtb wrote: Tue Sep 17, 2024 10:54 am
Hello Fehlix,
I manually partitioned the new laptop ssd with 78 GB / - and 920 GB /home.
I created a new snapshot with all /home files excluded
Upon install the installer now wants 390 GB for /root - and again won't install my /root directory into the / partition I want to use with the 78 GB / partition - even more than last time: with some /home data included it was 226 GB.
QSI gives me that output:
What is happening here that makes that install into / impossible and why does my 68 GB /root now need 390 GB??
Perhaps, post the used size within the ISO as mentioned above with
and
Code: Select all
sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
That would give us a clear indication to compare and maybe something is wrong with the size calcuation.
My candidate would be the calculcation of needed space, as indicate within the log :
Code: Select all
2024-09-16 23:38:45.797 DBG default: Basic image: 389831884800 true "/live/boot-dev/antiX/linuxfs.info"
2024-09-16 23:38:45.797 DBG default: Source inodes: 760992 Assumed block size: 4096
2024-09-16 23:38:45.797 DBG default: Minimum space: 540548339 (boot), 392948908032 (root)
maybe the potential trouble maker size calculation is somewhere related to "Assumed block size: 4096" and based on inodes.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Sep 17, 2024 11:42 am
by DukeComposed
fehlix wrote: Tue Sep 17, 2024 11:21 am
That would give us a clear indication to compare and maybe something is wrong with the size calcuation.
My candidate would be the calculcation of needed space, as indicate within the log :
We still haven't seen a QSI from the host machine being snapshotted, so we have no idea what the existing partition layout is.
If I have a 30 GB / partition and a 360 GB /var partition and I try to clone that file tree to a new system with only a / partition and a /home partition, my / partition is going to be 390 GBs.
As I've said before in this thread, file trees are not disk partitions. Where data exists on a hard disk is just as important as how much data there is on that disk. It sounds like there have been multiple attempts to convert or transpose data from one machine to another, but with a fundamental lack of attention to detail as to precise partitioning requirements and where, exactly, the data exists. A QSI would be invaluable in figuring this out.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 12:58 am
by monamtb
Hello Fehlix and Dukecomposed,
I apologize for my fundamental lack of attention to detail - I can only be as attentive as my technical knowledge reaches - and otherwise I depend on forum members who have that knowledge and help me learn.
The Isomount gives me this output:
Code: Select all
onamtb@mxlinuxmona:~
$ sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
516M /mnt/iso/sq1/./boot
24M /mnt/iso/sq1/./etc
352G /mnt/iso/sq1/./home
1.6G /mnt/iso/sq1/./opt
68M /mnt/iso/sq1/./root
9.6G /mnt/iso/sq1/./usr
200M /mnt/iso/sq1/./var
364G /mnt/iso/sq1/.
QSI from my host machine is:
Code: Select all
[CODE]Snapshot created on: 20240917_1220
System:
Kernel: 6.1.0-25-rt-amd64 [6.1.106-3] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-rt-amd64 root=UUID=<filter> ro quiet splash
resume=UUID=<filter> resume_offset=6895616
Desktop: KDE Plasma v: 5.27.5 info: latte-dock wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-23.3_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: Dell product: Precision 7510 v: N/A serial: <superuser required> Chassis:
type: 9 serial: <superuser required>
Mobo: Dell model: 00V5FJ v: A00 serial: <superuser required> UEFI: Dell v: 1.29.3
date: 09/18/2022
Battery:
ID-1: BAT0 charge: 49.3 Wh (100.0%) condition: 49.3/91.0 Wh (54.2%) volts: 12.2 min: 11.4
model: LGC-LGC3.975 DELL RDYCT69 type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Xeon E3-1535M v5 bits: 64 type: MT MCP arch: Skylake-S level: v3 note: check
built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 800 min/max: 800/3800 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 46398
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: Intel HD Graphics P530 vendor: Dell driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, HDMI-A-1,
HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:191d class-ID: 0300
Device-2: NVIDIA GM107GLM [Quadro M2000M] vendor: Dell driver: N/A alternate: nouveau
non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 01:00.0 chip-ID: 10de:13b0 class-ID: 0300
Device-3: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-11:5
chip-ID: 0bda:5686 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: LG Display 0x049b built: 2015 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel HD Graphics P530 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 1-1:2 chip-ID: 152a:8750 bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: fe01
class-ID: 0403
Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX] vendor: Dell driver: snd_hda_intel
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 10de:0fbc class-ID: 0403
Device-3: Thesycon System & Consulting GmbH D10s type: USB driver: snd-usb-audio
API: ALSA v: k6.1.0-25-rt-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
chip-ID: 8086:15b7 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 02:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 953.87 GiB used: 792.1 GiB (83.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM620 1TB size: 953.87 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: V1.23 temp: 34.9 C scheme: GPT
Partition:
ID-1: / raw-size: 57.22 GiB size: 56.02 GiB (97.90%) used: 50.44 GiB (90.0%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.4 GiB size: 881.25 GiB (98.31%) used: 741.65 GiB (84.2%) fs: ext4
dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 37.24 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 46.0 C pch: 50.0 C mobo: 43.0 C
Fan Speeds (RPM): cpu: 2015 fan-2: 2124
Repos:
Packages: pm: dpkg pkgs: 2693 libs: 1480 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Active apt repos in: /etc/apt/sources.list.d/softmaker.list
1: deb [signed-by=/etc/apt/keyrings/softmaker.gpg] https://shop.softmaker.com/repo/apt stable non-free
Active apt repos in: /etc/apt/sources.list.d/surfshark.list
1: deb https://ocean.surfshark.com/debian stretch main
Info:
Processes: 321 Uptime: 1h 38m wakeups: 2 Memory: 31.24 GiB used: 4.01 GiB (12.8%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
[/code]
I hope that helps to figure out what is wrong here.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 6:51 am
by fehlix
monamtb wrote: Sat Sep 21, 2024 12:58 am
The Isomount gives me this output:
QSI from my host machine is:
Code: Select all
[CODE]Snapshot created on: 20240917_1220
System:
Kernel: 6.1.0-25-rt-amd64 [6.1.106-3] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-25-rt-amd64 root=UUID=<filter> ro quiet splash
resume=UUID=<filter> resume_offset=6895616
Desktop: KDE Plasma v: 5.27.5 info: latte-dock wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-23.3_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: Dell product: Precision 7510 v: N/A serial: <superuser required> Chassis:
type: 9 serial: <superuser required>
Mobo: Dell model: 00V5FJ v: A00 serial: <superuser required> UEFI: Dell v: 1.29.3
date: 09/18/2022
Battery:
ID-1: BAT0 charge: 49.3 Wh (100.0%) condition: 49.3/91.0 Wh (54.2%) volts: 12.2 min: 11.4
model: LGC-LGC3.975 DELL RDYCT69 type: Li-ion serial: <filter> status: full
CPU:
Info: model: Intel Xeon E3-1535M v5 bits: 64 type: MT MCP arch: Skylake-S level: v3 note: check
built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache: L1: 256 KiB
desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 800 min/max: 800/3800 scaling: driver: intel_pstate governor: powersave
cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 bogomips: 46398
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling status: Vulnerable: No microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: Intel HD Graphics P530 vendor: Dell driver: i915 v: kernel arch: Gen-9
process: Intel 14n built: 2015-16 ports: active: eDP-1 empty: DP-1, DP-2, DP-3, HDMI-A-1,
HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:191d class-ID: 0300
Device-2: NVIDIA GM107GLM [Quadro M2000M] vendor: Dell driver: N/A alternate: nouveau
non-free: 530.xx+ status: current (as of 2023-03) arch: Maxwell code: GMxxx process: TSMC 28nm
built: 2014-19 pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s
bus-ID: 01:00.0 chip-ID: 10de:13b0 class-ID: 0300
Device-3: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo bus-ID: 1-11:5
chip-ID: 0bda:5686 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22") s-diag: 582mm (22.93")
Monitor-1: eDP-1 model: LG Display 0x049b built: 2015 res: 1920x1080 hz: 60 dpi: 142 gamma: 1.2
size: 344x194mm (13.54x7.64") diag: 395mm (15.5") ratio: 16:9 modes: 1920x1080
API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel HD Graphics P530 (SKL GT2)
direct-render: Yes
Audio:
Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Dell driver: snd_hda_intel
v: kernel bus-ID: 1-1:2 chip-ID: 152a:8750 bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: fe01
class-ID: 0403
Device-2: NVIDIA GM107 High Definition Audio [GeForce 940MX] vendor: Dell driver: snd_hda_intel
v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 16 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1
chip-ID: 10de:0fbc class-ID: 0403
Device-3: Thesycon System & Consulting GmbH D10s type: USB driver: snd-usb-audio
API: ALSA v: k6.1.0-25-rt-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel port: N/A bus-ID: 00:1f.6
chip-ID: 8086:15b7 class-ID: 0200
IF: eth0 state: down mac: <filter>
Device-2: Intel Wireless 8260 driver: iwlwifi v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
bus-ID: 02:00.0 chip-ID: 8086:24f3 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 953.87 GiB used: 792.1 GiB (83.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Lexar model: SSD NM620 1TB size: 953.87 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: V1.23 temp: 34.9 C scheme: GPT
Partition:
ID-1: / raw-size: 57.22 GiB size: 56.02 GiB (97.90%) used: 50.44 GiB (90.0%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.4 GiB size: 881.25 GiB (98.31%) used: 741.65 GiB (84.2%) fs: ext4
dev: /dev/nvme0n1p3 maj-min: 259:3
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: file size: 37.24 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap
Sensors:
System Temperatures: cpu: 46.0 C pch: 50.0 C mobo: 43.0 C
Fan Speeds (RPM): cpu: 2015 fan-2: 2124
Repos:
Packages: pm: dpkg pkgs: 2693 libs: 1480 tools: apt,apt-get,aptitude,nala pm: rpm pkgs: 0
pm: flatpak pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm main non-free
2: deb http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/skype-stable.list
1: deb [arch=amd64] https://repo.skype.com/deb stable main
Active apt repos in: /etc/apt/sources.list.d/softmaker.list
1: deb [signed-by=/etc/apt/keyrings/softmaker.gpg] https://shop.softmaker.com/repo/apt stable non-free
Active apt repos in: /etc/apt/sources.list.d/surfshark.list
1: deb https://ocean.surfshark.com/debian stretch main
Info:
Processes: 321 Uptime: 1h 38m wakeups: 2 Memory: 31.24 GiB used: 4.01 GiB (12.8%) Init: SysVinit
v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
[/code]
I hope that helps to figure out what is wrong here.
Seems the needed calculation is somehow correct
Code: Select all
2024-09-16 23:38:45.797 DBG default: Minimum space: 540548339 (boot), 392948908032 (root)
which is about 365 GiB
Code: Select all
echo $((392948908032 / 2**30))
365
and 364 GiB as shown on the iso for "/"
Have you tried, first to assign the big sized "/home" partition,
b/c the installer should reduce the needed size for "/" -root by the amount used for "/home" if "/home" was set onto another partition.
If that does not work, it may an be indication some adjustments are needed within the installer re space calculations.
Otherwise, workaround may be to create snapshot, with excluded big data under home.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 10:57 am
by DukeComposed
fehlix wrote: Sat Sep 21, 2024 6:51 am
monamtb wrote: Sat Sep 21, 2024 12:58 am
The Isomount gives me this output:
QSI from my host machine is:
Code: Select all
[CODE]
Partition:
ID-1: / raw-size: 57.22 GiB size: 56.02 GiB (97.90%) used: 50.44 GiB (90.0%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 896.4 GiB size: 881.25 GiB (98.31%) used: 741.65 GiB (84.2%) fs: ext4
dev: /dev/nvme0n1p3 maj-min: 259:3
Seems the needed calculation is somehow correct
Code: Select all
2024-09-16 23:38:45.797 DBG default: Minimum space: 540548339 (boot), 392948908032 (root)
which is about 365 GiB
Code: Select all
echo $((392948908032 / 2**30))
365
and 364 GiB as shown on the iso for "/"
If we take this along with the output from #23:
Code: Select all
onamtb@mxlinuxmona:~
$ sudo du -h --max-depth=1 /mnt/iso/sq1/. | grep -v ^0
516M /mnt/iso/sq1/./boot
24M /mnt/iso/sq1/./etc
352G /mnt/iso/sq1/./home
1.6G /mnt/iso/sq1/./opt
68M /mnt/iso/sq1/./root
9.6G /mnt/iso/sq1/./usr
200M /mnt/iso/sq1/./var
364G /mnt/iso/sq1/.
we can say for sure we know three things:
- OP's /home directory is nearly 900 GiB on a 1 TB drive. MX Snapshot needs roughly 2x the total used space to build an ISO, so a full snapshot of this system that includes /home cannot be made on this drive.
- OP's /mnt/iso/sql/ directory is 364 GB. The /mnt/iso/sql/home directory is still 352 GB in size, which means some parts of /home are being excluded, but not everything in /home is being left out.
- QSI shows only three partitions: root, /boot/efi, and /home.
Point (2) and (3) answers the earlier question "[W]hy does my 68 GB /root now need 390 GB??" 364 - 352 = 12, so the target machine needs a minimum of 12 GB to install correctly and the rest is /home data. It is imperative that OP either (a) make a single partition large enough to store 364 GB of data or (b) explicitly partition the target machine to allow for 12 GB or more for root, room for an EFI partition, and a second partition big enough for 352 GB of /home data.
Repartitioning the target machine can be done in any number of ways. fdisk, parted, or gparted are all good choices. I'd run "sudo parted /dev/sda p" first to know what the current partition table looks like, and I'd bet right now it doesn't look at all like the host machine's partition table.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 12:45 pm
by fehlix
Maybe someone would try to reproduce the mentioned issue:
* Create a personal snapshot with a big enough home with data, e.g bigger then 60GB
* Now prepare "/"-root partition e.g. size 30GB
and /home partition e.g with 90GB
And try to install with separate /home.
And the question: Would the installer complain about a size 30GB for "/"- root as not being big enough?
I can't currently try this out myself, as I don't have such setup, but may be able to prepare in about 2 weeks, after re-arranging some installs.
Thanks
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 3:08 pm
by monamtb
Hello Fehlix,
Just for reference - on this second install attempt I checked the "leave out all data of the home partition" while creating the snapshot - so no /home data should have been included in the snapshot.
I have no idea why that /home directory should hold so much data when I explicitly did exclude all home date before creating the snapshot.
But as you said, while partitioning I always created the / directory on my respectively sized partition of the target system first, then the /home directory as my second, large partition on the target system.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 3:20 pm
by fehlix
monamtb wrote: Sat Sep 21, 2024 3:08 pm
Hello Fehlix,
Just for reference - on this second install attempt I checked the "leave out all data of the home partition" while creating the snapshot - so no /home data should have been included in the snapshot.
I have no idea why that /home directory should hold so much data when I explicitly did exclude all home date before creating the snapshot.
But as you said, while partitioning I always created the / directory on my respectively sized partition of the target system first, then the /home directory as my second, large partition on the target system.
maybe you didn't exclude properly. Perhaps tell us where your data are and show they way you tried to exclude.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 3:55 pm
by DukeComposed
fehlix wrote: Sat Sep 21, 2024 3:20 pm
maybe you didn't exclude properly. Perhaps tell us where your data are and show they way you tried to exclude.
MX Snapshot creates a log file, which we also haven't seen yet.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Sep 21, 2024 4:38 pm
by fehlix
DukeComposed wrote: Sat Sep 21, 2024 3:55 pm
fehlix wrote: Sat Sep 21, 2024 3:20 pm
maybe you didn't exclude properly. Perhaps tell us where your data are and show they way you tried to exclude.
MX Snapshot creates a log file, which we also haven't seen yet.
That would indeed help to see what was excluded. And in conjunction with the yet to be provided details of where the big “data” is actually located, that would give a clue as to what went wrong with the exclusion attempt.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Sep 22, 2024 4:18 am
by monamtb
If I try to insert the log file content here it gets rejected because it is too long - also when I insert it as code it gets rejected the same way.
How can I get the log file into the conversation for you to check???
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Sep 22, 2024 4:20 am
by monamtb
All of my data is stored on home.
That is all I know because whatever I do I save it in my home folder.
I tried to exclude all my home data using the checkbox in the MX snapshot utility - just as it was recommended.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Sep 22, 2024 4:54 am
by DukeComposed
monamtb wrote: Sun Sep 22, 2024 4:18 am
If I try to insert the log file content here it gets rejected because it is too long - also when I insert it as code it gets rejected the same way.
I'll refer you to How To Ask Questions The Smart Way:
Volume is not precision: "This end is not served by simply dumping huge volumes of code or data into a help request."
You know enough about the problem at this point to be able to read the log file yourself and identify key components that are relevant to your situation. You know there's been questions raised about what you're excluding in the snapshot, and about what is being included. Take this as a starter and look at the log file and see what looks related to that and we'll go from there.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Sep 22, 2024 4:32 pm
by juwido
I think the hidden .files in the home folder are not excluded, as they are needed for the settings of the snapshoted programs...
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Sep 22, 2024 4:59 pm
by DukeComposed
juwido wrote: Sun Sep 22, 2024 4:32 pm
I think the hidden .files in the home folder are not excluded, as they are needed for the settings of the snapshoted programs...
Don't speculate. Your system has disk usage utilities installed. Check for Disk Usage Analyzer in the menu, or try to run "baobab" from a command line. If that's not there, you can install QDirStat ("apt install qdirstat") and run that. You always have the "du" command you can run against a directory. "du -sh /home/user/.config" for example will tell you how large the ~/.config directory is. Mine is 680 MB.
Code: Select all
$ du -sh ~/.config
680M /home/user/.config
OK, why is my ~/.config 680 megs? I can keep drilling down into this.
Code: Select all
$ du -s ~/.config/* | sort -rn | head
626200 /home/user/.config/emacs
63391 /home/user/.config/Tracktion
3944 /home/user/.config/libreoffice
1022 /home/user/.config/balena-etcher
[snip]
OK, so it's mostly Emacs's fault. Makes sense. Graphical tools can do the same thing interactively. Use them.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 11:30 am
by monamtb
DukeComposed wrote: Sun Sep 22, 2024 4:54 am
monamtb wrote: Sun Sep 22, 2024 4:18 am
If I try to insert the log file content here it gets rejected because it is too long - also when I insert it as code it gets rejected the same way.
I'll refer you to How To Ask Questions The Smart Way:
Volume is not precision: "This end is not served by simply dumping huge volumes of code or data into a help request."
You know enough about the problem at this point to be able to read the log file yourself and identify key components that are relevant to your situation. You know there's been questions raised about what you're excluding in the snapshot, and about what is being included. Take this as a starter and look at the log file and see what looks related to that and we'll go from there.
If I could solve that myself I wouldn't ask it here in the forum - and no - I cannot identify key components since I have no programming skills - or otherwise I would know why the /root and / files are so large although I excluded all files from my /home directory as recommended here.
The "Smart Way" you referred me to sounds like for programmers - not for someone unskilled like me.
If you ask me to get the first 100 lines that I can do - but since I have no idea what could be relevant I might just leave out a piece of info that could be important since I don't understand most of the lines in a .log file output.
The du command gives me that output:
Code: Select all
monamtb@mxlinuxmona:~
$ du -sh ~/.config
1.2G /home/monamtb/.config
I copy the beginning of the log file here - yet the output doesn't make sense for me since I only have a 65 GB /root and I can't understand for the world why it wants 270 something GB and why some 64 GB are excluded - and instead of 27 GB it wants 270 GB:
Code: Select all
2024-09-17 12:19:14.530 DBG: mx-snapshot version: 24.9.03
2024-09-17 12:19:14.557 DBG: grep -oP '(?<=DISTRIB_ID=).*' /etc/lsb-release
2024-09-17 12:19:14.564 DBG: cut -f1 -d'_' /etc/mx-version
2024-09-17 12:19:14.570 DBG: grep -oP '(?<=DISTRIB_CODENAME=).*' /etc/lsb-release
2024-09-17 12:19:14.577 DBG: /usr/share/mx-snapshot/scripts/snapshot-bootparameter.sh | tr '
' ' '
2024-09-17 12:19:14.619 DBG: +++ QString Settings::getFilename() const +++
2024-09-17 12:19:14.619 DBG: +++ void Settings::selectKernel() +++
2024-09-17 12:19:14.666 DBG: +++ void MainWindow::setup() +++
2024-09-17 12:19:14.675 DBG: +++ void MainWindow::loadSettings() +++
2024-09-17 12:19:14.675 DBG: +++ void MainWindow::listFreeSpace() +++
2024-09-17 12:19:14.676 DBG: - Free space on /home, where snapshot folder is placed: 254.36GiB
2024-09-17 12:19:14.676 DBG: The free space should be sufficient to hold the compressed data from / and /home
If necessary, you can create more available space
by removing previous snapshots and saved copies:
0 snapshots are taking up 0MiB of disk space.
2024-09-17 12:19:33.009 DBG: +++ void MainWindow::listFreeSpace() +++
2024-09-17 12:19:33.009 DBG: - Free space on /media/monamtb/ISOSTAR/snapshot, where snapshot folder is placed: 835.42GiB
2024-09-17 12:19:33.010 DBG: The free space should be sufficient to hold the compressed data from / and /home
If necessary, you can create more available space
by removing previous snapshots and saved copies:
0 snapshots are taking up 0MiB of disk space.
2024-09-17 12:19:43.173 DBG: +++ void MainWindow::listFreeSpace() +++
2024-09-17 12:19:43.174 DBG: - Free space on /media/monamtb/ISOSTAR, where snapshot folder is placed: 835.42GiB
2024-09-17 12:19:43.174 DBG: The free space should be sufficient to hold the compressed data from / and /home
If necessary, you can create more available space
by removing previous snapshots and saved copies:
0 snapshots are taking up 0MiB of disk space.
2024-09-17 12:19:47.587 DBG: +++ void Settings::selectKernel() +++
2024-09-17 12:19:47.608 DBG: glxinfo | grep -q NVIDIA
2024-09-17 12:20:20.185 DBG: grep ^CONFIG_SQUASHFS_LZ4=y /boot/config-6.1.0-25-rt-amd64
2024-09-17 12:20:23.871 DBG: +++ bool Settings::checkSnapshotDir() const +++
2024-09-17 12:20:23.871 DBG: mkdir -p "/media/monamtb/ISOSTAR/snapshot"
2024-09-17 12:20:29.580 DBG: chown $(logname): "/media/monamtb/ISOSTAR/snapshot"
2024-09-17 12:20:29.608 DBG: +++ bool Settings::checkTempDir() +++
2024-09-17 12:20:29.608 DBG: +++ static bool Settings::isOnSupportedPart(const QString&) +++
2024-09-17 12:20:29.608 DBG: Detected partition: "ext4" Supported part: true
2024-09-17 12:20:29.608 DBG: +++ static QString Settings::largerFreeSpace(const QString&, const QString&, const QString&) +++
2024-09-17 12:20:29.608 DBG: +++ static QString Settings::largerFreeSpace(const QString&, const QString&) +++
2024-09-17 12:20:29.609 DBG: +++ static QString Settings::largerFreeSpace(const QString&, const QString&) +++
2024-09-17 12:20:29.609 DBG: Work directory is placed in "/media/monamtb/ISOSTAR/snapshot"
2024-09-17 12:20:29.609 DBG: +++ void Settings::excludeDesktop(bool) +++
2024-09-17 12:20:29.609 DBG: runuser monamtb -c "xdg-user-dir DESKTOP" 2>/dev/null
2024-09-17 12:20:29.642 DBG: +++ void Settings::excludeDocuments(bool) +++
2024-09-17 12:20:29.642 DBG: runuser monamtb -c "xdg-user-dir DOCUMENTS" 2>/dev/null
2024-09-17 12:20:29.676 DBG: +++ void Settings::excludeDownloads(bool) +++
2024-09-17 12:20:29.676 DBG: runuser monamtb -c "xdg-user-dir DOWNLOAD" 2>/dev/null
2024-09-17 12:20:29.709 DBG: +++ void Settings::excludeFlatpaks(bool) +++
2024-09-17 12:20:29.709 DBG: +++ void Settings::excludeMusic(bool) +++
2024-09-17 12:20:29.709 DBG: runuser monamtb -c "xdg-user-dir MUSIC" 2>/dev/null
2024-09-17 12:20:29.744 DBG: +++ void Settings::excludeNetworks(bool) +++
2024-09-17 12:20:29.744 DBG: +++ void Settings::excludePictures(bool) +++
2024-09-17 12:20:29.744 DBG: runuser monamtb -c "xdg-user-dir PICTURES" 2>/dev/null
2024-09-17 12:20:29.778 DBG: +++ void Settings::excludeSteam(bool) +++
2024-09-17 12:20:29.778 DBG: +++ void Settings::excludeVideos(bool) +++
2024-09-17 12:20:29.778 DBG: runuser monamtb -c "xdg-user-dir VIDEOS" 2>/dev/null
2024-09-17 12:20:29.812 DBG: +++ void Settings::excludeVirtualBox(bool) +++
2024-09-17 12:20:29.812 DBG: +++ void Settings::otherExclusions() +++
2024-09-17 12:20:29.816 DBG: +++ void Work::setupEnv() +++
2024-09-17 12:20:29.816 DBG: mountpoint /boot
2024-09-17 12:20:29.825 DBG: /boot is not a mountpoint
2024-09-17 12:20:29.825 DBG: +++ static bool Work::checkInstalled(const QString&) +++
2024-09-17 12:20:29.825 DBG: dpkg-query -W -f='${Status}' mx-installer | grep 'install ok installed'
2024-09-17 12:20:29.895 DBG: installed-to-live -b /.bind-root start bind=/home live-files version-file adjtime read-only
2024-09-17 12:20:31.251 DBG: Calculating total size of excluded files...
2024-09-17 12:20:31.252 DBG: du -sxc {/.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/boot/grub/,/.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/var/cache/apt/archives/partial/,/.bind-root/var/cache/apt-xapian-index/index.*,/.bind-root/var/cache/debconf/*-old,/.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/var/cache/brightness-settings-cache/,/.bind-root/var/lib/flatpak/,/.bind-root/var/lib/flatpak/.*,/.bind-root/etc/NetworkManager/system-connections/} 2>/dev/null |tail -1 |cut -f1
2024-09-17 12:20:31.368 DBG: 651940
2024-09-17 12:20:31.368 DBG: Calculating size of root...
2024-09-17 12:20:31.368 DBG: du -sx /.bind-root 2>/dev/null |tail -1 |cut -f1
2024-09-17 12:20:35.663 DBG: 52876992
2024-09-17 12:20:35.664 DBG: SIZE 52876992
2024-09-17 12:20:35.664 DBG: SIZE ROOT 52876992
2024-09-17 12:20:35.664 DBG: SIZE EXCLUDES 651940
2024-09-17 12:20:35.664 DBG: COMPRESSION 52
2024-09-17 12:20:35.664 DBG: SIZE NEEDED 27157027
2024-09-17 12:20:35.664 DBG: SIZE FREE 875999512
2024-09-17 12:20:35.664 DBG: +++ void Work::checkNoSpaceAndExit(quint64, quint64, const QString&) +++
2024-09-17 12:20:35.665 DBG: Needed space: 27157027
2024-09-17 12:20:35.665 DBG: Free space : 875999512 on "/media/monamtb/ISOSTAR/snapshot"
2024-09-17 12:20:35.665 DBG: Copying the new-iso filesystem...
2024-09-17 12:20:35.665 DBG: tar xf /usr/lib/iso-template/iso-template.tar.gz
2024-09-17 12:20:35.962 DBG: cp /usr/lib/iso-template/template-initrd.gz iso-template/antiX/initrd.gz
2024-09-17 12:20:35.971 DBG: cp /boot/vmlinuz-6.1.0-25-rt-amd64 iso-template/antiX/vmlinuz
2024-09-17 12:20:35.988 DBG: +++ void Work::replaceMenuStrings() +++
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 11:58 am
by CharlesV
I am going to suggest to install qdirstat and run that. It will show you where all the data is and you can snap a picture and show that if you need too.
I agree with felix that it sounds like something in home was not excluded. But understanding where / what is taking space will help isolate this.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 12:07 pm
by fehlix
monamtb wrote: Tue Oct 01, 2024 11:30 am
I copy the beginning of the log file here
Pls. provide the whole log-file as compressed zip file. FWIW, QSI-tool -> select mx-snapshot.log
and perhaps keep Quick System Info selected and click on the “Save” button at the bottom left
to get save a zip-file
Also any specific reason why you have manually installed a real-time kernel: /boot/vmlinuz-6.1.0-25-rt-amd64
To attached the zip file select attach file within the full post editor and navigate to the save-folder (maybe the home folder),
you may need to change a file-filter from "*.odt" to "All Files" to allow selecting the zip file.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 2:32 pm
by monamtb
Hello Fehlix and Charles V,
I wasn't aware that I used a special kernel - I never did anything like that since I don't know how to do it anyway - I just installed MX 23.3 - that was it.
The screenshots are not shown when I use the P to post the images and I don't know how to include them using the image button from the menu - I don't get to choose the folder they are located in on my laptop
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 2:52 pm
by fehlix
monamtb wrote: Tue Oct 01, 2024 2:32 pm
I wasn't aware that I used a special kernel - I never did anything like that since I don't know how to do it anyway - I just installed MX 23.3 - that was it.
Maybe somone else is using your computer? Where did you got the MX-iso from and what filename was it exactly?
None of MX release iso, do ship with a realtime-kernel, at least non I'm aware of.
monamtb wrote: Tue Oct 01, 2024 2:32 pm
The png images that spectacle made are not shown when I use the P to post the images and I don't know how to include them using the image button from the menu - I don't get to choose the folder they are located in on my laptop
Do you see within qdirstat, where your big files are stored? And did you exclude those?
Thanks for the QSI. I thought you wanted to send the snapshot.log also?
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 2:57 pm
by monamtb
I clicked to QSI and snapshot log to create the text file...
I'll try again......
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 2:59 pm
by davidy
If you know you put everything in home then you know what needs to be copied OUT of home so that you can make a bootable snapshot. The smaller your OS disk actual data size, the better. Putting everything incl. the kitchen sink on home is a recipe for disaster. A 1TB nvme OS disk with root,home, and a swap will work for anybody anywhere for any purpose whatsoever providing they also have a secondary data drive to actually handle whatever load (your data here) they are giving it. Either you copy stuff off or you install clean. Easy decision.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:00 pm
by monamtb
I only take isos from the MX Linux website and no one uses the laptop but me.
How that came about I really have no clue.
Maybe at the time when I tried to install a live system I messed something up - and instead of the USB it is now using it also on my laptop????
How can I change that - since it seems to be a bad thing?
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:09 pm
by monamtb
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:10 pm
by monamtb
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:13 pm
by Eadwine Rose
As far as I know you cannot hotlink from google drive. That, and the images will exceed the maximum sizes stated in the forum rules. There is an add image to this post link at the bottom below the post entry area, you can use that.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:17 pm
by davidy
15 years ago when I was still running windows I NEVER used the default 'music, documents, pictures etc.' folders. Linux is no different now. The only things that get put in home are what the OS itself may put there automatically. I keep nothing on the OS disk but that which is required for the device to boot and show me a desktop. That is why I have 97% of my disk as free space, on purpose. 2 heads like 2 drives is better than one. Makes backing up and taking snaps a breeze. Simple reason if the drive fails I lose nothing. Backups are critical if you use computers and so are multiple drives to separate the data from the OS itself.
That's also why I love portable software like appimages. They go anywhere BUT the OS disk. Makes backups smaller and therefore faster too. Win win as far as I'm concerned. Good luck with your laptop and don't be shy about segregating the OS from actual data you can move around.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:18 pm
by monamtb
The largest file in my home folder is the iso snapshot I made under /Templates
I tried to put it onto an external drive but then the snapshot creation always aborted.
And I always put my /home folder on a separate partition.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:32 pm
by davidy
I consider 'home' to be required for the OS so as far as I'm concerned it IS the OS, just like root and the occassional swap. When ubuntu first came out I was concerned with partitoning schemes but soon realized that by simply keeping any actual data on a completely separate drive was the ticket. Worrying about partition schemes I leave to the installer. Makes my life easy. MX will part for you. You just need to put your documents on a different disk. If you only have one then you should only have an OS partition scheme, meaning one just big enough to run the OS, and the other part for actual data. Separating home from root and then making it so big you can't really use it properly is a waste of your time as this thread is witness too (it aint a catch all). Home defines configurations for a user and the applications he may run. Without home, no user, without user, no boot. The user is not the data itself though and neither should be home.
The default folders in your home directory are for your convenience and that's all. If I were to put all my data in 'home' it would have to be well over 3TB and that's just a folder now isn't it? If you only have a single drive you need to invest in external usb nvme's or better yet get a nas. With at least a 2.5GbE eth0 connection you will hardly notice your data is elsewhere.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 3:42 pm
by fehlix
monamtb wrote: Tue Oct 01, 2024 3:18 pm
The largest file in my home folder is the iso snapshot I made under /Templates
I tried to put it onto an external drive but then the snapshot creation always aborted.
And I always put my /home folder on a separate partition.
My question was, do you now see with qdirstat, where you big files are located.
And if yes, either remove those if not needed or exclude during snapshot creation.
If you don't understand or know how to do this, best would be to formulate as a question,
in order to avoid people to guess.
Also I'm not sure, if you found something was installed like a realtime kernel,
which you have no clue where this is coming from - maybe reinstall from scratch,
with latest ISO, so you have a clear start.
And do validate the downloaded iso, as explained within the wiki.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 4:22 pm
by DukeComposed
monamtb wrote: Tue Oct 01, 2024 11:30 am
no - I cannot identify key components since I have no programming skills - or otherwise I would know why the /root and / files are so large
This is false, and makes no logical sense. Programming skills are not necessary here. You need to know the difference between a file and a directory, and between a file system and a mountpoint, and you already do, so you really do have the knowledge to tackle this. I believe in you.
monamtb wrote: Tue Oct 01, 2024 11:30 am
The "Smart Way" you referred me to sounds like for programmers - not for someone unskilled like me.
This is false and explained in the introduction of the document. You can do this.
monamtb wrote: Tue Oct 01, 2024 11:30 am
I copy the beginning of the log file here - yet the output doesn't make sense for me since I only have a 65 GB /root and I can't understand for the world why it wants 270 something GB and why some 64 GB are excluded
A number of disk usage analysis tools have been mentioned in this thread: du and QDirStat for instance, with examples, by myself and others. I think you need to sit down and find, and document, what your file systems look like so you can start to understand where you've put your data. To quote that introduction I mentioned: "It's simply not efficient for us to try to help people who are not willing to help themselves." You have the tools you need to solve this at your disposal. No programming needed, just a little bit of elbow grease.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Tue Oct 01, 2024 5:47 pm
by CharlesV
monamtb wrote: Tue Oct 01, 2024 3:18 pm
The largest file in my home folder is the iso snapshot I made under /Templates
I tried to put it onto an external drive but then the snapshot creation always aborted.
And I always put my /home folder on a separate partition.
OK, so 334GB in *** TEMPLATES *** and you put your iso snapshot there ? Delete it! Or move it off to a Removable Drive if you want to save it... but that is not a good place to store it!
Note: Templates is NOT excluded with any of the check boxes NOR in the default snapshot exclude list. So that folder is a big problem in you current state / config
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sun Oct 13, 2024 9:38 am
by monamtb
Hello to all helping me out here
I wanted to give a big thank you to everybody who was assisting me in finding my way through that jungle.
I think I understand a bit more about what to use each program for now.
I went with the strategy of making a clean install - took me more than a week to get everything to work the way it did on my old laptop.
I will create regular Backups with Lucky Backup - and else I will make a snapshot of my system without home to avoid setting up my base system again - like I had to do now and not have any additional GB load to create that snapshot.
I think that makes most sense for me going about this way with all things I have learned from all of you so far.
I had never tried cloning a hard disk and as long as the strategy I decided for now works, I intent to keep it that way.
Again, big heart felt thanks to all who gave their best to help me out and helped me to finally decide which concept I want to use from now on in terms of Back up and Snapshots.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Oct 14, 2024 3:57 am
by monamtb
CharlesV wrote: Tue Oct 01, 2024 5:47 pm
monamtb wrote: Tue Oct 01, 2024 3:18 pm
The largest file in my home folder is the iso snapshot I made under /Templates
I tried to put it onto an external drive but then the snapshot creation always aborted.
And I always put my /home folder on a separate partition.
OK, so 334GB in *** TEMPLATES *** and you put your iso snapshot there ? Delete it! Or move it off to a Removable Drive if you want to save it... but that is not a good place to store it!
Note: Templates is NOT excluded with any of the check boxes NOR in the default snapshot exclude list. So that folder is a big problem in you current state / config
Hello Charles,
I created another snapshot of the new system - and when I tried to install it a similar incident happened - I couldn't get past 170 GB for /root - while I believed all folders of /home excluded.
Learning about the templates folder from you and qdirstat I double checked my home folder again - and I put quite some data in the /public folder - which showed up using quite an amount on the snapshot doing the same thing as before - creating a large snapshot with a lot of /root GB space needed.
So, I guess the public folder is also not included by the "remove home folder files" - which kind of doesn't make sense to me!
Why aren't all home folder files and directories included by default when I check the box "Exclude /home folder directories (files)" whenc I put this checkmark on MX Snapshot?
That would have prevented from my problems being created in the first place!!
Maybe another checkbox can be implemented saying "Exclude complete /home folder content"???
The new snapshot with /home/public excluded now made my /root section come down to 19 GB during install - so my /home/public folder and my /home/templates folder where the culprits!!!
Again - a big thank you to everybody who helped me along figuring out what was wrong with mi idea of snapshots - correct snapshot procedure - and correct backup strategy.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Oct 14, 2024 5:01 am
by DukeComposed
monamtb wrote: Mon Oct 14, 2024 3:57 am
I put quite some data in the /public folder - which showed up using quite an amount on the snapshot doing the same thing as before
So, I guess the public folder is also not included by the "remove home folder files" - which kind of doesn't make sense to me!
Be very clear here when you answer: Did you put the data under /public, or did you put the data under /home/monamtb/Public? Because you know those are two different locations and only one of them is under /home.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Mon Oct 14, 2024 7:51 am
by fehlix
monamtb wrote: Mon Oct 14, 2024 3:57 am
So, I guess the public folder is also not included by the "remove home folder files" - which kind of doesn't make sense to me!
Maybe you did not read properly what was stated on the screen:
snapshot-exclude-all-marked-en.jpg
When you click "All of the above", only those items are excluded as shown nothing else.
Or maybe it is a translation issue, e.g here in German:
snapshot-exclude-all-marked-de.jpg
The shown text makes it very clear, to manually exclude any other directory or file(s) manually,
by hitting the "Edit Exclusion File" button to edit the exclusion list file.
monamtb wrote: Mon Oct 14, 2024 3:57 am
Why aren't all home folder files and directories included by default when I check the box "Exclude /home folder directories (files)" whenc I put this checkmark on MX Snapshot?
That would have prevented from my problems being created in the first place!!
In case you don't understand what's on the screen clearly stated, maybe ask in the forum if something is unclear
or the translation makes no sense, which may happen.
E.g German translation for "Desktop" (which means the~/Desktop folder)
is shown on the screen as "Benutzeroberfläche", which is rather confusion,
b/c the Desktop folder is translated as "Schreibtisch" at least in "German locale for Germany" (=de_DE) maybe different in Austria or other German dialects.
monamtb wrote: Mon Oct 14, 2024 3:57 am
Maybe another checkbox can be implemented saying "Exclude complete /home folder content"???
The exclusion list is really simple to understand. Also there may always be some folders or other files the user want to keep or exclude.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Sat Jan 18, 2025 11:43 am
by atomick
Best thought to action per "Excluding 'LARGE FILES' "
on 2nd page of Snapshot menu to create - look at the bottom. Select Resetting accounts (for Distribution to Others). this excludes most all primary all /home/userAccount dirs.
flash this using the "Live USB Maker" . Flash your created S/S-image and it can run the same as your Vanilla .iso
process is much all the same to install so username hostname time question /user -name/passwd / root /passwd all the same the continue and finish all the same.
Also if to be detailed and cover for all question. Same Page in the middle left of this option screen is "Edit Exclusion File" This is the complete list Snapshot knows what NOT
to include or negated into the snapshot result .iso file. This is a text file found /etc/mx-snapshot-exclude.list > This can be now edited by sudo nano mx-snapshot-exclude.list or
vi/vim this same file vi mx-snapshot-exclude.list cursor all down and back up and view carefully to current syntax and format to entries and how set. Smart thing to do is.
sudo cp mx-snapshot-exclude.list mx-snapshot.exclude.list.org (always create a backup when touching anything in /etc/ dir first. )
eg: I add in this to exclude Virtualbox from this keeping my VBox.guest images out of the snapshot. cursor down too: #Entries below can be edited by you the user I add
home/*/VBoxVMs
home/*/.cache/* < there already is an entry this is the way to remove its content of no use per snapshot.
- follow this format if you have say .bin created for your own personal files in /home/me-acct/.bin add this then
home/*/.bin/* - keep to this syntax and run your snapshot and check size. In common terms selecting Resetting accounts - size should end up around 3.4-4gig pretty much
- all your installed apps will be added nice feature results of this size compared to the original vanilla mx-23.xyz.iso file you originally downloaded.
Hope this helps all as a direct yet an eye full but copy and practice. there are features to either. Consider as well - on the 1st page. if you have a 2nd partition or full 2nd hard drive
set the entry SnapShot Location .. default shows /home/snapshot click in this box and change it too /myBigdrive/backups or an archive dir. just the 1st name. Snapshot will
auto-magically create the snapshot directory for your image to dump out too when all done using /tmp as the temp workbench creating the snapshot. hence
/myBigdrive/backups/snapshot will result when its all done. If you do have a 2nd SSD or HD or even mounted ext-usb-device with an External SSD and MX sees this then point the snapshot to that mounted drive eg: /mybigdrive/backups all the same. just examples how too.
Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??
Posted: Thu Apr 17, 2025 12:08 pm
by monamtb
Hello Duke,
I put it in my /home/public folder - since I stay away from messing around with anything else than my /home directory.
DukeComposed wrote: Mon Oct 14, 2024 5:01 am
monamtb wrote: Mon Oct 14, 2024 3:57 am
I put quite some data in the /public folder - which showed up using quite an amount on the snapshot doing the same thing as before
So, I guess the public folder is also not included by the "remove home folder files" - which kind of doesn't make sense to me!
Be very clear here when you answer: Did you put the data under /public, or did you put the data under /home/monamtb/Public? Because you know those are two different locations and only one of them is under /home.