Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[solved] mx-snapshot 8.9 FAT32 et NTFS

Help for Current Versions of MX
Message
Author
mimimx
Forum Novice
Forum  Novice
Posts: 13
Joined: Wed Jun 07, 2017 8:49 am

[solved] mx-snapshot 8.9 FAT32 et NTFS

#1 Post by mimimx » Fri Sep 21, 2018 7:40 am

Hello
Since version 18.8 snapshots backups become impossible on FAT 32 and NTFS while it was handy when you have a USB key and a PC under Windows.
Do you intend to allow this again

Thank you for this development

(MX linux 17.1)
Last edited by mimimx on Sun Sep 23, 2018 3:08 pm, edited 1 time in total.

User avatar
dolphin_oracle
Forum Veteran
Forum Veteran
Posts: 10045
Joined: Sun Dec 16, 2007 1:17 pm

Re: mx-snapshot 8.9 FAT32 et NTFS

#2 Post by dolphin_oracle » Fri Sep 21, 2018 8:29 am

mimimx wrote:
Fri Sep 21, 2018 7:40 am
Hello
Since version 18.8 snapshots backups become impossible on FAT 32 and NTFS while it was handy when you have a USB key and a PC under Windows.
Do you intend to allow this again

Thank you for this development

(MX linux 17.1)
what do you mean by impossible? the changes in 18.8 shouldn't affect anything that was possible before.

Of course, if the iso is too large, fat32 can't be used due to file size limitations, but those shouldn't affect NTFS unless the usb key is too small.
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad T530 - MX-17
lenovo s21e & 100s - antiX-17, MX17(live-usb)
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 9177
Joined: Wed Jul 12, 2006 1:42 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#3 Post by Adrian » Fri Sep 21, 2018 8:36 am

We make it possible to save to non-Linux file systems only on August 12. So what happened for you between August 12 and now that you cannot save anymore to FAT32 (BTW, you cannot write files larger than 4GB on FAT32) and NTFS? Any error message? You cannot select the partition? Give us a clue what's going on...

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2380
Joined: Wed Apr 11, 2018 5:09 pm

Re: mx-snapshot 8.9 FAT32 et NTFS

#4 Post by fehlix » Fri Sep 21, 2018 9:11 am

mimimx wrote:
Fri Sep 21, 2018 7:40 am
Hello
... snapshots backups become impossible on FAT 32 and NTFS ...
I do see three theoretical possibilities for your "snapshots backups become impossible" :
  • 1st : the FAT32/NTFS partion is simply not mounted, so you cannot select the snapshot target-directory on that drive
  • 2nd: the NTFS partion was made by this other OS readonly, so you cannot create a snapshot there
  • 3rd: The snapshot might be bigger in size than 4GB, which is a FAT32 max size limit of files
But perhaps you can enlight us, what other error messages you might have seen.
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

mimimx
Forum Novice
Forum  Novice
Posts: 13
Joined: Wed Jun 07, 2017 8:49 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#5 Post by mimimx » Fri Sep 21, 2018 9:52 am

Thank you for your answers

I tried to do 4 snapshots
1- with mx-snaphot 8.8 on NTFS OK iso 3.2 GB
2- with mx-snaphot 8.9 on NTFS memory saturated process stops at 30 %
3- with mx-snaphot 8.9 on FAT 32 memory saturated process stopped at 30 %
4- with mx-snaphot 8.9 on ext 4 OK iso 3.2 GB

mimimx
Forum Novice
Forum  Novice
Posts: 13
Joined: Wed Jun 07, 2017 8:49 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#6 Post by mimimx » Fri Sep 21, 2018 10:17 am

I specify that my system works on USB key in FAT 32 of 14 GB and that the snaphot backups are made on HDD of my PC on which is the USB key

User avatar
fehlix
Forum Guide
Forum Guide
Posts: 2380
Joined: Wed Apr 11, 2018 5:09 pm

Re: mx-snapshot 8.9 FAT32 et NTFS

#7 Post by fehlix » Fri Sep 21, 2018 11:04 am

mimimx wrote:
Fri Sep 21, 2018 10:17 am
I specify that my system works on USB key in FAT 32 of 14 GB and that the snaphot backups are made on HDD of my PC on which is the USB key
This "my system works on USB key in FAT32" means you have created one USB key with MX-17.1_August and another one with MX-17.1_September ISO, right? Which architecure i386 or x64_86?
Do you run from this LiveUSB with persitence or without?
Have you made a system update before running MX Snapshot tool?
Would you tell us how you created both USB keys.
And last but not least, please show us the system information
by pasting the output of this command

Code: Select all

inxi -Fxz
And do post the text output between the code-tags [code] here [/code]
please.
Thanks
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Richard
Posts: 2239
Joined: Fri Dec 12, 2008 10:31 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#8 Post by Richard » Fri Sep 21, 2018 12:51 pm

mimimx wrote:
Fri Sep 21, 2018 10:17 am
I specify that my system works on USB key in FAT 32 of 14 GB and that the snaphot backups are made on HDD of my PC on which is the USB key
Yes, I can create a partition over 4 GB with FAT; however,
I have never been able to create a USB when the ISO is a bit over 4 GB.

I think I did once with a 4.1 GB ISO, but that may just be faulty memory.

The 4 GB limit is actually on file size, while the partition limit is something like 2 TB?
MX18b1: Lenovo T430: Intel Ivy Bridge i5-3320M, 8GB RAM, 4.19.0-1-amd64, 119 GB SSD
MX18b1: Eee&AA1 NBs: Dual Core Atom N270, 1GB RAM, 4.19.0-1-686, 150 GB HDD
DoubleCmd/Thunar, LibO613, Dropbox, Vivaldi/Firefox, CherryTree, Vbox. LinuxCounter #208633

User avatar
Adrian
Forum Veteran
Forum Veteran
Posts: 9177
Joined: Wed Jul 12, 2006 1:42 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#9 Post by Adrian » Fri Sep 21, 2018 8:37 pm

I tested on my system with the latest mx-snapshot, I was able to create a ISO on a NTFS flashdrive, so whatever problem you are having might be specific to your system. Monitor your free space with "df", see if you are running out of space, also it might help if you run mx-snapshot from the terminal "sudo -E mx-snapshot" and see what's the last output in the terminal maybe that would give us a clue of what's going wrong.

The only change I did to mx-snapshot that could potentially changed how things work is that I check which has more free space /tmp or /home (relevant if home is a separate partition) and then write the build environment in the larger partition -- this should actually improve things, but if there's an error in my code or something else going on it could be the cause of the problem you see -- so one thing to look for is while you are creating the snapshot if the mx-snapshot-XXXXXXX (the Xs are random letters) is created in /tmp or /home (the terminal output should also give you a clue) and then run "df" to see if you are running out of space on that particular partition. Otherwise I'm pretty much out of ideas...

mimimx
Forum Novice
Forum  Novice
Posts: 13
Joined: Wed Jun 07, 2017 8:49 am

Re: mx-snapshot 8.9 FAT32 et NTFS

#10 Post by mimimx » Sat Sep 22, 2018 4:18 am

That's what I have by launching mx-snaphot with sudo cde ...

Code: Select all

----------------------
root@mx:/home/demo# sudo -E mx-snapshot
Qt: Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed
"dpkg-query -f '${Version}' -W mx-snapshot"
"18.9"
exit code: 0
"mountpoint -q /live/aufs"
exit code: 0
"uname -m"
"x86_64
"
exit code: 0
"cat /etc/debian_version | cut -f1 -d'.'"
"9
"
exit code: 0
+++ Enter Function: void MainWindow::setup() +++
+++ Enter Function: void MainWindow::loadSettings() +++
+++ Enter Function: QString MainWindow::getFilename() +++
"date +%Y%m%d_%H%M"
"20180922_1006
"
exit code: 0
+++ Enter Function: void MainWindow::listFreeSpace() +++
"df -h "/home" | awk 'NR==2 {print $4}'"
"854M
"
exit code: 0
+++ Enter Function: QString MainWindow::getSnapshotSize() +++
+++ Enter Function: int MainWindow::getSnapshotCount() +++
"du --exclude-from="/usr/local/share/excludes/mx-snapshot-exclude.list" -sch / 2>/dev/null | tail -n1 | cut -f1"
"8,1G
"
exit code: 0
"mountpoint -q /home"
exit code: 0
"df -h /home | awk 'NR==2 {print $3}'"
"980M
"
exit code: 0
Gtk-Message: 10:08:38.951: GtkDialog mapped without a transient parent. This is discouraged.
+++ Enter Function: void MainWindow::listFreeSpace() +++
"df -h "/media/demo/Data" | awk 'NR==2 {print $4}'"
"156G
"
exit code: 0
+++ Enter Function: QString MainWindow::getSnapshotSize() +++
"find "/media/demo/Data/snapshot/snapshot" -maxdepth 1 -type f -name '*.iso' -exec du -shc {} + | tail -1 | awk '{print $1}'"
exit code: 0
+++ Enter Function: int MainWindow::getSnapshotCount() +++
"uname -r"
"4.15.0-1-amd64
"
exit code: 0
+++ Enter Function: void MainWindow::checkDirectories() +++
+++ Enter Function: bool MainWindow::isOnLinuxPart(QDir) +++
"stat --file-system --format=%T /media/demo/Data/snapshot/snapshot"
"fuseblk
"
exit code: 0
detected partition "fuseblk" supported linux part: false
+++ Enter Function: QString MainWindow::largerFreeSpace(QString, QString) +++
"df -k --output=avail /tmp 2>/dev/null | tail -n1"
"2891720
"
exit code: 0
"df -k --output=avail /home 2>/dev/null | tail -n1"
"874440
"
exit code: 0
"mktemp -d "/tmp/mx-snapshot-XXXXXXXX""
"/tmp/mx-snapshot-5dbQgFb9
"
exit code: 0
/home/demo
+++ Enter Function: void MainWindow::copyNewIso() +++
"tar xf /usr/lib/iso-template/iso-template.tar.gz"
exit code: 0
"cp /usr/lib/iso-template/template-initrd.gz iso-template/antiX/initrd.gz"
exit code: 0
"cp /boot/vmlinuz-4.15.0-1-amd64 iso-template/antiX/vmlinuz"
exit code: 0
+++ Enter Function: void MainWindow::replaceMenuStrings() +++
"date +'%d %B %Y'"
"22 septembre 2018
"
exit code: 0
"cat /etc/antix-version | cut -f1 -d'_'"
"MX-17.1
"
exit code: 0
"lsb_release -is"
"MX
"
exit code: 0
"cat /etc/antix-version | cut -f-2 -d' '"
"MX-17.1_x64 Horizon
"
exit code: 0
"lsb_release -cs"
"Horizon
"
exit code: 0
"sed -i 's/%DISTRO_NAME%/MX/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/grub.cfg""
exit code: 0
"sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/syslinux.cfg""
exit code: 0
"sed -i 's/%OPTIONS%/quiet/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/isolinux.cfg""
exit code: 0
"sed -i 's/%FULL_DISTRO_NAME%/MX-17.1_x64 Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/grub.cfg""
exit code: 0
"sed -i 's/%FULL_DISTRO_NAME%/MX-17.1_x64 Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/syslinux.cfg""
exit code: 0
"sed -i 's/%FULL_DISTRO_NAME%/MX-17.1_x64 Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/readme.msg""
exit code: 0
"sed -i 's/%FULL_DISTRO_NAME%/MX-17.1_x64 Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/isolinux.cfg""
exit code: 0
"sed -i 's/%FULL_DISTRO_NAME%/MX-17.1_x64 Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/readme.msg""
exit code: 0
"sed -i 's/%DISTRO%/MX-17.1/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/theme/theme.txt""
exit code: 0
"sed -i 's/%DISTRO%/MX-17.1/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/grub.cfg""
exit code: 0
"sed -i 's/%RELEASE_DATE%/22 septembre 2018/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/grub.cfg""
exit code: 0
"sed -i 's/%RELEASE_DATE%/22 septembre 2018/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/syslinux.cfg""
exit code: 0
"sed -i 's/%RELEASE_DATE%/22 septembre 2018/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/readme.msg""
exit code: 0
"sed -i 's/%RELEASE_DATE%/22 septembre 2018/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/isolinux.cfg""
exit code: 0
"sed -i 's/%RELEASE_DATE%/22 septembre 2018/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/readme.msg""
exit code: 0
"sed -i 's/%CODE_NAME%/Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/syslinux/syslinux.cfg""
exit code: 0
"sed -i 's/%CODE_NAME%/Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/isolinux/isolinux.cfg""
exit code: 0
"sed -i 's/%ASCII_CODE_NAME%/Horizon/g' "/tmp/mx-snapshot-5dbQgFb9/iso-template/boot/grub/theme/theme.txt""
exit code: 0
+++ Enter Function: void MainWindow::makeMd5sum(QString, QString) +++
"md5sum "vmlinuz">"/tmp/mx-snapshot-5dbQgFb9/iso-template/antiX/vmlinuz.md5""
exit code: 0
"mktemp -d"
"/tmp/tmp.AtYKXxgmHy
"
exit code: 0
+++ Enter Function: void MainWindow::openInitrd(QString, QString) +++
"chmod a+rx "/tmp/tmp.AtYKXxgmHy""
exit code: 0
"gunzip -c "/tmp/mx-snapshot-5dbQgFb9/iso-template/antiX/initrd.gz" | cpio -idum"
"6150 blocs
"
exit code: 0
"test -d "/tmp/tmp.AtYKXxgmHy/lib/modules" && rm -r "/tmp/tmp.AtYKXxgmHy/lib/modules""
exit code: 1
"test -r /usr/local/share/live-files/files/etc/initrd-release && cp /usr/local/share/live-files/files/etc/initrd-release "/tmp/tmp.AtYKXxgmHy/etc""
exit code: 1
"test -r /etc/initrd-release && cp /etc/initrd-release "/tmp/tmp.AtYKXxgmHy/etc""
exit code: 0
"/usr/share/mx-packageinstaller/scripts/copy-initrd-modules -t="/tmp/tmp.AtYKXxgmHy" -k="4.15.0-1-amd64""
"modprobe: WARNING: Module aufs not found in directory /lib/modules/4.15.0-1-amd64
modprobe: WARNING: Module block not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module fotg210-hcd not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module fusbh200-hcd not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module hid-lenovo-tpkbd not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module jbd not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module pcie-aspm not found in directory /lib/modules/4.15.0-1-amd64
"
"modprobe: WARNING: Module printk not found in directory /lib/modules/4.15.0-1-amd64
modprobe: WARNING: Module rts5139 not found in directory /lib/modules/4.15.0-1-amd64
"
exit code: 0
"/usr/share/mx-packageinstaller/scripts/copy-initrd-programs --to="/tmp/tmp.AtYKXxgmHy""
"  add program: ntfs-3g
"
"ld_linux: /lib64/ld-linux-x86-64.so.2
"
"ld_dir: /tmp/tmp.AtYKXxgmHy/lib/x86_64-linux-gnu
"
"  add program: eject
"
"ld_linux: /lib64/ld-linux-x86-64.so.2
"
"ld_dir: /tmp/tmp.AtYKXxgmHy/lib/x86_64-linux-gnu
"
exit code: 0
+++ Enter Function: void MainWindow::closeInitrd(QString, QString) +++
"(find . | cpio -o -H newc --owner root:root | gzip -9) >"/tmp/mx-snapshot-5dbQgFb9/iso-template/antiX/initrd.gz""
"46029 blocs
"
exit code: 0
"rm -r /tmp/tmp.AtYKXxgmHy"
exit code: 0
+++ Enter Function: void MainWindow::makeMd5sum(QString, QString) +++
"md5sum "initrd.gz">"/tmp/mx-snapshot-5dbQgFb9/iso-template/antiX/initrd.gz.md5""
exit code: 0
+++ Enter Function: void MainWindow::mkDir(QString) +++
+++ Enter Function: void MainWindow::savePackageList(QString) +++
"dpkg -l | grep ^ii\ \ | awk '{print $2,$3}' | sed 's/:'$(dpkg --print-architecture)'//' | column -t >"/tmp/mx-snapshot-5dbQgFb9/iso-template/snapshot-20180922_1006/package_list""
exit code: 0
+++ Enter Function: void MainWindow::setupEnv() +++
+++ Enter Function: bool MainWindow::checkInstalled(QString) +++
"dpkg -s mx-installer | grep Status"
"Status: install ok installed
"
exit code: 0
"echo /home/*/Desktop | xargs -n1 cp /usr/share/applications/minstall.desktop 2>/dev/null"
exit code: 0
"chmod +x /home/*/Desktop/minstall.desktop"
exit code: 0
"installed-to-live -b /.bind-root start bind=/home live-files version-file adjtime read-only"
exit code: 0
+++ Enter Function: bool MainWindow::createIso(QString) +++
+++ Enter Function: void MainWindow::addRemoveExclusion(bool, QString) +++
+++ Enter Function: void MainWindow::addRemoveExclusion(bool, QString) +++
"mksquashfs /.bind-root iso-template/antiX/linuxfs -comp xz -wildcards -ef /usr/local/share/excludes/mx-snapshot-exclude.list -e 'media/demo/Data/snapshot/snapshot' 'tmp/mx-snapshot-5dbQgFb9'"
"Parallel mksquashfs: Using 4 processors
Creating 4.0 filesystem on iso-template/antiX/linuxfs, block size 131072.
[|                                                         ]    500/328973   0%"
[==\                                                       ]  13300/328973   4%"
[===|                                                      ]  17400/328973   5%"
[===|                                                      ]  21600/328973   6%"
[====-                                                     ]  23500/328973   7%"
[====\                                                     ]  24000/328973   7%"
[====-                                                     ]  24500/328973   7%"
[====|                                                     ]  25600/328973   7%"
[====\                                                     ]  25800/328973   7%"
[====|                                                     ]  26100/328973   7%"
terminating parent process: 7355
exit code: 1
+++ Enter Function: void MainWindow::cleanUp() +++
---------------------------------------------------------------------------------
root@mx:/home/demo#
---
* Mod-note: Wrapped the long text output into [code][/code] tags for better readability -- fehlix

Post Reply

Return to “MX Help”