Wrong md5sum leading to failed installation?

Hi all, hope you are all doing well.

I've tried installing the linuxcnc 2.9.2 ISO as described here . I initially tried to download using the link on the downloads page (using firefox 126.0 (64-bit)). This went fine (20MB/s, sweet). I got the file "LinuxCNC_2.9.2-amd64.hybrid.iso" and compare the md5 checksum as well as the SHA256. None of them match!

My result:
md5: d541b51f02ecc6f07fe652faa0fc4a2b  LinuxCNC_2.9.2-amd64.hybrid.iso
sha256: a2c9df3d1a16c2e09c66bbb87869be876892fd6bf9182fc39009c944cbf8f800  LinuxCNC_2.9.2-amd64.hybrid.iso

Results in the article:, I got the following response:

failed on url www.linuxcnc.org/iso/LinuxCNC_2.9.2-amd64.hybrid.iso
could not read control file from URL www.linuxcnc.org/iso/LinuxCNC_2.9.2-amd64.hybrid.iso

Undeterred, I continued with my wrong checksum ISO and used

dd if=

LinuxCNC_2.9.2-amd64.hybrid.iso

of=/dev/sdb

to write my the ISO to my FAT formatted USB drive. I plugged it into my sacrificial PC and tried to do a live version. However, once I saw the initial blue Debian 12, I was greeted with a bunch of errors along the line of:

SQUASHFS ERROR: XZ DECOMPRESSION FAILED DATA PROBABLY CORRUPT

together with some specific address that was apparently not working. I could get a CLI using ctrl+alt+f?3? I believe, and execute some basic commands (cd, ls, mkdir).

Anyway, I've googled a bit and what I understand 3 things could have gone wrong:
1. wrong iso.
2. incorrect writing to USB
3. fault in USB.

I don't think I did anything wrong while writing to the USB, but it could be that my USB is faulty. To rule that out I ordered a new USB stick. Lets see what it does when it arrives in the mail tomorrow. In the meanwhile, I hope to start the discussion on point 1:
-How come my checksum doesn't match, and why can I not use zsync?

Any ideas / tips / suggestions on this point or any other point in my message would be greatly appreciated.

Many thanks,
Jerry

Apologies for the weird formatting, I tried to change it but my edits do not seem to take effect. I hope the idea is still clear. I'm not really familiar with posting on forums

Hi tommylight,

Thank you for the suggestion I just tried this with Rufus. I got the live version to start now, so I decided to move onto the installation. This is where I landed on:
"installation step failed ... The failing step is: Install the system".

I actually got here before, when I tried making the bootable USB with 'startup disk creater' on ubuntu. Figured this was incorrect and moved to the steps as described in the guide.

pressing ctrl alt f4 showed some strange logs.
'cant open blockdev'
'the tar process copying the live system failed'
'xz decompression failed'

will try tomorrow with the new USB stick and some different rufus options / win32diskimager. Current USB is too slow in writing for doing this repeatedly.

win32diskimager I found was best when I used to use windows, it doesn't try to be smart, it's a basic byte by byte copy. Like dd on linux.

On Ubuntu\Mint USB Image Writer is the same. I use it to copy hybrid ISO to USB drives and custom RPi images to SDCards.

If the checksums don't match (and you have confirmed the online checksum is correct) you have None & Buckley's chance of getting it going.

A VM (Virtual Box)is a good way to check if a downloaded ISO will boot without wasting time writing it to a device.

Thanks for the suggestions, will try win32diskimager when I get the new stick.

In the meanwhile I've tried to use the virtual machine, thats a great idea! Should eliminate any chance of the stick being bad. I've seen other forum posts here where a faulty hardware device worked on ubuntu install but not debian, which is why I initially suspect the stick to be bad.

In another forum post (i found out about the search functionality, albeit a bit late) I read that zsync does not take HTTPS, only HTTP, so when trying that I managed to also download the correct ISO version.

I also saw Balena Etcher coming along, might try it too if I don't have any results.

Will revert back once I have results on the VM / new hardware / new ISO / win32diskimager.

Thanks for the tip on Ventoy, I just read their main page, looks very interesting!

 

Hi all just wanted to give a quick followup:
I used KVM + virt-manager to try the ISO I downloaded, and it worked! I could install without problems this time to the virtual machine, further strengthening the hypothesis of the bad USB. At the same time my new usb drive arrived. Followed the same steps as before, I now managed to complete the full installation.

Summary: Even though the USB stick was able to upload Ubuntu 20.04 to a machine (and still is), it didn't manage to do Debian 12. Switching to a new usb stick solved the problem.

Many thanks for the replies. The next step in my journey will be obtaining an appropriate ethercat servo driver

Balena etcher is multiplatform and the only one I use. The ISO's were tested with it when they were built.
Win32DiskImager has never worked for me for years.
Rufus needs to download stuff of the internet whwn it runs which is disconcerting...