[PVE-User] WG: Strange LVM problem
elacunza at binovo.es
Fri Mar 30 18:23:42 CEST 2012
I just modified the devices section in the lvm.conf of the initrd. I
suggest you check that /etc/lvm.conf is the same in both initrd's.
El vie, 30-03-2012 a las 17:44 +0200, Vincendon Bruno escribió:
> it seems I have the same kind of problem; what did you change in your lvm.conf ?
> I made a squeeze install:
> ( http://pve.proxmox.com/wiki/Install_Proxmox_VE_on_Debian_Squeeze ) because
> since the upgrade to RC1 I can't boot on pve-kernel-2.6.32-10-pve (grub is OK
> but boot locks on the access of pve VG).
> I did try an install with the ISO RC1 : same problem
> I did try an install with the new ISO (2.0 stable): same problem.
> If I boot with the squeeze kernel, everything is OK...
> I have :
> dpkg -l | grep lvm
> ii lvm2 2.02.88-2pve2 Linux
> Logical Volume Manager
> And the 2 kernels (squeeze and pve) :
> ls -alt /boot
> total 32004
> drwxr-xr-x 3 root root 7168 30 mars 17:27 grub
> drwxr-xr-x 4 root root 1024 30 mars 17:27 .
> -rw-r--r-- 1 root root 11566355 30 mars 17:27 initrd.img-2.6.32-10-pve
> -rw-r--r-- 1 root root 10335195 30 mars 16:50 initrd.img-2.6.32-5-amd64
> The machine is an HP Z800 with an LSILOGIC MPT SAS BIOS C1068E SAS 1068E with 2
> 300G sas disk in physical raid 1.
> It was OK with the first release of Proxmox 2 (december).
> Any idea ?
> Thank you
> Le 06/03/2012 18:45, Eneko Lacunza a écrit :
> > Hi,
> > For the record,
> > Problem was that lvm.conf in the initrd for 2.6.35 kernel was not
> > up-to-date; was filtering a partition member of the volume group "pve",
> > and this made lvm unable to use pve VG.
> > Thanks to all
> > Eneko
Zuzendari Teknikoa / Director Técnico
Binovo IT Human Project, S.L.
Astigarraga bidea 2, planta 6 dcha., ofi. 3-2; 20180 Oiartzun (Gipuzkoa)
More information about the pve-user