Bug 65525
| Summary: | Upgrade of 7.2 to 7.3 crashed via CD installation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Sankofasystems <aghana> | ||||||
| Component: | anaconda | Assignee: | Michael Fulbright <msf> | ||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Mike McLean <mikem> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.2 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i386 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2002-08-15 19:37:39 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: | |||||||||
| Attachments: |
|
||||||||
Changing component to be "anaconda", and reassigning to msf. Tim Created attachment 58787 [details]
Crash dump during 7.1-7.3 upgrade
I believe this is the same exception I got while updating a 7.1 system to 7.3. In my case, the upgrade was done via a fresh boot from CD #1 (i.e., the OS was not loaded at the time). The "Upgrade Existing System" install option was selected. The exception occurred prior to the prompt for CD #3, near the end of the install. I was also upgrading from LILO to GRUB, and the hard drive was left in an unbootable state after the exception occurred. So the install had to be restarted from the beginning. The scans for packages and dependencies took much less time this attempt, which is to be expected. The "Preparing to install..." process seemed to take about the same amount of time as the first attempt. I am in the throes of the second install attempt now and it appears I am going to have to go through the whole thing again. I would have thought the packages installed on the first pass would be recognized during this phase, but it does not appear that they are. If the same exception occurs again, I supposed I will have to reformat the hard drive and install from scratch. Good thing I backed-up my data first. The crash dump was uploaded as a text file. These errors in the log:
<4>hdd: command error: status=0x51 { DriveReady SeekComplete Error }
<4>hdd: command error: error=0x50
indicate one of your IDE devices is having read errors. Have you tested your CDs?
It appears that this bug should be marked NEEDINFO rather than MODIFIED. If it is indeed modified, can somebody please give me a clue as to how to verify the fix? |
Created attachment 915102 [details] Comment (This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).