- This topic has 12 replies, 6 voices, and was last updated Oct 18-10:58 am by anticapitalista.
-
Posts
-
anticapitalista
Could some of you test if live-usb-maker (cli and gui versions) work? I think the gui app may be broken for antiX-19 series.
Make sure you are fully upgraded.
Test 1: Use live-usb-maker (cli) to ‘burn’ a live usb. Does it finish correctly and boot?
Test 2: Use live-usb-maker (gui) to ‘burn’ a live usb. Does it finish correctly and boot?
Test 3: Use live-usb-maker (gui) to ‘burn’ in dd mode. Does it finish correctly and boot?
Thanks
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
ex_Koo
anticapitalista
I will have a look at these after work tonight with antiX 19-b3 will test booting on my main and t430 as well.
christophe
I upgraded my 19.b3 32-bit frugal (base version), then tested both gui & cli live-usb-maker — did both for full-featured antix & dd. All 4 live-usbs created fine & booted perfectly.
- This reply was modified 3 years, 6 months ago by christophe.
confirmed antiX frugaler, since 2019
ile
Hello anticapitalista
using hp 8440p antiX-19.b3_x64, 4.9.189-antix.1-amd64-smp x86_64,upgraded, spacefm-fluxbox
live-usb-maker 0.4.0 , live-usb-maker-gui-antix 0.2.32 using fluxbox menu, ControlCentre >Disks >Live USB Maker (gui)=
target usb2 100% Full-featured mode , checkmark Make the ext4 filesystem even if one exists. burn MX-19 beta-3_x64iso to device.
This live OS device booted yes normally to default desktop on one desktop Firsti3intel and on one notebook Firsti5intel machines.
one for one on #Test 23 target usb2 Image mode , burn antiX-19.b3_x64-fulliso to device.
This completed dd file device booted yes normally to default desktop on one desktop and on one notebook machines.
one for one on #Test 31 using fluxboxmenu, Applications >System >App Select >>Command Line Control Centre >>Execute or
using fluxbox menu, Applications >antiX >Command Line Control Centre >>Live System Centre >>live-usb-maker
target usb2 , full-featured, from ISO antiX-19.b3-full_x64. make_, copy.
This completed live OS device booted yes normally to default desktop on one desktop and on one notebook machines.
one for one on #Test 1That is full success but just one trial each. The full-featured devices took five and a half minutes to burn.
- This reply was modified 3 years, 6 months ago by ile. Reason: additional machine trial
All tested with antiX-17.4.1_x64-base.iso.
Both cli Full featured and dd burned and booted
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
GUI dd burned and bootedGUI Full featured failed to even burn . (Even tried twice)
LOGS~~~
live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 mount: /media/koo/antiX-uefi: /dev/sdc2 already mounted or mount point busy. devmon: error mounting /dev/sdc2 (32) mount: /media/koo/antiXlive-2: /dev/sdc1 already mounted or mount point busy. devmon: error mounting /dev/sdc1 (32) live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) Empty filename passed to function Options: "-N " start io is 0 max progress bar is 1294336 live-usb-maker gui -N -C off --from="/media/storage1/antiX-17.4.1_x64-base.iso" -t /dev/sdc live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) "" EXIT="abort" live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 mount: /media/koo/antiX-uefi: /dev/sdc2 already mounted or mount point busy. devmon: error mounting /dev/sdc2 (32) mount: /media/koo/antiXlive-2: /dev/sdc1 already mounted or mount point busy. devmon: error mounting /dev/sdc1 (32) EXIT="abort" live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) EXIT="abort" lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) Empty filename passed to function Options: "-N " start io is 0 max progress bar is 1296384 live-usb-maker gui -N -C off --from="/home/koo/antiX-17.4.1_x64-base.iso" -t /dev/sdcThe above GUI burns were done on live-usb-maker-gui-antiX 0.2.2 before todays update to 0.2.3 after the update.
GUI Full featured burned and booted. Fixed
mv: cannot stat '/home/koo/scr/screenshot-thumb.jpg': No such file or directory mv: cannot stat '/home/koo/scr/screenshot-thumb.jpg': No such file or directory info: restarting jgmenu... live-usb-maker-gui-antix version: 0.2.3 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) EXIT="abort" Empty filename passed to function Options: "-N " start io is 676 max progress bar is 1297060 live-usb-maker gui -N -C off --from="/home/koo/antiX-17.4.1_x64-base.iso" -t /dev/sdc ""BobC
Running antiX-19.b3-full_x64 with all updates. Yesterday, GUI from Control-Centre failed to burn.
I see there was new code for that today, so will try again with today’s updates.
In dd mode from control centre with all updates applied to antiX-19.b3-full_x64, the sha256sum did not match.
What is interesting is that if I run the dd command manually that the log had in it, the the checksum matches, but from the control centre it does not. I happened to have burned nutyx to a usb before I saw this post, and so was checking it.
Here is the log of when I ran it via the GUI from a terminal, I see now it was running version 0.2.2 at that time:
bobc@xps15:/usr/local/bin $ sudo live-usb-maker-gui-antix [sudo] password for bobc: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' live-usb-maker-gui-antix version: 0.2.2 df -T / |tail -n1 |awk '{print $2}' live-usb-maker --help | grep data-first lsblk --nodeps -nlo name,size,model,vendor -I 3,8,22,179,259 . /usr/local/lib/cli-shell-utils/cli-shell-utils.bash;get_drive $(get_live_dev) Options: "-N " start io is 1 max progress bar is 3514369 live-usb-maker gui partition-clear -NC off --target sdc "" dd bs=1M if="/media/BIGData/iso/NuTyX_x86_64-mate-20191015.iso" of=/dev/sdc "" bobc@xps15:/usr/local/binWhen I check the sha256sum I get one value, but its different than the one it was supposed to be, and I recalculated it from the .iso just to be sure:
$ sudo head -c $(stat -c '%s' NuTyX_x86_64-mate-20191015.iso) /dev/sdc | sha256sum 2edc6f591161ee55804068fe1b33b3c3533485929dc1b443e4d5abff224c65fb - bobc@xps15:/media/BIGData/iso $ cat NuTyX_x86_64-mate-20191015.sha256sum e6f3ac1167d8d4ea0eabe1bb77a5061a2391a9587ce15204bbdba8cae4ce7136 NuTyX_x86_64-mate-20191015.iso bobc@xps15:/media/BIGData/iso $ sha256sum NuTyX_x86_64-mate-20191015.iso e6f3ac1167d8d4ea0eabe1bb77a5061a2391a9587ce15204bbdba8cae4ce7136 NuTyX_x86_64-mate-20191015.isoSo then I use the dd command from the log to write it again and check it, but it looks good:
$ sudo dd bs=1M if="/media/BIGData/iso/NuTyX_x86_64-mate-20191015.iso" of=/dev/sdc 1716+0 records in 1716+0 records out 1799356416 bytes (1.8 GB, 1.7 GiB) copied, 382.363 s, 4.7 MB/s bobc@xps15:/media/BIGData/iso $ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' NuTyX_x86_64-mate-20191015.iso) / 4096)) | sha256sum 439296+0 records in 439296+0 records out 1799356416 bytes (1.8 GB, 1.7 GiB) copied, 9.52737 s, 189 MB/s e6f3ac1167d8d4ea0eabe1bb77a5061a2391a9587ce15204bbdba8cae4ce7136 -Then I try it again from the control centre directly, wait a couple min, then come here to check it:
$ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' NuTyX_x86_64-mate-20191015.iso) / 4096)) | sha256sum 439296+0 records in 439296+0 records out 1799356416 bytes (1.8 GB, 1.7 GiB) copied, 151.238 s, 11.9 MB/s 2edc6f591161ee55804068fe1b33b3c3533485929dc1b443e4d5abff224c65fb -But its wrong again with the same value as the first time it was wrong.
$ sudo live-usb-maker-gui-antix -v QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Version: 0.2.4So I redid it via the GUI in dd mode again, and double checked the version, here is a pic of it running:
I got the same wrong checksum again:
$ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' NuTyX_x86_64-mate-20191015.iso) / 4096)) | sha256sum 439296+0 records in 439296+0 records out 1799356416 bytes (1.8 GB, 1.7 GiB) copied, 162.65 s, 11.1 MB/s 2edc6f591161ee55804068fe1b33b3c3533485929dc1b443e4d5abff224c65fb -- This reply was modified 3 years, 6 months ago by BobC. Reason: rerun and take pic
- This reply was modified 3 years, 6 months ago by BobC. Reason: repeat test
- This reply was modified 3 years, 6 months ago by BobC.
Attachments:
I will try to see if I can figure out how to do a YAD script to check an .iso compared to a checksum file and compare it to a calculated checksum from the device. I will try to do it first using PPC’s YAD screens as an example, and if I can get it to work I will try to localize it, too. I always wished I had a program to check the iso’s I burn to flash drives or CD/DVD, anyway, so I know it would be nice to have for a small amount of code.
Let me know if you see an error in my calculations. The logic came from Julien Palard here: https://unix.stackexchange.com/questions/75483/how-to-check-if-the-iso-was-written-to-my-usb-stick-without-errors
Ok, one more test and I go sleep. I burned antix 19 386 base in live mode and tested it, then did it manually via dd. The resule is the same as with nutyx in dd mode:
$ ls -l antiX-19_386-base.iso* -rw-rw-r-- 1 bobc users 730857472 Oct 16 23:00 antiX-19_386-base.iso -rw-rw-r-- 1 bobc users 56 Oct 16 22:58 antiX-19_386-base.iso.md5 -rw-rw-r-- 1 bobc users 88 Oct 16 22:58 antiX-19_386-base.iso.sha256 bobc@xps15:/media/BIGData/iso $ cat antiX-19_386-base.iso.sha256 a2b1d497ecab37fd37b286317bf0a682f90e95cbe451b8544b2d0134860cbff7 antiX-19_386-base.iso bobc@xps15:/media/BIGData/iso $ sha256sum antiX-19_386-base.iso a2b1d497ecab37fd37b286317bf0a682f90e95cbe451b8544b2d0134860cbff7 antiX-19_386-base.iso bobc@xps15:/media/BIGData/iso burn to flashdrive from control centre here, note wrong checksum $ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' antiX-19_386-base.iso) / 4096)) | sha256sum 178432+0 records in 178432+0 records out 730857472 bytes (731 MB, 697 MiB) copied, 4.07511 s, 179 MB/s f456ffd33c529277095657db7d7104cfb0cad38156030163666f723d215c5bef - bobc@xps15:/media/BIGData/iso now write manually via dd command, note correct checksum $ sudo dd bs=1M if="antiX-19_386-base.iso" of=/dev/sdc 697+0 records in 697+0 records out 730857472 bytes (731 MB, 697 MiB) copied, 7.22643 s, 101 MB/s bobc@xps15:/media/BIGData/iso $ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' antiX-19_386-base.iso) / 4096)) | sha256sum 178432+0 records in 178432+0 records out 730857472 bytes (731 MB, 697 MiB) copied, 3.92659 s, 186 MB/s a2b1d497ecab37fd37b286317bf0a682f90e95cbe451b8544b2d0134860cbff7 -Tried again this morning with cli version. It appears to write but the sha256sum and md5sums do not match with originals. This assumes I am doing my check correctly.
$ sudo live-usb-maker -v live-usb-maker version 2.41.07 (Thu 10 Oct 2019 11:20:26 PM MDT) cli-shell-utils version 2.41.03 (Tue 15 Oct 2019 02:39:07 PM MDT) bobc@xps15:/media/BIGData/iso $ sudo live-usb-maker =============================================================================== Starting live-usb-maker 2.41.07 =============================================================================== Only one target usb device was found sdc Will use target device sdc (29.8G SanDisk SSD_U110_32GB) Please select an action to perform = Make a full-featured live-usb > Start live-usb with a data partition > Make an encrypted full-featured live-usb > Make a customized live-usb (includes encryption option) > Other options Press <Enter> to select the highlighted entry Use 'h' for help, 'r' to redraw, 'q' to quit Please select the source for the new live-usb = Copy from an ISO file Press <Enter> to select the highlighted entry Use 'h' for help, 'r' to redraw, 'q' to quit Please enter the filename (tab completion is enabled) /media/BIGData/iso/antiX-19_386-base.iso You entered: /media/BIGData/iso/antiX-19_386-base.iso Is this correct? = yes > no Press <Enter> to select the highlighted entry Use 'h' for help, 'r' to redraw, 'q' to quit Check md5 of the file antiX-19_386-base.iso? = yes > no Press <Enter> to select the highlighted entry Use 'h' for help, 'r' to redraw, 'q' to quit Checking md5 ... antiX-19_386-base.iso: OK Will use source file /media/BIGData/iso/antiX-19_386-base.iso Distro: antiX-19_386-base Marielle Franco 16 October 2019 Found grub config 2.0 Total Used Extra entire drive 29.8 GiB 29.8 GiB 1 MiB main partition 29.8 GiB 738 MiB 29.0 GiB uefi partition 50 MiB 18 MiB 32 MiB ------------------------------------------------------------------------------- Ready to make live-usb on device sdc ... by copying file /media/BIGData/iso/antiX-19_386-base.iso ------------------------------------------------------------------------------- Shall we begin? = yes > no > pretend mode Press <Enter> to select the highlighted entry Use 'h' for help, 'r' to redraw, 'q' to quit >> partition-clear >> partition-make Using msdos partitioning >> makefs-bios >> makefs-uefi Filesystem Type Size Used Avail Use% Mounted on /dev/sdc1 ext4 30G 44M 30G 1% main /dev/sdc2 vfat 49M 512 49M 1% uefi >> copy-uefi copy from iso to uefi partition files [Ee][Ff][Ii] version Fix Dell uefi memtest bug >> copy-main copy from iso to main partition copy /antiX/vmlinuz copy /antiX/initrd.gz copy remaining files ... |=================================================================================================================================================================================>100% >> check-usb-md5 check md5 for initrd.gz check md5 for linuxfs check md5 for vmlinuz >> uuids Using antiX/MX grub config 2.0 >> install extlinux version 6.04 Filesystem Type Size Used Avail Use% Mounted on /dev/sdc1 ext4 30G 740M 29G 3% main /dev/sdc2 vfat 49M 4.2M 45M 9% uefi >> done live-usb-maker took 14 seconds. bobc@xps15:/media/BIGData/iso $ sha256sum antiX-19_386-base.iso a2b1d497ecab37fd37b286317bf0a682f90e95cbe451b8544b2d0134860cbff7 antiX-19_386-base.iso bobc@xps15:/media/BIGData/iso note sha256sum is different $ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' antiX-19_386-base.iso) / 4096)) | sha256sum 178432+0 records in 178432+0 records out 730857472 bytes (731 MB, 697 MiB) copied, 4.0923 s, 179 MB/s 5a6192c6e4ad15a75c305b8c9e1937170535dd63d11f64ecb4e4ba28a6dd653f - bobc@xps15:/media/BIGData/iso md5sum is different too $ cat antiX-19_386-base.iso.md5 c44fc332dd1e0d02a14414ebfb7bff29 antiX-19_386-base.iso bobc@xps15:/media/BIGData/iso $ md5sum antiX-19_386-base.iso c44fc332dd1e0d02a14414ebfb7bff29 antiX-19_386-base.iso bobc@xps15:/media/BIGData/iso $ sudo dd if=/dev/sdc bs=4096 count=$(($(stat -c '%s' antiX-19_386-base.iso) / 4096)) | md5sum 178432+0 records in 178432+0 records out 730857472 bytes (731 MB, 697 MiB) copied, 1.49265 s, 490 MB/s 74077b7843df03705f15a0d8e1caf475 - bobc@xps15:/media/BIGData/isoI saw its been updated today. I burned it again with the cli version, told it to check md5, and it said they were ok. I booted it in a different machine with checkmd5 on at boot and it booted and ran fine. I think the test command that tested the md5 of the flashdrive doesn’t work in all cases anymore, suspecting the ones that are not written in straight dd mode.
Yes, I am pretty sure the last command to get the md5 of the flashdrive doesn’t work right for a distro burned as an iso-hybrid, and that’s why it doesn’t match. It makes sense, but I would have thought there would be a way to calculate it and get a matching number. Sometimes flashdrives are bad.
Anyway, the current program is working, so I feel better… Thanks for antix-19!
- This reply was modified 3 years, 6 months ago by BobC.
PPC
I will try to see if I can figure out how to do a YAD script to check an .iso compared to a checksum file and compare it to a calculated checksum from the device
Hi Bob, here’s a script that may help you- it does half the job- it calculates the checksum of a file, and displays it on screen. The user can then copy the results and open the file checksum’s text file, paste the result below the original value and visually check if the values match…
You can automate the second part (comparing the checksum string)- but I felt no need to do that- I had no time, so I just adapted 2 scripts from YAD’s smokey01 webpage- that did not run anymore… (I hope the forum does not mangle this…)#!/bin/sh
v=yad --button="OK" --text="Drop your file here, then press the button and wait for a new window with the calculated checksum" --dnd | sed 's/^.......//'
o=$(sha256sum $v)
yad –title=”CheckSum” –form –field=”” “$o” –no-buttons –geometry=550×50+500+0- This reply was modified 3 years, 6 months ago by PPC.
anticapitalista
Since antiX-19 has been released, I’m closing this thread.
Thanks for all the feedback.Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
- The topic ‘antiX-19 beta users – please test’ is closed to new replies.
