Bug 2412714
| Summary: | False FAIL on media check with Fedora Workstation 43 USB (verified ISO & checksum) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Yassin Omer <yassinomer2002> |
| Component: | anaconda | Assignee: | anaconda-maint |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 43 | CC: | a.badger, alpha, anaconda-maint, kkoukiou, kparal, w |
| Target Milestone: | --- | Keywords: | Bugfix, Upgrades |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-11-06 08:01:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Yassin Omer
2025-11-05 16:16:02 UTC
You don't need to use a media writer, Fedora's iso images are hybrid and are suitable for directly writing them to the USB device using dd. It is likely that these writers are doing more than just copying the iso to the device which is why the media check fails. Try using the instructions here to write the usb drive - https://docs.fedoraproject.org/en-US/quick-docs/creating-and-using-a-live-installation-image/#_using_a_direct_write_method FMW is the number one official method to create a USB image, working across OSes. It's heavily tested and it's working correctly. The 4.8% verification failure is well known, but we don't know how to avoid it: https://discussion.fedoraproject.org/t/install-media-sometimes-fail-media-check-at-4-8/108478 Since yassinomer2002 isn't writing it on Windows, the most likely case is that the actual PC firmware is writing data to the stick (possibly to ESP) before booting it. It should be safe to ignore this error. *** This bug has been marked as a duplicate of bug 2269373 *** |