Bug 215296 – unknown exception when upgrading FC5 to FC6 thru HTTP

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 215296 - unknown exception when upgrading FC5 to FC6 thru HTTP

Summary:	unknown exception when upgrading FC5 to FC6 thru HTTP

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	anaconda (Show other bugs)
Sub Component:
Version:	6
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Anaconda Maintenance Team
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2006-11-13 05:36 EST by Peter Cermak
Modified:	2007-11-30 17:11 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-11-13 10:21:15 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
generated by installer (340.59 KB, text/plain) 2006-11-13 05:36 EST, Peter Cermak	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Peter Cermak 2006-11-13 05:36:54 EST

Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.run upgrade FC5 -> FC6 thru HTTP
2.at the end it fails on bootloader upgrade
3.reboot -> fail to boot because of fsck error
  
Actual results:
unknown exception -> see attached file

Expected results:


Additional info:
/boot on /dev/hda1
/ on /dev/VG00/LG00 (lvm)
no specialities in PC or system, only FC on /dev/hda

Comment 1 Peter Cermak 2006-11-13 05:36:54 EST

Created attachment 141035 [details]
generated by installer

Comment 2 Chris Lumens 2006-11-13 10:21:15 EST

According to your anaconda log, you are having problems with the hard drive you
are installing to.  This could be due to hardware failure, cabling, or other
such issues.  Looks like the media was remounted as read-only automatically
because of these problems.

<4>hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
<4>hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=14942815,
sector=14942813
<4>ide: failed opcode was: unknown

Note You need to log in before you can comment on or make changes to this bug.