Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 84463
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Eric Edgar (RETIRED) <rocket@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Forsman <gentoo@thoth.purplefrog.com>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 84463 depends on: Show dependency tree
Bug 84463 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-03-07 19:29 0000
After I updated my system it no longer booted correctly.

To work around this problem I added 
=sys-fs/lvm2-2.00.33-r1
to /etc/portage/package.mask and re-emerged lvm2 (and got the previous version which doesn't dynamically link against the lib in /usr).

Reproducible: Always
Steps to Reproduce:
1. /usr is an LVM partition
2. emerge lvm2
3. reboot

Actual Results:  
system failed to fsck because the LVM partitions were not active.
The LVM partitions were not active because vgchange was dynamically linked
against something in /usr (I think libgpm)
/usr was unavailable because it was an LVM partition that didn't get fscked or
mounted.

Expected Results:  
boot normally

Portage 2.0.51.19 (default-linux/x86/2004.3, gcc-3.3.5, glibc-2.3.4.20040808-r1,
2.4.28-gentoo-r7 i686)
=================================================================
System uname: 2.4.28-gentoo-r7 i686 AMD Athlon(tm) 64 Processor 3000+
Gentoo Base System version 1.4.16
Python:              dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 23 2005, 16:44:54)]
dev-lang/python:     2.3.4-r1
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4
sys-devel/binutils:  2.15.92.0.2-r1
sys-devel/libtool:   1.5.10-r4
virtual/os-headers:  2.4.22-r1
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=i686 -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env
/usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/bind /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=i686 -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms"
GENTOO_MIRRORS="http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/home/thoth/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow 3dnowex X Xaw3d acl apache2 apm arts avi bash-completion berkdb
bitmap-fonts bonobo bzlib cdr crypt cups curl divx4linux doc dvb dvd dvdr
dvdread emboss encode esd f77 fam font-server foomaticdb gdbm gif gnome gpm gtk
gtk2 gtkhtml guile imlib ipv6 java jpeg junit kde libg++ libwww mad maildir
mikmod mjpegi mmx mng motif mp3 mpeg mysql mythtv ncurses nls nojython oggvorbis
opengl oss pam pcmcia pdflib perl png python qt quicktime readline sdl spell sse
sse2 ssl svg svga tcltk tcpd theora tiff transcode truetype truetype-fonts
type1-fonts unicode v4l vim-with-x wmf xinerama xml xml2 xmms xv xvid zlib"
Unset:  ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS

------- Comment #1 From Eric Edgar (RETIRED) 2005-03-07 20:15:15 0000 -------
please do a ldd /sbin/lvm on the 2.00.33 version.

------- Comment #2 From Eric Edgar (RETIRED) 2005-03-08 06:28:04 0000 -------
there is a new 2.00.33-r2 ebuild that builds statically by default because the
files are in /sbin.  Please let me know if that fixes your issues.

------- Comment #3 From Robert Forsman 2005-03-09 10:30:28 0000 -------
To those who have been bitten by this bug, you can repair your system with a
little work.  This info is distilled from

http://www.gentoo.org/doc/en/lvm2.xml

Boot from a liveCD.  I still had the CD-RW I used to install gentoo in the
first place.  We are not re-installing, just giving ourselves a working copy of
LVM.  Then I activated LVM and mounted my filesystem heirarchy (you will most
likely have to adjust your mount commands since these are for MY system, not
yours) using the following commands:

modprobe dm-mod
vgchange -a y

# adjust these for your system
mount /dev/hda3 /mnt/gentoo
mount /dev/vg0/lv_usr /mnt/gentoo/usr
mount /dev/vg0/lv_var /mnt/gentoo/var
mount /dev/vg0/lv_home /mnt/gentoo/home

chroot /mnt/gentoo

echo =sys-fs/lvm2-2.00.33-r1 >> /etc/portage/package.mask

emerge -pv lvm2
emerge lvm2

ldd /sbin/vgchange

  And make sure it isn't dynamically linked against something in /usr still.
Once the new version of lvm is installed in /mnt/gentoo, you may reboot and
eject the CD, and you should have a bootable system again.

------- Comment #4 From Robert Forsman 2005-03-09 10:40:55 0000 -------
The 2.0.33-r2 ebuild appears to solve my problem.

------- Comment #5 From Eric Edgar (RETIRED) 2005-04-05 13:27:02 0000 -------
newer ebuilds fix this issue

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug