MX-23 alpha2 feedback thread

Message
Author
User avatar
dolphin_oracle
Developer
Posts: 22111
Joined: Sun Dec 16, 2007 12:17 pm

Re: MX-23 alpha2 feedback thread

#251 Post by dolphin_oracle »

How large is your perstence file?
http://www.youtube.com/runwiththedolphin
lenovo ThinkPad X1 Extreme Gen 4 - MX-23
FYI: mx "test" repo is not the same thing as debian testing repo.

User avatar
user-green
Posts: 326
Joined: Sat Mar 14, 2020 1:40 am

Re: MX-23 alpha2 feedback thread

#252 Post by user-green »

operadude wrote:
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash persist_static from=usb
I think you should choose p_static_root or persist_all, instead of persist static.

Best regards

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#253 Post by operadude »

dolphin_oracle wrote: Sun Apr 30, 2023 5:14 pm How large is your perstence file?
Here are the stats I found on the Micro SD in: /media/opera-dude/MX23_ALPHA2/antiX/:

homefs = 1.7 GB

linuxfs = 1.9 GB

rootfs = 6.0 GB

Available Space = 9.9 GB

I am assuming, based on videos and the antiX info on persistence, that the "persistence file" is "rootfs". Please let me know if I have that wrong.

Also, on my Micro SD, there is no "/boot-dev/antiX-12/rootfs"; rather, on my card, rootfs resides on the "/antiX" directory of the drive (which is mounted on: "/media/opera-dude/MX23_ALPHA2"). On my card, there is no "/boot-dev" directory. Don't know if that's a problem.

Maybe I didn't set-up the persistence properly? To counter that, I have been able to make a number of changes, such as configuring Firefox, placing icons on the panel, changing sounds, changing time and location, etc. All of those changes DO persist at reboot (when I make the same selections for persistence (static) and boot options (from=usb).

So, don't know why I cant install upgrades & packages !?! :confused:

:bawling:

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#254 Post by operadude »

user-green wrote: Sun Apr 30, 2023 6:37 pm
operadude wrote:
parameters: BOOT_IMAGE=/antiX/vmlinuz quiet splasht nosplash persist_static from=usb
I think you should choose p_static_root or persist_all, instead of persist static.

Best regards
OK, will try that, and report back...

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#255 Post by operadude »

Note: Verified not only the md5 of the .iso download, but also verified the .sig (as I always do).

OK, tried with same persistence as before, but this time used the "check persistence file" option on the opening menu (GRUB menu?). ===> NO difference!

Then, tried using "persist_all": =======> No difference!

Here's the error message I got after attempting an update (also installed printer driver):

Code: Select all

full upgrade
apt full-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
   featherpad-l10n (1.4.0-0.1~mx23+1)
   qttranslations5-l10n (5.15.8-2)
The following packages will be upgraded:
   advert-block-antix (0.3.1 => 0.3.1+2)
   avahi-daemon (0.8-9 => 0.8-10)
   bootlogd (3.06-2 => 3.06-4)
   busybox (1:1.35.0-4+b2 => 1:1.35.0-4+b3)
   checkaptgpg (23.01.01 => 23.04.02)
   cleanup-notifier-mx (22.05.02mx => 23.04)
   console-setup (1.218 => 1.219)
   console-setup-linux (1.218 => 1.219)
   cryptsetup (2:2.6.1-3~deb12u1 => 2:2.6.1-4~deb12u1)
   cryptsetup-bin (2:2.6.1-3~deb12u1 => 2:2.6.1-4~deb12u1)
   cryptsetup-initramfs (2:2.6.1-3~deb12u1 => 2:2.6.1-4~deb12u1)
   cups (2.4.2-2 => 2.4.2-3)
   cups-bsd (2.4.2-2 => 2.4.2-3)
   cups-client (2.4.2-2 => 2.4.2-3)
   cups-common (2.4.2-2 => 2.4.2-3)
   cups-core-drivers (2.4.2-2 => 2.4.2-3)
   cups-daemon (2.4.2-2 => 2.4.2-3)
   cups-ipp-utils (2.4.2-2 => 2.4.2-3)
   cups-ppdc (2.4.2-2 => 2.4.2-3)
   cups-server-common (2.4.2-2 => 2.4.2-3)
   curl (7.88.1-7 => 7.88.1-9)
   deb-installer (23.1.01 => 23.4)
   debian-archive-keyring (2023.2 => 2023.3)
   desktop-defaults-mx-common (23.03.03mx23 => 23.04.02mx23)
   desktop-defaults-mx-xfce (23.03.02mx23 => 23.04.03mx23)
   desktop-defaults-mx-xfce-desktop (23.03.02mx23 => 23.04.03mx23)
   desktop-defaults-mx-xfce-system (23.03.02mx23 => 23.04.03mx23)
   disk-manager (23.01.01 => 23.04.04)
   dkms (3.0.10-6 => 3.0.10-8)
   e2fsprogs (1.46.6-1 => 1.47.0-2)
   fakeroot (1.31-1.1 => 1.31-1.2)
   featherpad (1.3.5-1 => 1.4.0-0.1~mx23+1)
   firefox (111.0.1~mozillabinaries-1mx23+2 => 112.0.2~mozillabinaries-1mx23+1)
   grub-common (2.06-8 => 2.06-12)
   grub-efi-amd64-bin (2.06-8 => 2.06-12)
   grub-efi-ia32-bin (2.06-8 => 2.06-12)
   grub-pc (2.06-8 => 2.06-12)
   grub-pc-bin (2.06-8 => 2.06-12)
   grub2-common (2.06-8 => 2.06-12)
   initscripts (3.06-2 => 3.06-4)
   installation-report (2.87 => 2.88)
   inxi (3.3.25-1-1 => 3.3.26-1-1)
   keyboard-configuration (1.218 => 1.219)
   libargon2-1 (0~20171227-0.3 => 0~20171227-0.3+deb12u1)
   libavahi-client3 (0.8-9 => 0.8-10)
   libavahi-common-data (0.8-9 => 0.8-10)
   libavahi-common3 (0.8-9 => 0.8-10)
   libavahi-core7 (0.8-9 => 0.8-10)
   libavahi-glib1 (0.8-9 => 0.8-10)
   libc-l10n (2.36-8 => 2.36-9)
   libcom-err2 (1.46.6-1 => 1.47.0-2)
   libcryptsetup12 (2:2.6.1-3~deb12u1 => 2:2.6.1-4~deb12u1)
   libcups2 (2.4.2-2 => 2.4.2-3)
   libcurl3-gnutls (7.88.1-7 => 7.88.1-9)
   libcurl4 (7.88.1-7 => 7.88.1-9)
   libdebconfclient0 (0.268 => 0.269)
   libext2fs2 (1.46.6-1 => 1.47.0-2)
   libfakeroot (1.31-1.1 => 1.31-1.2)
   libfluidsynth3 (2.3.1-1 => 2.3.1-2)
   libglib2.0-0 (2.74.6-1 => 2.74.6-2)
   libglib2.0-bin (2.74.6-1 => 2.74.6-2)
   libglib2.0-data (2.74.6-1 => 2.74.6-2)
   libgnutls30 (3.7.9-1 => 3.7.9-2)
   liblrdf0 (0.6.1-3 => 0.6.1-4)
   libmbedcrypto7 (2.28.2-1 => 2.28.3-1)
   libmozjs-102-0 (102.9.0-1 => 102.10.0-1)
   libopenexr-3-1-30 (3.1.5-4 => 3.1.5-5)
   libpaper-utils (1.1.28+b1 => 1.1.29)
   libpaper1 (1.1.28+b1 => 1.1.29)
   libpcsclite1 (1.9.9-1 => 1.9.9-2)
   libprotobuf-lite32 (3.21.12-1+b2 => 3.21.12-3)
   libprotobuf32 (3.21.12-1+b2 => 3.21.12-3)
   libpython3-stdlib (3.11.2-1 => 3.11.2-1+b1)
   libss2 (1.46.6-1 => 1.47.0-2)
   libx264-164 (2:0.164.3095+gitbaee400-2+b1 => 2:0.164.3095+gitbaee400-3)
   libxml2 (2.9.14+dfsg-1.1+b3 => 2.9.14+dfsg-1.2)
   libxt6 (1:1.2.1-1 => 1:1.2.1-1.1)
   libzstd1 (1.5.4+dfsg2-3 => 1.5.4+dfsg2-5)
   linux-compiler-gcc-12-x86 (6.1.20-1 => 6.1.20-2)
   linux-headers-6.1.0-7-amd64 (6.1.20-1 => 6.1.20-2)
   linux-headers-6.1.0-7-common (6.1.20-1 => 6.1.20-2)
   linux-headers-amd64 (6.1.20-1 => 6.1.20-2)
   linux-image-6.1.0-7-amd64 (6.1.20-1 => 6.1.20-2)
   linux-image-amd64 (6.1.20-1 => 6.1.20-2)
   linux-kbuild-6.1 (6.1.20-1 => 6.1.20-2)
   lo-main-helper (23.07.05mx23 => 23.07.06mx23)
   locales (2.36-8 => 2.36-9)
   logsave (1.46.6-1 => 1.47.0-2)
   mx-boot-options (23.2.01 => 23.4)
   mx-bootrepair (23.3.01 => 23.4)
   mx-conky (22.12.02 => 23.4)
   mx-datetime (23.4 => 23.4.01)
   mx-goodies (23.01.04mx21 => 23.04.01)
   mx-idevice-mounter (0.1.5.13 => 0.1.5.14)
   mx-installer (23.3mx23 => 23.4mx23)
   mx-iso-template (23.03.02mx23 => 23.04.01mx23)
   mx-live-usb-maker (23.2.04 => 23.4)
   mx-packageinstaller (23.3.02 => 23.4)
   mx-packageinstaller-pkglist (23.07.05mx23 => 23.07.06mx23)
   mx-snapshot (23.3.03 => 23.4.01)
   mx-system-sounds (22.11.02 => 23.04.01mx23)
   mx-tweak (23.04.01 => 23.04.08mx23)
   mx-user (23.2 => 23.4.01)
   nvidia-detect (525.89.02-1 => 525.105.17-1)
   openvpn (2.6.0-1 => 2.6.1-1)
   pci.ids (0.0~2023.02.23-1 => 0.0~2023.03.17-1)
   python3 (3.11.2-1 => 3.11.2-1+b1)
   python3-dateutil (2.8.2-1 => 2.8.2-2)
   python3-minimal (3.11.2-1 => 3.11.2-1+b1)
   system-keyboard-qt (22.10.01mx21 => 23.04.04mx23)
   sysv-rc (3.06-2 => 3.06-4)
   sysvinit-core (3.06-2 => 3.06-4)
   sysvinit-utils (3.06-2 => 3.06-4)
   thunar-custom-actions-mx (22.06.02mx21 => 23.04.01mx23)
   thunderbird (1:102.9.0-1+b1 => 1:102.10.0-1)
   tlp (1.5.0-1 => 1.5.0-2)
   tzdata (2023c-2 => 2023c-3)
   vim-common (2:9.0.1000-4 => 2:9.0.1378-1)
   vim-tiny (2:9.0.1000-4 => 2:9.0.1378-1)
   zstd (1.5.4+dfsg2-3 => 1.5.4+dfsg2-5)
120 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
Need to get 0 B/265 MB of archives.
After this operation, 37.7 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Extracting templates from packages: 24%E: Invalid archive signature
E: Internal error, could not locate member control.tar{.zst,.lz4,.gz,.xz,.bz2,.lzma,}
E: Prior errors apply to /var/cache/apt/archives/vim-common_2%3a9.0.1378-1_all.deb
E: Prior errors apply to /var/cache/apt/archives/libc-l10n_2.36-9_all.deb
E: Prior errors apply to /var/cache/apt/archives/locales_2.36-9_all.deb
E: Prior errors apply to /var/cache/apt/archives/advert-block-antix_0.3.1+2_all.deb
E: Prior errors apply to /var/cache/apt/archives/bootlogd_3.06-4_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/busybox_1%3a1.35.0-4+b3_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/firefox_112.0.2~mozillabinaries-1mx23+1_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/checkaptgpg_23.04.02_all.deb
E: Prior errors apply to /var/cache/apt/archives/cleanup-notifier-mx_23.04_all.deb
E: Prior errors apply to /var/cache/apt/archives/cryptsetup-initramfs_2%3a2.6.1-4~deb12u1_all.deb
E: Prior errors apply to /var/cache/apt/archives/libargon2-1_0~20171227-0.3+deb12u1_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/libcryptsetup12_2%3a2.6.1-4~deb12u1_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/cryptsetup-bin_2%3a2.6.1-4~deb12u1_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/cryptsetup_2%3a2.6.1-4~deb12u1_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/curl_7.88.1-9_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/libcurl4_7.88.1-9_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/deb-installer_23.4_amd64.deb
E: Prior errors apply to /var/cache/apt/archives/desktop-defaults-mx-common_23.04.02mx23_all.deb
E: Prior errors apply to /var/cache/apt/archives/thunar-custom-actions-mx_23.04.01mx23_all.deb
E: Prior errors apply to /var/cache/apt/archives/desktop-defaults-mx-xfce-desktop_23.04.03mx23_all.deb
E: Prior errors apply to /var/cache/apt/archives/desktop-defaults-mx-xfce-system_23.04.03mx23_all.deb
debconf: apt-extracttemplates failed: Resource temporarily unavailable
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up libc-bin (2.36-9) ...
Bus error
ldconfig: Can't stat /usr/local/lib/i386-linux-gnu: No such file or directory
ldconfig: Path `/usr/lib/i386-linux-gnu' given more than once
(from /etc/ld.so.conf.d/i386-linux-gnu.conf:4 and /etc/ld.so.conf.d/i386-linux-gnu.conf:3)
ldconfig: Can't stat /usr/local/lib/i686-linux-gnu: No such file or directory
ldconfig: Can't stat /lib/i686-linux-gnu: No such file or directory
ldconfig: Can't stat /usr/lib/i686-linux-gnu: No such file or directory
ldconfig: Can't stat /usr/local/lib/x86_64-linux-gnu: No such file or directory
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
(from /etc/ld.so.conf.d/x86_64-linux-gnu.conf:4 and /etc/ld.so.conf.d/x86_64-linux-gnu.conf:3)
ldconfig: Path `/lib/x86_64-linux-gnu' given more than once
(from <builtin>:0 and /etc/ld.so.conf.d/x86_64-linux-gnu.conf:3)
ldconfig: Path `/usr/lib/x86_64-linux-gnu' given more than once
(from <builtin>:0 and /etc/ld.so.conf.d/x86_64-linux-gnu.conf:3)
ldconfig: Path `/usr/lib' given more than once
(from <builtin>:0 and <builtin>:0)
/usr/lib/x86_64-linux-gnu/libfakeroot: (from /etc/ld.so.conf.d/fakeroot-x86_64-linux-gnu.conf:1)
	libfakeroot-0.so -> libfakeroot-tcp.so
/lib/i386-linux-gnu: (from /etc/ld.so.conf.d/i386-linux-gnu.conf:3)
	libutil.so.1 -> libutil.so.1
	libthread_db.so.1 -> libthread_db.so.1
	librt.so.1 -> librt.so.1
	libresolv.so.2 -> libresolv.so.2
	libpthread.so.0 -> libpthread.so.0
	libpcprofile.so -> libpcprofile.so
	libnss_hesiod.so.2 -> libnss_hesiod.so.2
	libnss_files.so.2 -> libnss_files.so.2
	libnss_dns.so.2 -> libnss_dns.so.2
	libnss_compat.so.2 -> libnss_compat.so.2
	libnsl.so.1 -> libnsl.so.1
	libmemusage.so -> libmemusage.so
	libm.so.6 -> libm.so.6
	libgcc_s.so.1 -> libgcc_s.so.1
	libdl.so.2 -> libdl.so.2
	libc_malloc_debug.so.0 -> libc_malloc_debug.so.0
	libc.so.6 -> libc.so.6
	libanl.so.1 -> libanl.so.1
	libBrokenLocale.so.1 -> libBrokenLocale.so.1
ldconfig: /lib/i386-linux-gnu/ld-linux.so.2 is the dynamic linker, ignoring

	ld-linux.so.2 -> ld-linux.so.2
/usr/local/lib: (from /etc/ld.so.conf.d/libc.conf:2)
/lib/x86_64-linux-gnu: (from /etc/ld.so.conf.d/x86_64-linux-gnu.conf:3)
Bus error
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 135
Errors were encountered while processing:
 libc-bin
E: Sub-process /usr/bin/dpkg returned an error code (1)

full upgrade complete (or was canceled)

this terminal window can now be closed

Press any key to close...
So, not having an easy time...

Seems that the main issue is:

Code: Select all

Bus error
dpkg: error processing package libc-bin (--configure):
 installed libc-bin package post-installation script subprocess returned error exit status 135
I really would like to test-out MX-23: Help me Obi-Wan :exclamation:

:crossfingers:

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#256 Post by operadude »

Decided to also check the md5's not only of the .iso download, but also of the files:
"initrd", "linuxfs", "vmlinuz" on the live USB media (which I had created using MX-LUM), which reside at: /live/boot-dev/antiX/ (on live USB).

"initrd" and "vmlinuz" md5's passed, but "linuxfs" FAILED!

So, perhaps there's an issue with my media. I have @fehlix to thank for this idea, as that was a problem for me in the past!

So, will try a different medium, re-test, and report back!

:crossfingers:

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#257 Post by operadude »

Quickly: looks like the issue was with the USB (Micro SD Card).
Tried again, and updates went through!
However, there was a write failure at the very end because no room left on the 4 GB USB.
Will try again with at least 8 GB, and preferably 16, or even 32 GB!
Will report back, hopefully soon!

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

Re: MX-23 alpha2 feedback thread

#258 Post by fehlix »

operadude wrote: Mon May 01, 2023 5:59 am Decided to also check the md5's not only of the .iso download, but also of the files:
"initrd", "linuxfs", "vmlinuz" on the live USB media (which I had created using MX-LUM), which reside at: /live/boot-dev/antiX/ (on live USB).

"initrd" and "vmlinuz" md5's passed, but "linuxfs" FAILED!
On the LiveBoot menu we have now a new menu entry "Check Intergrity of Live Media":
check_integrety_of_live_media.jpg
which would do the check at bootup.
The success or failuer is shown on screen
and if booted the log is also at /var/log/live/initrd.log.color.
Shown here on terminal with:

Code: Select all

less -R /var/log/live/initrd.log.color
log_check_integrety_of_live_media.jpg
You do not have the required permissions to view the files attached to this post.

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#259 Post by operadude »

Thank You @fehlix :exclamation:
fehlix wrote: Mon May 01, 2023 7:30 am
operadude wrote: Mon May 01, 2023 5:59 am Decided to also check the md5's not only of the .iso download, but also of the files:
"initrd", "linuxfs", "vmlinuz" on the live USB media (which I had created using MX-LUM), which reside at: /live/boot-dev/antiX/ (on live USB).

"initrd" and "vmlinuz" md5's passed, but "linuxfs" FAILED!
On the LiveBoot menu we have now a new menu entry "Check Intergrity of Live Media":
check_integrety_of_live_media.jpg
which would do the check at bootup.
The success or failuer is shown on screen
and if booted the log is also at /var/log/live/initrd.log.color.
Shown here on terminal with:

Code: Select all

less -R /var/log/live/initrd.log.color
log_check_integrety_of_live_media.jpg
I had checked my initial attempt with the 16GB SD Card, using that cool new feature "Check Integrity of Live Media" on the GRUB menu. I don't remember seeing an error; however, the media was probably faulty, since the md5 for "linuxfs" on that card failed!

OK, just finished successfully creating a 32 GB Micro SD Card with MX-LUM, and before testing, I have checked the md5's for "initrd", "linuxfs", and "vmlinuz" on the media (before booting). All md5's passed "OK"!!!

Note: I have had to run MX-Format-USB -- TWICE -- for these el-cheapo generic SD Cards. Maybe that's the problem I'm having. Created the 32GB Card with MX-LUM, which reported all md5's "OK". However, checking the md5's on the card itself (after MX-LUM finished "Successfully"), got that md5 error again for "linuxfs". Ran MX-Format-USB again on that Card; ran MX-LUM again (with "Success" message); then, checked all md5's on the card -- second time, they all passed (including "linuxfs").

I will now shutdown, and re-test with the new 32GB Card, and try your cool trick with:

Code: Select all

less -R /var/log/live/initrd.log.color
Will report back soon!

User avatar
operadude
Posts: 858
Joined: Tue Nov 05, 2019 12:08 am

Re: MX-23 alpha2 feedback thread

#260 Post by operadude »

So far so good, but not out of the woods yet!

1. Reminder: My "alpha2" .iso has good md5 and .sig checks.
2. Created a new Live MX 16 GB USB (Not an SD Card) with MX-LUM "Successfully":

Code: Select all

=====================================================================
/usr/local/bin/live-usb-maker gui -N --label=MX23_ALPHA2 -C off --from=/media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23 Alpha/MX-23_alpha2_x64.iso -t /dev/sdl
        program: live-usb-maker
        started: Mon 01 May 2023 04:47:17 PM IDT
        version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
         kernel: 5.10.0-22-amd64
             OS: MX 21.3 (Wildflower)
      found lib: /usr/local/lib/cli-shell-utils/cli-shell-utils.bash
    lib version: 2.41.05-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
---------------------------------------------------------------------

Found man page: live-usb-maker.1
Will use target device /dev/sdl (14.6G VendorCo ProductCode)
Will use source file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23 Alpha/MX-23_alpha2_x64.iso
Distro: MX-23_alpha2_x64 Libretto April 7, 2023
Found grub config 2.0
Estimated extfs overhead for 14949M is 36M

                    Total      Used     Extra
   entire drive  14.6 GiB 14.6 GiB     1 MiB
 main partition  14.6 GiB 2.01 GiB  12.6 GiB
 uefi partition    50 MiB   32 MiB    18 MiB

Ready to make live-usb on device sdl
... by copying file /media/opera-dude/Seagate Expansion Drive/Documents/Computer/OS/Linux Distros/MX Linux/MX-23 Alpha/MX-23_alpha2_x64.iso

>> partition-clear
Total bytes: 15728640000
Total blocks: 30720000
 > dd status=none if=/dev/zero of=/dev/sdl bs=512 count=34
 > dd status=none if=/dev/zero of=/dev/sdl bs=512 count=34 seek=64
 > dd status=none conv=notrunc if=/dev/zero of=/dev/sdl bs=512 count=34 seek=30719966
 > partprobe /dev/sdl

>> partition-make
Using msdos partitioning
 > parted --script --align optimal /dev/sdl unit MiB mklabel msdos
 > dd status=none if=/dev/zero of=/dev/sdl seek=1024 bs=1K count=128
 > parted --script --align optimal /dev/sdl unit MiB mkpart primary 1 14949
 > parted --script --align optimal /dev/sdl unit MiB set 1 boot on
 > dd status=none if=/dev/zero of=/dev/sdl seek=15307776 bs=1K count=128
 > parted --script --align optimal /dev/sdl unit MiB mkpart primary 14949 14998
 > parted --script --align optimal /dev/sdl unit MiB set 2 esp on
 > partprobe /dev/sdl
 > wait_for_file /dev/sdl1

>> makefs-bios
 > mkfs.ext4 -O ^64bit -m0 -i16384 -J size=32 /dev/sdl1
mke2fs 1.46.2 (28-Feb-2021)
64-bit filesystem support is not enabled.  The larger fields afforded by this feature enable full-strength checksumming.  Pass -O 64bit to rectify.
Creating filesystem with 3826688 4k blocks and 958464 inodes
Filesystem UUID: 823de401-1b8a-4d28-820f-6e71e5b97d95
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208

Allocating group tables:   0/117       done                            
Writing inode tables:   0/117       done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information:   0/117       done

 > tune2fs -L MX23_ALPHA2 /dev/sdl1
tune2fs 1.46.2 (28-Feb-2021)
 > wait_for_file /dev/sdl2

>> makefs-uefi
 > mkfs.vfat -F 32 -n MX-UEFI /dev/sdl2
mkfs.fat 4.2 (2021-01-31)
 > partprobe /dev/sdl
 > wait_for_file /dev/sdl1
 > mkdir -p /run/live-usb-maker/main
 > mount -t ext4 /dev/sdl1 /run/live-usb-maker/main
 > wait_for_file /dev/sdl2
 > mkdir -p /run/live-usb-maker/uefi
 > mount -t vfat /dev/sdl2 /run/live-usb-maker/uefi

Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sdl1      ext4   15G   24K   15G   1% /run/live-usb-maker/main
/dev/sdl2      vfat   49M   512   49M   1% /run/live-usb-maker/uefi


>> copy-uefi
copy from iso to uefi partition
files [Ee][Ff][Ii] version
 > cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/EFI /run/live-usb-maker/uefi/.
 > cp --no-dereference --preserve=mode,links --recursive /run/live-usb-maker/iso/version /run/live-usb-maker/uefi/.
Fix Dell uefi memtest bug
 > cp /run/live-usb-maker/uefi/EFI/BOOT/grubx64.efi /run/live-usb-maker/uefi/EFI/BOOT/fallback.efi

>> copy-main
 > rm -rf /run/live-usb-maker/main/boot.orig
copy from iso to main partition
vm.dirty_bytes = 20000000
copy /antiX/vmlinuz
 > cpio -pdm --quiet /run/live-usb-maker/main/
 > e4defrag -v ./antiX/vmlinuz
e4defrag 1.46.2 (28-Feb-2021)
ext4 defragmentation for ./antiX/vmlinuz
[1/1][1/1]./antiX/vmlinuz:	100%  extents: 1 -> 1	[ OK ]
 Success:			[1/1]
copy /antiX/initrd.gz
 > cpio -pdm --quiet /run/live-usb-maker/main/
 > e4defrag -v ./antiX/initrd.gz
e4defrag 1.46.2 (28-Feb-2021)
ext4 defragmentation for ./antiX/initrd.gz
[1/1][1/1]./antiX/initrd.gz:	100%  extents: 1 -> 1	[ OK ]
 Success:			[1/1]
copy remaining files ...
 > cpio -pdm --quiet /run/live-usb-maker/main/
copy pids: 12756 12759
vm.dirty_bytes = 20000000
vm.dirty_ratio = 0
 > write_file /run/live-usb-maker/main/made-by-live-usb-maker   created: Mon 01 May 2023 04:53:16 PM IDT
  program: live-usb-maker
  version: 2.41.19-2302 (Sat, 25 Feb 2023 12:45:10 -0500)
 > dd status=none if=/dev/urandom of=/run/live-usb-maker/main/antiX/random-seed bs=512 count=1
 > chmod 600 /run/live-usb-maker/main/antiX/random-seed
 > rm -rf /run/live-usb-maker/main/.disk

>> check-usb-md5
check md5 for initrd.gz
 > md5sum -c initrd.gz.md5
initrd.gz: OK
check md5 for linuxfs
 > md5sum -c linuxfs.md5
linuxfs: OK
check md5 for vmlinuz
 > md5sum -c vmlinuz.md5
vmlinuz: OK

>> uuids
Using antiX/MX grub config 2.0
 > mkdir -p /run/live-usb-maker/uefi/boot/grub
 > cp /run/live-usb-maker/main/boot/grub/config/efi-grub.cfg /run/live-usb-maker/uefi/boot/grub/grub.cfg
 > touch /run/live-usb-maker/main/boot/grub/config/did-efi-grub
 > sed -i /^\s*#/! s/%UUID%/823de401-1b8a-4d28-820f-6e71e5b97d95/ /run/live-usb-maker/uefi/boot/grub/grub.cfg
 > rm -f /run/live-usb-maker/main/boot/grub/config/*.id
 > touch /run/live-usb-maker/main/boot/grub/config/1a3af27349929ec76372590844443671.id
 > sed -i /^\s*#/! s|%ID_FILE%|/boot/grub/config/1a3af27349929ec76372590844443671.id| /run/live-usb-maker/uefi/boot/grub/grub.cfg

>> install
extlinux version 6.04
 > dd status=none bs=440 conv=notrunc count=1 if=/usr/lib/syslinux/mbr/mbr.bin of=/dev/sdl
 > rm -f /run/live-usb-maker/main/boot/syslinux/chain.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/gfxboot.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/ldlinux.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/libcom32.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/libmenu.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/libutil.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/menu.c32
 > rm -f /run/live-usb-maker/main/boot/syslinux/syslinux.bin
 > rm -f /run/live-usb-maker/main/boot/syslinux/version
 > cp /usr/lib/syslinux/modules/bios/chain.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/gfxboot.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/vesamenu.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/ldlinux.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/libcom32.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/libmenu.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/libutil.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/linux.c32 /run/live-usb-maker/main/boot/syslinux/
 > cp /usr/lib/syslinux/modules/bios/menu.c32 /run/live-usb-maker/main/boot/syslinux/
 > write_file /run/live-usb-maker/main/boot/syslinux/version 6.04
 > extlinux -i /run/live-usb-maker/main/boot/syslinux
/run/live-usb-maker/main/boot/syslinux is device /dev/sdl1

Filesystem     Type  Size  Used Avail Use% Mounted on
/dev/sdl1      ext4   15G  2.0G   13G  14% /run/live-usb-maker/main
/dev/sdl2      vfat   49M   13M   36M  26% /run/live-usb-maker/uefi

>> done

live-usb-maker took 6 minutes and 4 seconds.
3. Manually checked the 3 md5's on the USB: All "OK"
4. Booted the new 16GB Live MX-ALPHA2 USB, and at GRUB menu opted for the option: "Check Integrity of Live Media", and as per @fehlix instructions, got this:
md5 Pass.png
5. Boot was done WITHOUT PERSISTENCE: I wanted to check if the Update would complete. And...YES! The Updater completed successfully for all 130 Updates! There were some error messages about missing firmware, etc. However, the key was that the Updater ran to completion, and the Updater Icon in the Panel (Green Box) turned to an Empty Open Box (Black and White), showing that all the updates took.

6. So, it seems to me that perhaps my issue with the Live Media (remember: unable to complete updates; cannot install anything!), is my use of Persistence-- For the other attempts I had chosen either "persist_static" or "persist_static_root", along with the Boot Option "from=usb".

7. Question: Which options for persistence should I choose? Is there a set of options that are more reliable than others?

8. Also, I noticed that when I had chosen persistence on those attempts, while booting, I set-up passwords for root and home. However...upon Reboot, I was never prompted for a password to login. That doesn't seem right. Shouldn't there be a login dialog for the "new" home user? If not, why is there an option to set a password for "home" (or "root", for that matter)?

I have watched @dolphin_oracle's videos on the subject (as well as the remastering video), but I thought I would ask for some expert opinion at this point.

Anyway...Bottom Line:

Especially since it seems that it is at this step that is causing problems for persistent updating:

What's the best way to proceed for setting up Persistence on the new Live Media? :confused:
You do not have the required permissions to view the files attached to this post.

Locked

Return to “General”