MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

Help with the version of MX KDE officially released by the Development Team.
When asking for help, use Quick System Info from MX Tools. It will be properly formatted using the following steps.
1. Click on Quick System Info in MX Tools
2. Right click in your post and paste.
Message
Author
User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#21 Post 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

Code: Select all

sudo isomount snapshot.iso
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.

User avatar
DukeComposed
Posts: 1506
Joined: Thu Mar 16, 2023 1:57 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#22 Post 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.

monamtb
Posts: 119
Joined: Sat Oct 26, 2019 9:03 am

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#23 Post 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.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#24 Post by fehlix »

monamtb wrote: Sat Sep 21, 2024 12:58 am The Isomount gives me this output:

Code: Select all

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.
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 "/"

Code: Select all

364G    /mnt/iso/sq1/.
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.

User avatar
DukeComposed
Posts: 1506
Joined: Thu Mar 16, 2023 1:57 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#25 Post 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:

Code: Select all

364G    /mnt/iso/sq1/.
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 "/"

Code: Select all

364G    /mnt/iso/sq1/.
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:
  1. 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.
  2. 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.
  3. 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.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#26 Post 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

monamtb
Posts: 119
Joined: Sat Oct 26, 2019 9:03 am

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#27 Post 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.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#28 Post 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.

User avatar
DukeComposed
Posts: 1506
Joined: Thu Mar 16, 2023 1:57 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#29 Post 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.

User avatar
fehlix
Developer
Posts: 12886
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX Snapshot tool usage for migrating my system to a new laptop - snapshot or backup tool??

#30 Post 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.

Post Reply

Return to “MX KDE Official Release”