Bug 499974
Summary: | Error creating LVM partition | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | George Galt <george> |
Component: | anaconda | Assignee: | David Lehman <dlehman> |
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | agk, aj.werkman, anaconda-maint-list, bmarzins, bmr, ctdiaz, dcantrell, dwysocha, heinzm, jlaska, lvm-team, mbroz, msnitzer, prockai, rmaximo, tpelka, vanmeeuwen+fedora, vinic |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | anaconda_trace_hash:92bc7c0d0223ec6ab54f12df5bd88ccebd8271659d8fee959b0df1f1bf2f2738 | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-28 12:28:35 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
George Galt
2009-05-09 17:50:02 UTC
Created attachment 343227 [details]
Attached traceback automatically from anaconda.
According to the program.log in your traceback report, we create a physical volume on /dev/sde3, but then are unable to add it to the volume group, due to the following message: No physical volume label read from /dev/sde3 /dev/sde3 not identified as an existing physical volume Unable to add physical volume '/dev/sde3' to volume group 'vg_server'. Created attachment 343819 [details]
Attached traceback automatically from anaconda.
I just got this. Here was my setup. Two sata drives that were previously used for a "Use entire drive" auto partition setup. This new install also checked "Use entire drive" but I only checked the first drive to be used, leaving one of the drives unchecked. Created attachment 344654 [details]
Attached traceback automatically from anaconda.
Hitting this consistently while trying to reinstall, but leaving a partition untouched that contains existing ISO media. I'm using "Custom Layout" * I add a mount point for my 5G /isos partition * I choose to reformat the existing storage layout * I create logical volumes for swap and root Created attachment 346527 [details]
Attached traceback automatically from anaconda.
I see this with a two disk configuration. I hit this while trying to reproduce bug #502286 Started with PXE and the following kickstart: =============================================================== install url --url http://<server>/fedora/development/i386/os lang en_US.UTF-8 keyboard us skipx text # Network configuration. network --device eth0 --bootproto static --ip <IP> --netmask <MASK> --gateway <GW> --nameserver <NS> --hostname <hostname> rootpw hallo firewall --disabled authconfig --enableshadow --passalgo=sha512 selinux --disabled timezone --utc Europe/Amsterdam zerombr bootloader --location=mbr --timeout=20 --append="nomodeset" clearpart --all --initlabel #part /boot --fstype ext3 --size=512 --grow --maxsize=1024 #part / --fstype ext3 --size=1024 --grow part /boot --fstype ext3 --size=512 part pv.7 --size=10 --grow --ondisk=sda volgroup VolGroup00 --pesize=32768 pv.7 logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00 --size=1000 --grow --maxsize=1984 logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024 --grow #part swap --size=512 --grow --maxsize=1024 repo --name="Fedora rawhide - i386" --baseurl=http://<server>/fedora/development/i386/os %packages @base @core %post %end Created attachment 346672 [details]
Attached traceback automatically from anaconda.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Created attachment 347548 [details]
Attached traceback automatically from anaconda.
Created attachment 347721 [details]
Attached traceback automatically from anaconda.
Created attachment 349524 [details]
Attached traceback automatically from anaconda.
This does not appear to be an LVM2 bug. All of the anaconda tracebacks attached to this bug (I've looked at 4 of them so far) show the failed vgcreate is due to the fact that the VG already exists. Specifically either: - the VG is created more than once by anaconda's install logic - the VG already exists but anaconda attempts to create it again (e.g. reinstall) If I'm somehow foolishly mistaken (that this is an anaconda storage bug) please reassign back to the LVM team with justification. Created attachment 350007 [details]
Attached traceback automatically from anaconda.
Created attachment 356177 [details]
Attached traceback automatically from anaconda.
Has anyone seen this behavior in Fedora 12? This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed. |