PVE 3.3 does not boot with kernel 3.10.0-4

mmm

New Member
Oct 16, 2014
3
0
1
Hi,
I have done a fresh installation of PVE 3.3 and without changing the kernel everything works.
However when I try to boot with kernel 3.10.0-4 the system does not boot properly showing these errors:
Code:
Volume group "pve" not found
Skipping volume group pve
Unable to find LVM volume pve/root

...

ALERT! /dev/mapper/pve-root does not exist. Dropping to a shell!

and

Code:
ls /dev/mapper
shows only one element: control

In order to install the new kernel I tried two ways:
1. using the pve-kernel-3.10.0-4-pve_3.10.0-17_amd64.deb from the ISO's dists folder
2. by loading the same file with wget http://download.proxmox.com/debian/...4/pve-kernel-3.10.0-4-pve_3.10.0-17_amd64.deb
and dpkg -i <file> in either case

I'm trying to switch to the new kernel in order to use PCIe passthrough.

Just in case it could matter for the SATA controller - the motherboard is a ASUS Z9PE-D8 WS and I've tried plugging the HDD in to the SATA connectors of the Marvel chipset and using the SATA connectors of the PCH - same result either way.


Does anyone know why this is happening and what I can do about it?




=============EDIT===============
So I got it working thanks to this thread: http://forum.proxmox.com/threads/17306-New-3-10-0-Kernel

But to make it clear for anyone else having the same problem, this is what worked for me:
1. When the emergency consoles is active after the error above, the boot proceduce can be finished successfully using the command
Code:
[COLOR=#333333]lvm vgchange -a y[/COLOR]
followed by CTRL+D. Alternatively rebooting with the old kernel should work the same to get the terminal ready for (2.)

2. in /etc/default/grub changing it to
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=10"
followed by issuing the command
Code:
update-grub
gives the system enough time to find the device when booting.



"scsi_mod.scan=sync" did not work for me as (like the name implies) this only seems to be meant for SCSI/SAS (+raid).
 
Last edited:
So I got it working thanks to this thread: http://forum.proxmox.com/threads/17306-New-3-10-0-Kernel

But to make it clear for anyone else having the same problem, this is what worked for me:
1. When the emergency consoles is active after the error above, the boot proceduce can be finished successfully using the command
Code:
[COLOR=#333333]lvm vgchange -a y[/COLOR]
followed by CTRL+D. Alternatively rebooting with the old kernel should work the same to get the terminal ready for (2.)

2. in /etc/default/grub changing it to
Code:
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=10"
followed by issuing the command
Code:
update-grub
gives the system enough time to find the device when booting.



"scsi_mod.scan=sync" did not work for me (Although others noted it helped on their SAS raid, so it's not SCSI exclusive, it seems).
 
Hello,

I have the same issue "Volume group "pve" not found" on a new proxmox 4.0 beta installation on an Dell R200
after I have 3,5" SATA hard drives with 2,5" 10K.6 SAS hdd's replaced
Is it possible that the hard drives are too fast for the recognition of the LVM volume?
Maybe if the rest of the system (=> CPU) is not in accordance fast?

For my system rootdelay=5 was enough

pveversion -v
proxmox-ve: 4.0-7 (running kernel: 4.1.3-1-pve)
pve-manager: 4.0-26 (running version: 4.0-26/5d4a615b)
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
lvm2: 2.02.116-pve1
corosync-pve: 2.3.4-2
libqb0: 0.17.1-3
pve-cluster: 4.0-14
qemu-server: 4.0-15
pve-firmware: 1.1-6
libpve-common-perl: 4.0-14
libpve-access-control: 4.0-6
libpve-storage-perl: 4.0-13
pve-libspice-server1: 0.12.5-1
vncterm: 1.2-1
pve-qemu-kvm: 2.4-1
pve-container: 0.9-7
pve-firewall: 2.0-6
pve-ha-manager: 1.0-4
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2
lxc-pve: 1.1.2-4
lxcfs: 0.9-pve2
cgmanager: 0.37-pve2