See linked issue. Downloaded latest Fedora Kinoite x86_64 ISO on Windows using Chrome https://download.fedoraproject.org/pub/fedora/linux/releases/39/Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-39-1.5.iso flashed it to a usb stick with fedora media writer on windows 11 booted, did the verification check, it failed. Rebooted and installed, it works normally. Opening this bug as it was said to be not reproducible.
I can confirm this. This only happens on the latest version of FMW on Windows Only though. works fine with the Linux version (No idea about MacOS). https://github.com/FedoraQt/MediaWriter/issues/669
It fails the validation check but still installs properly if you skip that check? Can you confirm if the problem appears on Fedora Workstation or Fedora KDE install media?
Proposed as a Blocker for 40-beta by Fedora user sgallagh using the blocker tracking app because: Beta Criterion: "Release-blocking live and dedicated installer images must boot when written to a USB stick with any of the officially supported methods." Officially supported methods includes the Windows Fedora Media Writer tool.
I took the safest route to reproduce this: 1- Downloaded the freely available Fedora 39 iso downloadable from https://fedoraproject.org/workstation/download (Use the Torrent download) 2- Booted into Windows (Bare metal, not VM) 3- Downloaded FMW from the link in #1, installed. Burned the image onto USB. 4- Booted (Again, baremetal) into the usb flash drive, did a media test. Failed.
Created attachment 2021428 [details] Failed test
Just to confirm: does the installer itself run to completion if you skip the media check?
Hi, I think this is a long-standing issue, it was most like present for past couple Fedora releases. I'm afraid that fix for this and some other related issues (like drive restoration on Windows) would require a rewrite of how we write images on Windows using Windows API. This is something I have zero experience with, not to mention that I don't have capacity to work on this in the near future. Fedora Media Writer used to have a full time developer working on it, before it went under my maintanence and it didn't really change much internally (except UI-wise) since then. There are definitely technical depts in some areas. Another issue is that even if we fix this, we won't get an official binary published on getfedora.org, because we are not signing Windows binaries since last year, after a certificate we used to have expired and signing of Windows binaries got more complex. I'm open to review PRs if someone decides to fix this issue, but I'm afraid that's the only thing I can promise you right now.
(In reply to Stephen Gallagher from comment #6) > Just to confirm: does the installer itself run to completion if you skip the > media check? Checking into that now
(In reply to Stephen Gallagher from comment #6) > Just to confirm: does the installer itself run to completion if you skip the > media check? So, I installed this on a VM, and booted from it. Went through setup, everything seems to have worked fine.
Just to triple check, I also booted from the USB drive and tested the media. It did still fail.
(In reply to Steve Cossette from comment #1) > No idea about MacOS FMW works as expected on MacOS and the media check result is PASS.
Yeah interestingly enough, I tried to burn the workstation image using Rufus in Windows. First, I tried to write the image in "ISO mode" and it complained it didn't have a copy of our custom grub version. So I instead burned it in DD mode, and it succeeded. But, booting from the image still results in a fail at 4.8% which is odd.
I've tested FMW 5.0.6 (the official stable version from getfedora.org) on Windows 11, I've written both F39 Workstation Live and F40 Workstation Live Beta RC 1.2, and both pass checkisomd5 just fine. So this is NOT an universal issue, just to make that clear. On the other hand, I've seen 4.8% errors even on Fedora in the past. My assumption is that it happens when some partition gets automounted and some filesystem metadata change (and then the whole checksum changes). (In reply to Jan Grulich from comment #7) > Fedora Media Writer used to have a full time developer Slightly off topic, but on my Win11, I had to burn each image twice, the first write attempt always failed after a while. FMW will bit-rot more and more, if we don't resolve staffing and certificate signing.
Someone on the Fedora Discord called Yuu says this might have to do with USB automount on Windows disabling automount and flashing a USB should hopefully then create one that passes the checksum test no idea what that means myself as i rarely use Windows
Discussed at 2024-03-14 Fedora Beta Go/No-Go meeting, acting as a blocker review meeting: https://meetbot-raw.fedoraproject.org/teams/f40-beta-go-no-go-meeting/f40-beta-go-no-go-meeting.2024-03-14-17.01.html . Rejected as a blocker on the basis that it doesn't entirely violate the criteria (it is possible to write a bootable image) and it is complex to fix for various reasons outlined above.
I believe that Yuu fellow is correct: some time ago, I forgot to unplug a Fedora USB drive before booting into a W10 installation, and the media check started to fail exactly at 4.8%; apparently, Windows tries to automount everything with wild abandon (even if you never get past the login screen), and instantly writes some hidden garbage on the connected disks, which ends up breaking the media check. See also: https://superuser.com/questions/1199823/how-to-prevent-creation-of-system-volume-information-folder-in-windows-10-for
I can verify that this is most certainly an error with Windows and not Fedora Disk Writer. I was having the same issue and out of curiosity made the following test after seeing this bug report. I created a new disk using disk writer on my computer running fedora and then booted from it on the windows machine I was originally trying to install on. It then passes the check. After rebooting in to Windows 10, and then trying to boot from the disk once more causes it to fail.
It just happened to me today, once, after creating the image using FMW on Fedora 40. So as I said before, this is not OS-specific. But on some OSes the likelihood might be higher.
*** Bug 2275270 has been marked as a duplicate of this bug. ***