| View previous topic :: View next topic |
| Author |
Message |
Riftwing Apprentice


Joined: 06 Oct 2002 Posts: 293
|
Posted: Thu Apr 20, 2006 4:28 am Post subject: Upgrade to LVM2-2.02.03 borked my system. |
|
|
After upgrading to the above lvm2 version, I can no longer activate my lvm volume. When I attempt to do so I am greeted with several errors saying
"Volume group for uuid not found: blah blah blah(guessing this is a uuid, but it doesn't match any of my logical volume uuid numbers)"
After booting up on a livecd with an older version of lvm2, I was able to activate my lvm volume once again. Any ideas on what changed to cause this? _________________ Good, bad, I'm the guy with the gun. - Ash, Army of Darkness |
|
| Back to top |
|
 |
trad511 n00b

Joined: 29 Nov 2003 Posts: 27
|
Posted: Thu Apr 20, 2006 4:41 am Post subject: |
|
|
Same exact problem, but no reason that I can see. Thanks for the livecd tip and I'll let you know if I figure anything out. _________________ Success is the ability to go from one failure to another with no loss of enthusiasm. - Winston Churchill |
|
| Back to top |
|
 |
asiobob Veteran


Joined: 29 Oct 2003 Posts: 1375 Location: Bamboo Creek
|
|
| Back to top |
|
 |
GoingDown Tux's lil' helper

Joined: 13 Jan 2004 Posts: 117 Location: Finland
|
Posted: Thu Apr 20, 2006 8:37 am Post subject: |
|
|
Yeah, mee too
My fix:
I booted with gentoo 2006.0 install cd, mounted disks and chrooted, masked lvm2-2.02.03 and downgraded to lvm2-2.01.14 (btw, I needed to modify 2.01.14 ebuild to get it working...)
lvm2-2.02.03 mask:
| Code: |
echo "=sys-fs/lvm2-2.02.03" >>/etc/portage/package.mask
|
Then, emerge -auDv world shows lvm2 and device-mapper downgrades. Unfortunately emerging lvm2-01.14 didn't work, it tries to use lvm2-2.01.14-static.patch which seems not to be in portage tree.
So, I just removed line
| Code: |
epatch ${FILESDIR}/lvm2-2.01.14-static.patch
|
from /usr/portage/sys-fs/lvm2/lvm2-2.01.14.ebuild, and ran
[code]
ebuild lvm2-2.01.14.ebuild digest
[code]
After that, emerge was succesfull, and downgraded device-mapper and lvm2.
Note that you really SHOULD put your modified lvm2-2.01.14.ebuild to your overlay dir with all files to prevent its overwrite by emerge --sync. |
|
| Back to top |
|
 |
cheatah n00b

Joined: 19 Oct 2004 Posts: 21
|
Posted: Fri Apr 21, 2006 3:59 am Post subject: |
|
|
| Upgraded to lvm2-2.02.04 and it borked my system today. Had to boot off livecd masked lvm2-2.02.03 and above and downgraded to lvm2-2.02.02-r1. |
|
| Back to top |
|
 |
nbensa l33t


Joined: 10 Jul 2002 Posts: 799 Location: Buenos Aires, Argentina
|
|
| Back to top |
|
 |
GoingDown Tux's lil' helper

Joined: 13 Jan 2004 Posts: 117 Location: Finland
|
Posted: Fri Apr 21, 2006 8:58 am Post subject: |
|
|
This bug report describes just same situation I had. And yes, I did try with vgcfgrestore, but it didn't work.
Now I see that there is new versions of lvm2 and device-mapper available, I will try those.
EDIT:
OK, I upgraded to lvm2 2.02.04, and without reboot ran pvscan, vgscan and lvscan. Here is error I got:
| Code: |
WARNING: Duplicate VG name vg: Existing wo9kdJ-0FMp-WtFa-zdlD-ofcT-WNi0-CWgpjb (created here) takes precedence over wo9kdJ-0FMp-WtFa-zdlD-ofcT-WNi0-CWgpjb
|
Gee, I don't want to reboot at all, I bet lvm2 volumes won't come up - so downgrade it is. This time, portage wanted to downgrade to 2.02.02-r1 instead of 2.01.14, maybe because of device-mapper upgrade? |
|
| Back to top |
|
 |
Thames n00b


Joined: 25 Feb 2003 Posts: 53
|
Posted: Fri Apr 21, 2006 11:23 am Post subject: |
|
|
| GoingDown wrote: | | This time, portage wanted to downgrade to 2.02.02-r1 instead of 2.01.14, maybe because of device-mapper upgrade? |
No, because 2.02.02 was put back into portage because someone (don't want to point fingers) figured out that that would be a nice thing to do if the newer versions breaked anything (which they did).
EDIT:
I can see that someone on the lvm mailinglist is having the same problem as we have (https://www.redhat.com/archives/linux-lvm/2006-April/msg00084.html), and a fix has been commited to lvm CVS. So that probably means that the fix is in the next release of lvm, so one should just stay away from 2.02.{03,04} and when 2.02.05 comes out we are back on track.
Someone could probably extract the commited fix from lvm CVS and post a bug report and have the maintainer of lvm2 patch the .04 versions until .05 is out. |
|
| Back to top |
|
 |
rocketman110 Retired Dev

Joined: 19 Oct 2004 Posts: 2
|
Posted: Fri Apr 21, 2006 6:29 pm Post subject: |
|
|
| lvm2-2.02.04-r1 is in the tree and should resolve this issue. The upstream patch is included in this ebuild. |
|
| Back to top |
|
 |
cheatah n00b

Joined: 19 Oct 2004 Posts: 21
|
Posted: Fri Apr 21, 2006 7:29 pm Post subject: |
|
|
| it seems lvm2-2.02.03 and lvm2-2.02.04 have been removed from portage |
|
| Back to top |
|
 |
rocketman110 Retired Dev

Joined: 19 Oct 2004 Posts: 2
|
Posted: Fri Apr 21, 2006 7:46 pm Post subject: |
|
|
| they have been removed because they are broken. 2.02.04-r1 should work for you. |
|
| Back to top |
|
 |
trad511 n00b

Joined: 29 Nov 2003 Posts: 27
|
Posted: Sat Apr 22, 2006 1:50 am Post subject: |
|
|
sys-fs/device-mapper-1.02.05
sys-fs/lvm2-2.02.04-r1
Works for me! Thank you. _________________ Success is the ability to go from one failure to another with no loss of enthusiasm. - Winston Churchill |
|
| Back to top |
|
 |
satanskin Guru

Joined: 25 Apr 2005 Posts: 353
|
Posted: Sat Apr 22, 2006 3:43 am Post subject: |
|
|
| How were you all able to chroot into your system? Could someone please post some instructions? Especially pertaining to lvm and raid setup in the livecd. I have my LVM2 volume group running on top of a software raid0. Neither the raid nodes or the vg show up under the livecd. I'm trying with the 2005.1 cd using dolvm2 dmraid. Could someone help me get those setup so that I could chroot into it and downgrade please? Thanks a lot! |
|
| Back to top |
|
 |
GoingDown Tux's lil' helper

Joined: 13 Jan 2004 Posts: 117 Location: Finland
|
Posted: Sat Apr 22, 2006 5:44 am Post subject: |
|
|
| Quote: | | How were you all able to chroot into your system? Could someone please post some instructions? Especially pertaining to lvm and raid setup in the livecd. I have my LVM2 volume group running on top of a software raid0. |
Ok, this is little bit tricky. When booting with livecd, you must first activate your raid:
1. create /etc/raidtab to match your existing raid settings
2. modprobe md
3. activate your raid (using mkraid?). Not sure of this,
see http://gentoo-wiki.com/HOWTO_Gentoo_Install_on_Software_RAID for more info
After raid is running, you should be able to run pvscan, vgscan, lvscan and see your lvm2 volumes.
Activate your lvm by running lvchange -ya |
|
| Back to top |
|
 |
satanskin Guru

Joined: 25 Apr 2005 Posts: 353
|
Posted: Sat Apr 22, 2006 5:51 am Post subject: |
|
|
Ok, well i've made some progress. I'm booting off of the RR64 livecd since i needed reiser4 support. Anyway, i have my raid setup/activated as well as my vg active and mounted. My only problem now is that when i try to chroot i get an error about my kernel being too old.....WTF!?!?!? My normal system runs a 2.6.16 based kernel!! how is that too old!? Anyway around this?
| Quote: | rr64dvd gentoo # chroot ./ /bin/bash
FATAL: kernel too old
|
|
|
| Back to top |
|
 |
satanskin Guru

Joined: 25 Apr 2005 Posts: 353
|
Posted: Sun Apr 23, 2006 7:46 am Post subject: |
|
|
| Anyone have any ideas on the Kernel Too old error? What the hell does that mean in this situation and how can i fix/get around it? Please help. |
|
| Back to top |
|
 |
smerrima n00b

Joined: 16 Mar 2004 Posts: 47 Location: Boise, ID
|
Posted: Mon Apr 24, 2006 3:56 am Post subject: /usr is an lvm partition |
|
|
So I have /usr as an lvm partition. So when I chroot into my environment I cannot access 'emerge' to change me lvm partition. Can anyone think of a way around this?
Thanks! _________________ -Seth |
|
| Back to top |
|
 |
GoingDown Tux's lil' helper

Joined: 13 Jan 2004 Posts: 117 Location: Finland
|
Posted: Mon Apr 24, 2006 4:51 am Post subject: |
|
|
Smerrima: Are you booting with livecd? If so, then you must activate your lvm volumes (lvchange -ay) and then mount all partitions before chroot. And then you can emerge.
Satanskin: Is it somehow saying that your kernel you are running (RR64) is too old compared to one you have on your hard disk? Can you boot with different one? |
|
| Back to top |
|
 |
cstiehl n00b

Joined: 07 Mar 2004 Posts: 12 Location: Pgh, PA
|
Posted: Sat Apr 29, 2006 12:43 pm Post subject: |
|
|
I had similar prob a while back, see below.
This thread saved my life. It pointed out the problem although I figured out a different way to resolve.
http://andy.boyko.net/2005/03/21/lvm2-the-devil-and-your-partition-table/
My solution:
| Code: |
I added the following to /etc/lvm/lvm.conf:
types = [ "ide", 1 ]
# Advanced settings.
# List of pairs of additional acceptable block device types found
# in /proc/devices with maximum (non-zero) number of partitions.
# types = [ "fd", 16 ]
types = [ "ide", 1 ]
|
My problem:
| Code: |
BEFORE UPGRADE:
mythback root # lvmdiskscan
/dev/hda [ 74.54 GB]
/dev/hde [ 372.61 GB] LVM physical volume
/dev/hdg [ 186.31 GB] LVM physical volume
/dev/hda1 [ 39.19 MB]
/dev/hde1 [ 372.61 GB]
/dev/hdg1 [ 186.31 GB]
/dev/hda2 [ 964.84 MB]
/dev/hda3 [ 73.55 GB]
/dev/hdh [ 189.92 GB] LVM physical volume
/dev/hdh1 [ 189.92 GB]
1 disk
6 partitions
3 LVM physical volume whole disks
0 LVM physical volumes
mythback root #
mythback myth # emerge lvm2 --ask
These are the packages that I would merge, in order:
Calculating dependencies ...done!
[ebuild U ] sys-fs/lvm2-2.01.09 [2.00.08]
Do you want me to merge these packages? [Yes/No]
AFTER UPGRADE:
mythback root # pvdisplay
mythback root # vgdisplay
No volume groups found
mythback root # lvdisplay
No volume groups found
mythback root # lvmdiskscan
/dev/hda1 [ 39.19 MB]
/dev/hde1 [ 372.61 GB]
/dev/hdg1 [ 186.31 GB]
/dev/hda2 [ 964.84 MB]
/dev/hda3 [ 73.55 GB]
/dev/hdh1 [ 189.92 GB]
0 disks
6 partitions
0 LVM physical volume whole disks
0 LVM physical volumes
mythback root #
|
|
|
| Back to top |
|
 |
|