Bug 1254202

Summary:	Fedora 22 Workstation ISO fails at 4.8%
Product:	[Fedora] Fedora	Reporter:	Bastien Nocera <bnocera>
Component:	distribution	Assignee:	Václav Pavlín <vpavlin>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	dennis
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 17:32:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bastien Nocera 2015-08-17 12:26:04 UTC

Using the Fedora 22 ISO available at:
https://dl.fedoraproject.org/pub/fedora/linux/releases/22/Workstation/x86_64/iso/
and verified corrected through its sha256sum:
$ sha256sum Fedora-Live-Workstation-x86_64-22-3.iso 
615abfc89709a46a078dd1d39638019aa66f62b0ff8325334f1af100551bb6cf  Fedora-Live-Workstation-x86_64-22-3.iso

On 2 different machines (Surface 3 and Lenovo Carbon X1 1st gen) and 2 different USB keys (one Lexar, one SuperTalent), the media verification fails at 4.8%

I also tested on both machines using either gnome-disk-utility's "Restore disk image" feature, or dd'ing the image to the device.

This is really problematic on the Surface because USB keyboards are sometimes not initialised on boot, leading to verification and failure to boot.

Comment 1 Bastien Nocera 2015-08-17 13:49:24 UTC

It's possible that the problem is the same as:
https://bugzilla.redhat.com/show_bug.cgi?id=1189345
but in my case it might be Windows writing data to that disk.

Comment 2 Fedora End Of Life 2016-07-19 17:32:04 UTC

Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.