Bug 213519
| Summary: | upgrade fails on RAID1 LVM root | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Andrew Gilmore <agilmore> | ||||||||||
| Component: | anaconda | Assignee: | Peter Jones <pjones> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | medium | ||||||||||||
| Version: | 6 | CC: | jgranado, triage | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i386 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | bzcl34nup | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2008-04-24 14:09:02 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: |
|
||||||||||||
|
Description
Andrew Gilmore
2006-11-01 19:39:05 UTC
Created attachment 140024 [details]
Anaconda traceback log
Created attachment 140025 [details]
FC5 fstab for affected computer
Created attachment 140027 [details]
RAID setup
Created attachment 140028 [details]
LVM information, ran pvs, vgs, and lvs from lvm console
Note that this LVM on RAID1 setup was created by the FC5 anaconda installer, and I haven't touched it since. Comment on attachment 140028 [details]
LVM information, ran pvs, vgs, and lvs from lvm console
Didn't know that BZ had such a problem IDing text files. Sorry for the spam.
Does booting with 'linux nodmraid' help? Away from the box for a week, sorry. Will test Monday, November 13. booting with linux nodmraid allowed the install to continue. Thanks for the tip. Probably ought to have a good list of bootloader commands to try with install failures linked to the CommonBugs page. I did get an error about the MBR not being suitable for bootloader install. Not sure what that was about. Fedora apologizes that these issues have not been resolved yet. We're sorry it's taken so long for your bug to be properly triaged and acted on. We appreciate the time you took to report this issue and want to make sure no important bugs slip through the cracks. If you're currently running a version of Fedora Core between 1 and 6, please note that Fedora no longer maintains these releases. We strongly encourage you to upgrade to a current Fedora release. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained and closing them. http://fedoraproject.org/wiki/LifeCycle/EOL If this bug is still open against Fedora Core 1 through 6, thirty days from now, it will be closed 'WONTFIX'. If you can reporduce this bug in the latest Fedora version, please change to the respective version. If you are unable to do this, please add a comment to this bug requesting the change. Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we are following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. And if you'd like to join the bug triage team to help make things better, check out http://fedoraproject.org/wiki/BugZappers There is a bug where the dmraid stuff just blocks. This bug has not been solved yet and we are still working to fix it. However there is a work around. If you use nodmraid, the installer will ignore/skip the dmraid stuff allowing the install to finish. This is a workaround and does not fix the problem. There is a long list of bugs that are filed against this problem. This bug is one of them. We have decided to close all the related nodmraid bugs and leave just one open that will represent all of the others. So this bug will be duped for this reason. *** This bug has been marked as a duplicate of 409931 *** |