Bug 590692
Summary: | LVM couldn't handle two or more bootable device | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Zoltan Hoppar <hopparz> |
Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | agk, bmarzins, bmr, dwysocha, heinzm, jonathan, lvm-team, mbroz, msnitzer, prajnoha, prockai |
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: | 2010-06-23 13:19:19 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
Zoltan Hoppar
2010-05-10 13:55:56 UTC
Do volume group names in these installations differ? If not, you need to rename one of them to make them unique (also changing the entry in boot loader's config accordingly). > (also changing the entry in boot loader's config accordingly).
...and entries in /etc/fstab as well.
I have did the changes, and doesn't work. I have met this problem too with F13 beta live, where I couldn't started the live installation, until the internal disk hasn't been removed. I choose the booting device in computer, starts the proper hw, and jumps back to the internal disk. Btw, the device always gets an unique ID, what consists from lot of numbers, however still can't boot. Else if I choose extFS, then I *could* boot differently. With LVM *not*. PS: When I try to show the newest release at booth, this is really blame us. If volume groups name differs, there is no problem from lvm point of view to handle it (I have system with 3 VG, every VG containt roo LV for different system - rawhide,RHEL5, etc... and even using one grub on one boot partition - and it works). If you have two VGs with the same name, but with differnet UUID, lvm allows you to rename (but system will not boot properly - on many places it expect unique VG name.) Hopefully installer now doed not use one common name for all VGs (which implicitly caused this problem.) So if you cannot install _new_ system with different vg_name, it is not lvm problem, but installer one - please report bug to anaconda then. |