For over 3 years Fedora has had the SAME problem, whether with programs like Rufus, Ventoy, etc. Is this abandoned or is it the chosen behavior to cause some kind of embarrassment? will w8 anothr 3 years mb this communit start to work
Use the fedora media writer and you should get media that will pass the test.
If writing on windows it is known that windows will damage the USB stick.
I have downloaded ISOs of different Fedora variants in 2024, all worked out fine and corresponded to their signed hashes.
However, without further information, it is not possible to identify what the exact problem is that you face. You need to give more details.
Generally, if you do not have the possibility to use the media writer (or if you do not want to install it), the generic way is to get the ISO of your preferred variant along with its CHECKSUM file, and then check the signature of the CHECKSUM file and then the ISO against the CHECKSUM. Finally, you can use dd or so to put the image on a usb drive or so. That’s not the most straightforward way that is possible and we work on improving that experience, but it is a way that should work on most Linux distros (in any case, every major distro) because it uses only tools that are available+installed in most distros even by default. In any case, all commands that are suggested on the getfedora page to get this done (curl, gpgv, sha256sum) should be available on Ubuntu too (I admit I didn’t use Ubuntu for long, but I am quite sure it still supports such default tools) → I obviously assume that you use Ubuntu (based on your user name).
Absolutely false.
However there is a known issue when using windows to create the usb media from the iso. If the user then plugs the usb device into a running windows machine windows will write to the usb device and cause it to fail when testing the media.
The simple solution:
Write the iso to the usb with rufus or balena etcher, then remove the device. Do not connect it back to a windows machine while windows is booted.
I am guessing you may be using windows to create the usb device since you mentioned rufus and there is an absolute dearth of other information.
1 Like
I’ve ran into 4% fails from Fedora Media Writer on Windows often enough to not use it, same with Rufus for Linux isos.
Why is it that Etcher’s the only thing that can write drives correctly? It seems like Fedora would have rushed to fix this considering it’s their tool writing their distro. It sounds like the problem is known (Windows doing something extra after writing?) and Etcher proves a workaround exists.
I’m not sure on the benefit of advertising an in-house inconsistent disk writer, but Ubuntu even recommends Etcher: Download Ubuntu Desktop | Ubuntu
The way it creates the USB image will cause the check done by anaconda to be skipped. The same for Rufus unless you use the DD mode.
And it almost imposible to avoid inserting the USB device into the Windows system as it is already inserted when running MediaWriter.
it used to happen on previous Fedora snapshots. But after 40 or 41, I have never seen this I installed many times though (Via Rufus, Fedora Media Writer, Ventoy, Etcher)
Anaconda still did the media check in all cases (from Etcher, Rufus in dd, iirc with Rufus Hybrid, different Fedora media writer versions Windows, and dd Linux).
I use a tool to write the image, close the writing program, and safely remove USB from Windows taskbar. I can do that with the above 3 tools and it seems like the most straightforward way to do it, but why is Etcher only able to do that without extra writes?