- This topic has 3 replies, 2 voices, and was last updated Jun 21-9:17 am by Xaver.
June 19, 2019 at 2:55 am #23366MemberXaver
At the end of creating the live-usb I get this error message:
Non-Fatal-Error At least one md5 checksum did not match
The iso was created with iso-snapshot. It does boot in VirtualBox without problems.
If I check the iso with GtkHash, md5 and sha512 are ok.
If I check md5 from the boot menu of the iso, I get the same error message.
June 19, 2019 at 4:23 pm #23437Forum AdminBitJam
- This topic was modified 8 months, 1 week ago by Xaver.
While running the live system, please run the following commands and let us know the output:
cd /live/boot-dev/antiX md5sum -c *.md5 head *.md5 ls -lh linuxfs* vmlinuz* initrd.gz*
If you want to save the output to a file you could do something like:
cd /live/boot-dev/antiX md5sum -c *.md5 | tee -a ~/Live-usb-storage/md5-debug head *.md5 | tee -a ~/Live-usb-storage/md5-debug ls -lh linuxfs* vmlinuz* initrd.gz* | tee -a ~/Live-usb-storage/md5-debug
I imagine this may be a harmless bug. Perhaps one of our programs did not update an .md5 file correctly.
It was good to check the md5 of then entire iso but that does not guarantee that the md5 checks for the 3 files were done correctly, it just means all the bytes in the iso file are correct even if those correct bytes include an incorrect .md5 file.
You could also run the same commands on a different system with the live-usb plugged in and mounted. Just cd to the $MOUNT_POINT/antiX/ directory and run the same tests.
Context is worth 80 IQ points -- Alan KayJune 20, 2019 at 6:43 am #23511MemberXaver
The created Live-USB does not boot. I forgot to mention that. So I cannot run this live system.
Here is the requested output for USB.stick:
$ md5sum -c *.md5 initrd.gz: OK linuxfs: FEHLSCHLAG md5sum: WARNUNG: die 1 berechnete Prüfsumme passte NICHT vmlinuz: OK
FEHLSCHLAG = failure
die 1 berechnete Prüfsumme passte NICHT = the 1 calculated checksum did not match
$ head *.md5 ==> initrd.gz.md5 <== c199b1bda4b3d57ac09f4f8084c5d57a initrd.gz ==> linuxfs.md5 <== 19a19642fa6c93c44eaf51a3aec3541e linuxfs ==> vmlinuz.md5 <== b06852fb64d62b616b94df3d69f9729d vmlinuz
$ ls -lh linuxfs* vmlinuz* initrd.gz* -rw-r--r-- 1 root root 6,9M Jun 19 08:13 initrd.gz -rw-r--r-- 1 root root 44 Jun 19 08:13 initrd.gz.md5 -rw-r--r-- 1 root root 3,2G Jun 19 08:36 linuxfs -rw-r--r-- 1 root root 42 Jun 19 08:37 linuxfs.md5 -rw-r--r-- 1 root root 4,5M Jun 19 08:13 vmlinuz -rw-r--r-- 1 root root 42 Jun 19 08:13 vmlinuz.md5
June 21, 2019 at 9:17 am #23611MemberXaver
- This reply was modified 8 months, 1 week ago by Xaver.
After a system upgrade (to kernel 5.1.12) the error has disappered. The live-USB does boot fine now.
Start-Date: 2019-06-21 16:05:14 Commandline: apt full-upgrade Install: linux-image-5.1.12-towo.1-siduction-amd64:amd64 (5.1-12.1, automatic), linux-headers-5.1.12-towo.1-siduction-amd64:amd64 (5.1-12.1, automatic) Upgrade: linux-image-siduction-amd64:amd64 (5.1-10, 5.1-12.1), linux-libc-dev:amd64 (4.19.37-4, 4.19.37-5), libwbclient0:amd64 (2:4.9.5+dfsg-4, 2:4.9.5+dfsg-5), live-usb-maker:amd64 (0.3.12, 0.3.14), antix-libs:amd64 (0.6.19, 0.6.20), nano:amd64 (3.2-2, 3.2-3), cli-aptix:amd64 (0.2.16, 0.2.17), libpq5:amd64 (11.3-1, 11.4-1), cli-shell-utils:amd64 (0.3.21, 0.3.22), samba-libs:amd64 (2:4.9.5+dfsg-4, 2:4.9.5+dfsg-5), antix-installer:amd64 (1.0.6, 1.0.7), samba-common:amd64 (2:4.9.5+dfsg-4, 2:4.9.5+dfsg-5), libsmbclient:amd64 (2:4.9.5+dfsg-4, 2:4.9.5+dfsg-5), firefox-esr-l10n-de:amd64 (60.7.1esr-1, 60.7.2esr-1), linux-headers-siduction-amd64:amd64 (5.1-10, 5.1-12.1), firefox-esr:amd64 (60.7.1esr-1, 60.7.2esr-1) End-Date: 2019-06-21 16:07:03
- This reply was modified 8 months ago by Xaver.
- You must be logged in to reply to this topic.