Bug 505575
| Summary: | anaconda doesn't show any lvm partitions | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas J. Baker <tjb> |
| Component: | anaconda | Assignee: | David Lehman <dlehman> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | rawhide | CC: | rmaximo, rvykydal, vanmeeuwen+fedora |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2009-06-17 12:59:14 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: | |||
|
Description
Thomas J. Baker
2009-06-12 13:53:19 UTC
I just tried this on another server that is brand new and has only had F11 preview installed on it (i.e., no old LVM layout here) and anaconda still doesn't display any LVM paritions. On my laptop, I tried just recreating the LVM setup since it didn't see the old one and that blew up anaconda. I tried to report it but it the bug buddy like dialog said it was a dup and I'd get cc'd. At this point, I can't install F11 at all even though I'm currently running the preview + rawhide/official updates. I was able to install on my laptop by doing a "remove linux" and then customizing it from there. Were you using any kickstart? If so, you might be hitting this bug: https://bugzilla.redhat.com/show_bug.cgi?id=503681, which is F11 Common Bug: https://fedoraproject.org/wiki/Common_F11_bugs#503681 Yes, that appears to be my problem exactly. And I was only using a kickstart to have the updates install at the same time and that is now taken care of by anaconda with a simple checkbox. *** This bug has been marked as a duplicate of bug 503681 *** |