Bug 595869

Summary: Unhadled exception while installing F13
Product: [Fedora] Fedora Reporter: António Lima <amrlima>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: anaconda-maint-list, jonathan, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 20:08:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
trace none

Description António Lima 2010-05-25 20:03:51 UTC
Created attachment 416501 [details]

Description of problem:

After writing changes to disk, on personalized partitioning scheme I got this exception.
Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Launch installer
2. Partition you hard drive
Actual results:
Unhadled exception.

Expected results:

Go on to next install fase.
Additional info:

Comment 1 Chris Lumens 2010-05-25 20:08:12 UTC
You have a huge number of media read errors during your installation.  Did you run mediacheck beforehand?

Buffer I/O error on device sr0, logical block 7
sr 3:0:0:0: [sr0] Unhandled sense code
sr 3:0:0:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 3:0:0:0: [sr0] Sense Key : Medium Error [current] 
sr 3:0:0:0: [sr0] Add. Sense: Unrecovered read error
sr 3:0:0:0: [sr0] CDB: Read(10): 28 00 00 00 00 0e 00 00 02 00
end_request: I/O error, dev sr0, sector 56

Comment 2 António Lima 2010-05-25 20:13:35 UTC
Yes, I did, but it just hanged and never booted up. I tried to boot it again and it took a long time, but finally did. I am using a usb disk. Booting from a CD also failed, never got threw the ISO Linux text in the beguining of the boot process.

Can it be a currupted image file?