Upgrade to 1.6 and new Kernel - Server can't find volumes

H

hec

Renowned Member
Jan 8, 2009
278
18
83
Wien
www.vector-its.at
After i upgraded to 1.6 and to the kernel version 2.6.32-3 one of my server will not boot

With the old 2.6.24 kernel i can boot without any problems

At the boot i see the message that there are no volumes found.

lspci:
Code: 
00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1)
00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1)
00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1)
00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1)
00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 (rev b1)
00:06.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 (rev b1)
00:07.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 (rev b1)
00:08.0 System peripheral: Intel Corporation 5000 Series Chipset DMA Engine (rev b1)
00:10.0 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.1 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:10.2 Host bridge: Intel Corporation 5000 Series Chipset FSB Registers (rev b1)
00:11.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:13.0 Host bridge: Intel Corporation 5000 Series Chipset Reserved Registers (rev b1)
00:15.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:16.0 Host bridge: Intel Corporation 5000 Series Chipset FBD Registers (rev b1)
00:1c.0 PCI bridge: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 (rev 09)
00:1d.0 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 (rev 09)
00:1d.1 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 (rev 09)
00:1d.2 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 (rev 09)
00:1d.3 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 (rev 09)
00:1d.7 USB Controller: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller (rev 09)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d9)
00:1f.0 ISA bridge: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller (rev 09)
00:1f.1 IDE interface: Intel Corporation 631xESB/632xESB IDE Controller (rev 09)
00:1f.2 IDE interface: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller (rev 09)
00:1f.3 SMBus: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller (rev 09)
01:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port (rev 01)
01:00.3 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge (rev 01)
02:00.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 (rev 01)
02:01.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 (rev 01)
02:02.0 PCI bridge: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E3 (rev 01)
05:00.0 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
05:00.1 Ethernet controller: Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper) (rev 01)
06:01.0 Ethernet controller: Intel Corporation 82545GM Gigabit Ethernet Controller (rev 04)
06:02.0 PCI bridge: IBM PCI-X to PCI-X Bridge (rev 02)
07:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID (rev 02)
09:00.0 RAID bus controller: Adaptec AAC-RAID (rev 09)
0e:0c.0 VGA compatible controller: ATI Technologies Inc ES1000 (rev 02)
pveversion -v
Code: 
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.24-12-pve
proxmox-ve-2.6.32: 1.6-13
pve-kernel-2.6.32-3-pve: 2.6.32-13
pve-kernel-2.6.24-5-pve: 2.6.24-6
pve-kernel-2.6.24-11-pve: 2.6.24-23
pve-kernel-2.6.24-1-pve: 2.6.24-4
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-12-pve: 2.6.24-24
pve-kernel-2.6.24-2-pve: 2.6.24-5
qemu-server: 1.1-18
pve-firmware: 1.0-7
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
ksm-control-daemon: 1.0-4
I don't know where i should search at first.

Has anybody an idea how to solve this problem?
 
post the relevant part of /boot/grub/menu.lst

can you provide a screenshot/foto of the error?
 
/boot/grub/menu.lst
Code: 
title           Proxmox Virtual Environment, kernel 2.6.32-3-pve
root            (hd0,0)
kernel          /vmlinuz-2.6.32-3-pve root=/dev/mapper/pve-root ro
initrd          /initrd.img-2.6.32-3-pve

title           Proxmox Virtual Environment, kernel 2.6.24-12-pve
root            (hd0,0)
kernel          /vmlinuz-2.6.24-12-pve root=/dev/mapper/pve-root ro
initrd          /initrd.img-2.6.24-12-pve

so i think this thould be ok

With i screenshot i have my problems but i could try to make a photo of the screen.
 
post /etc/fstab
 
/etc/fstab

Code: 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
/dev/sda1 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
/dev/sdb5       /backup ext3    defaults 0      1
proc /proc proc defaults 0 0
The next is the reboot of the Server an going to the control montior for a photo.
 
Last edited:
maybe sda and sdb get reordered? newer installations uses the UUID to address the boot partition to prevent such issues, see this example:

Code: 
cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=700591fd-1b6a-4743-b167-bc5536de1cf7 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0

try changing your fstab before reboot into the 2.6.32er kernel.
 
Please try to find out why th LVM device /dev/mapper/root is not available (pvs, vgs, lvs, ...)
 
in the initramfs envirenment i cant get infos with this commands because the commands are not available (booting the 2.6.32 kernel)

in 2.6.24 i get the following informations:

pvs:
Code: 
  PV         VG   Fmt  Attr PSize PFree
  /dev/sda2  pve  lvm2 a-   1.82T 4.00G
vgs:
Code: 
  VG   #PV #LV #SN Attr   VSize VFree
  pve    1   3   0 wz--n- 1.82T 4.00G
lvs:
Code: 
  LV   VG   Attr   LSize  Origin Snap%  Move Log Copy%  Convert
  data pve  -wi-ao  1.72T                                      
  root pve  -wi-ao 96.00G                                      
  swap pve  -wi-ao  4.00G
What do you think about taking the other raid controller out and trying to boot?
 
Last edited:
I am having the same problem. I just upgraded from 1.5 to 1.6 and I get the "/dev/mapper/pve-root does not exist" error on boot up. I ran the lvm command at the (initramfs) prompt and then ran lvscan. It couldn't find any lvm's. Then I ran vgscan and it found my volume groups. After that I ran lvscan again, and it found my logical volumes. I still don't know how to get it to boot at this point though.

Does anyone have any advice to offer?

Julian
 
Do you also have more than one raid controller?

I don't understand why i get this problem only on one server.
The other servers work fine with the update.
 
Yes, I do have more than one RAID controller. I have and Intel SCSI controller with a mirror for the boot drive and then I have an LSI MegaRaid controller witha Raid5 on it for the VM's. I have had a problem in the past where the BIOS was set to boot the Intel controller but once the Kernel loaded and looked at the drives, it would designate the Intel drive as sdd instead of sda. When I upgraded to 2.6.24, the mapping changed and the Intel went to sda and I had to change my /etc/fstab in order to get it to boot.

Does anyone know if you can boot a ProxMox system off the install CD? I am going to make an attempt at that next.
 
ok this sounds that we have the same scsi controller ;)

I use the SCSI controller only for my backups and the adaptec for proxmox

I think a reinstall of proxmox would work but it is a lot of work and time to recover all my vms.

I also want to know why this happened and how to fix the problem.

A fried hast the same sata controller and is trying to update from 2.6.24 to 2.6.32. Maybe he has with a single controller the same problem. If not we know where to search.
 
Well, I got mine back up and running by downgrading to the 2.6.24 kernel. Here is what I did...

Boot up using a Debian Lenny network install CD

Select Advanced > Rescue mode at the boot prompt

The system will guide you and request that you set up networking (Do this)

When prompted, select to use a shell within the root partition (pve-root)

Once in the shell, you will have to mount your /boot partition under /boot
Mine was /dev/sdd1 (mount /dev/sdd1 /boot)

Finally I ran "aptitude update" and then "Aptitude install proxmox-ve-2.6.24"

Exit from the shell and reboot.

That is what worked for me :)
 
i think the easier way is to boot in the 2.6.24er kernel and comment out the menu item in the grub config

but this is in my eyes not to solve the problem

with this workaround you only can reboot the server without a user input the problem is not solved

a fried has the sama sas controller and this server booted without problems so i think this problem only occurs with more than one raid controller
 
When I upgraded to the 2.6.32 kernel it uninstalled the 2.6.24 so I had no other kernel to choose at boot.

I removed the LSI MegaRaid card and booted with only the Intel SCSI Raid card and it still didn't work;

so I don't know what that means about the two controller theory because the controller was still present when the initrd was configured.

Also I am running a SuperMicro X8SAX mainboard in case anyone else with this problem is also.
 
julianweber said:
When I upgraded to the 2.6.32 kernel it uninstalled the 2.6.24 so I had no other kernel to choose at boot.

I removed the LSI MegaRaid card and booted with only the Intel SCSI Raid card and it still didn't work;

so I don't know what that means about the two controller theory because the controller was still present when the initrd was configured.

Also I am running a SuperMicro X8SAX mainboard in case anyone else with this problem is also.
Click to expand...

What version do you use exactly? (pveversion -v). You should have:

pve-firmware: 1.0-7
pve-kernel-2.6.32-3-pve: 2.6.32-13
 
What version do you use exactly? (pveversion -v). You should have:
Click to expand...

proxmox:~# pveversion -v
pve-manager: 1.6-2 (pve-manager/1.6/5087)
running kernel: 2.6.24-12-pve
proxmox-ve-2.6.24: 1.5-24
pve-kernel-2.6.24-12-pve: 2.6.24-24
qemu-server: 1.1-18
pve-firmware: 1.0-7
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-7
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.5-1
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back