Problem/Failure to install PVE over existing lenny

bhenderson · Sep 30, 2009

I'm pulling my hair out....
I am trying to install pve over an existing lenny (5.03; 2.6.26-2-amd64) installation with no success. I can install lenny without issues and all is well...boots cleanly, no disk issues, etc.... The initial boot messages with the default kernel are:

Code:

  root (hd0,0)
  file system type is ext2fs, partition type 0x83
  kernel          /boot/vmlinuz-2.6.26-2-amd64 root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet
    [Linuz bzimage setup=0x3000 size=0x1a9810]
  initrd /boot/initrd.img-2.6.26-2-amd64
    [Linuz-initrd @ 3787900, 
0x77649f bytes]

and all is well...a nice, stable system.

However, after I install the pve kernel exactly as described in the wiki I get the following boot messages:

Code:

  root (hd0,0)
  file system type is ext2fs, partition type 0x83
  kernel          /boot/vmlinuz-2.6.24-7-pve root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet
    [Linuz bzimage setup=0x2c00 size=0x1ff538]
  initrd /boot/initrd.img-2.6.24-7-pve
    [Linuz initrd @ 372f4000, 0xcfbd20 bytes]
 
Proxmox startup
mounting proc filesystem
pumnting sys filesystem
commandline: root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet
loading filesystem drivers:
/init: line 195: syntax error: oxUUID=3f565b95-c313-402f-8a3f-40629be5f3b2 & 255
Kernel panic - not syncing: Attempted to kill init!

I can boot back to the default lenny kernel without problems?!?
I have re-installed multiple times and get the same results. I have read on other forums of problems booting following kernel upgrades due to differnces in how the kernels assign device names. I tried using UUIDs in /boot/grub/menu.list and fstab to avoid this possibility but that did not help.
The relevant sections of the /boot/grub/menu.list and /etc/fstab are listed below as is output from df -h and mount when booted using the default lenny kernel.

HELP PLEASE!!!
Thanks
bhenderson
----------------------------------------------------------
cat /boot/grub/menu.lst

Code:

# kopt=root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro
...
# groot=(hd0,0)
... 
title           Debian GNU/Linux, kernel 2.6.26-2-amd64
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.26-2-amd64 root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet
initrd          /boot/initrd.img-2.6.26-2-amd64
...
title           Debian GNU/Linux, kernel 2.6.24-7-pve
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.24-7-pve root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet
initrd          /boot/initrd.img-2.6.24-7-pve
...

cat /etc/fstab

Code:

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
UUID=3f565b95-c313-402f-8a3f-40629be5f3b2       /               ext3    errors=remount-ro 0       1
UUID=85e6f35d-0e00-44bd-9796-a80a84e9b2b2 /mnt/backups    ext3    defaults        0       2
UUID=43eb502d-e740-437c-b8e5-7e5f9851382a /mnt/home       reiserfs defaults        0       2
UUID=a69860be-5d97-4b5f-9e9c-40d0830ec322 /mnt/music      reiserfs defaults        0       2
UUID=844e2671-b83e-4e00-ba60-2076681a8fcc /mnt/pictures   reiserfs defaults        0       2
UUID=1a20dad8-0aac-4ba2-b363-d5f3b67f420c /mnt/shared     reiserfs defaults        0       2
UUID=8c74f22d-35a4-477e-8ce9-30d535502ee8 /mnt/videos     xfs     defaults        0       2
UUID=33ee8602-8686-4a15-b8c0-1e2419609e3d /opt            reiserfs defaults        0       2
UUID=ca083848-353e-4662-8150-a09c6507ec48 /srv            reiserfs defaults        0       2
UUID=a380e60f-dc1b-4e03-ba49-f4a93ea572b6 /tmp            ext3    defaults        0       2
UUID=2bb41a50-6673-4f2d-921e-6b7eebe5cf61 /usr            reiserfs defaults        0       2
UUID=87b80e97-a81f-4865-a2d4-b17a12fe1cad /usr/local      reiserfs defaults        0       2
UUID=13fcc8da-db38-43e4-aa7d-38e9668a0593 /var            reiserfs defaults        0       2
UUID=2f3f7cdd-c4e9-408b-afb8-156ae8928f47 /vm/1           reiserfs defaults        0       2
/dev/mapper/sys1-swap none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto     0       0

mount

Code:

/dev/sda1 on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/dm-13 on /mnt/backups type ext3 (rw)
/dev/dm-12 on /mnt/home type reiserfs (rw)
/dev/dm-8 on /mnt/music type reiserfs (rw)
/dev/dm-9 on /mnt/pictures type reiserfs (rw)
/dev/dm-11 on /mnt/shared type reiserfs (rw)
/dev/dm-10 on /mnt/videos type xfs (rw)
/dev/dm-3 on /opt type reiserfs (rw)
/dev/dm-2 on /srv type reiserfs (rw)
/dev/dm-0 on /tmp type ext3 (rw)
/dev/dm-5 on /usr type reiserfs (rw)
/dev/dm-6 on /usr/local type reiserfs (rw)
/dev/dm-4 on /var type reiserfs (rw)
/dev/dm-7 on /vm/1 type reiserfs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)

df -h

Code:

Filesystem            Size  Used Avail Use% Mounted on
/dev/sda1             4.6G  384M  4.0G   9% /
tmpfs                 4.0G     0  4.0G   0% /lib/init/rw
udev                   10M  956K  9.1M  10% /dev
tmpfs                 4.0G     0  4.0G   0% /dev/shm
/dev/dm-13             99G  1.4G   93G   2% /mnt/backups
/dev/dm-12            200G   79G  122G  40% /mnt/home
/dev/dm-8              40G   25G   16G  62% /mnt/music
/dev/dm-9              50G   21G   30G  42% /mnt/pictures
/dev/dm-11             50G   31G   20G  62% /mnt/shared
/dev/dm-10            1.3T  525G  749G  42% /mnt/videos
/dev/dm-3             1.9G   33M  1.9G   2% /opt
/dev/dm-2             1.9G   33M  1.9G   2% /srv
/dev/dm-0             9.2G  150M  8.6G   2% /tmp
/dev/dm-5             9.4G  2.1G  7.3G  22% /usr
/dev/dm-6              19G   33M   19G   1% /usr/local
/dev/dm-4              19G  1.1G   18G   6% /var
/dev/dm-7              94G   33M   94G   1% /vm/1

dietmar · Sep 30, 2009

Our kernel does not support that syntax "root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2".

Use a device name instead.

bhenderson · Sep 30, 2009

Thanks for the suggestion. Unfortunately, device names don't work either. If i change the kernel line in /boot/grub/menu.lst from :

Code:

kernel          /boot/vmlinuz-2.6.24-7-pve root=UUID=3f565b95-c313-402f-8a3f-40629be5f3b2 ro quiet

to

Code:

kernel          /boot/vmlinuz-2.6.24-7-pve root=UUID=/dev/sda1 ro quiet

I get:

Code:

   root (hd0,0)
  file system type is ext2fs, partition type 0x83
  kernel          /boot/vmlinuz-2.6.24-7-pve root=/dev/sda1 ro quiet
    [Linuz bzimage setup=0x2c00 size=0x1ff538]
  initrd /boot/initrd.img-2.6.24-7-pve
    [Linuz initrd @ 372f4000, 0xcfbd20 bytes]
 
Proxmox startup
mounting proc filesystem
pumnting sys filesystem
commandline: root=/dev/sda1 ro quiet
loading filesystem drivers:
mount: mounting /dev/sda1 on /mnt failed: no such device or address
mount: mounting /dev/sda1 on /mnt failed: no such device or address
mount: mounting /dev/sda1 on /mnt failed: no such device or address
testing in 5 seconds
 
(repeat mount attempts 4 more times....)
 
switch_root: bad newroot /mnt
Kernel panic - not syncing: Attempted to kill init!

Just to clarify, I started with device names...not UUIDs. I changed to UUIDs since it appeared that the kernels were either loading drivers or identifying drives differently. Reading other forums I found that there have been changes in how kernels prior to 2.6.26 identified drives and assigned drivers. Using UUIDs was recommended as a means to "future proof" your setup which is why I tried them.

Oh, note that I have previously installed proxmox 1.2 on this very system and it installed and ran fine. This problem has cropped up in my attempts to utilize a custom partition layout.

Suggestions? I'm clueless.

Thanks
bhenderson

bhenderson · Sep 30, 2009

Progress....

After installing the pve kernel I had to update the initramfs image:

Code:

update-initramfs -u -t -k 2.6.24-7-pve

I could then boot into the pve kernel....but my network interfaces were gone...

udev was renaming my interfaces when I booted into the pve kernel:

Code:

Sep 30 08:15:22 pm1 kernel: udev: renamed network interface eth0 to eth3

Examining /etc/udev/rule.d/70-persistent-net.rules revealed differences in the naming between the 2 kernels.

eth0 which was acceptable for 2.6.26-2:

Code:

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:15:8d:e4:2
d", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

eth3 which was inserted by the pve kernel:

Code:

# PCI device 0x11ab:0x4364 (sky2)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:22:15:8d:e4:2
d", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3"

The difference being the ATTR{dev_id}=="0x0" attribute that was not tolerated by the earlier (pve) kernel. Deleting the entry for eth0 then renaming eth3 to eth0 then allowed booting into either kernel with network interfaces coming up correctly in both.

The only thing that I can see now that doesn't work in the pve kernel is sound...not a biggie or high priority but I would like to get it as clean as possible. I'll post back if/when I get it resolved.

You may want to update the HowTo on installing on existing Lenny distributions. There are problems reported all over the net regarding differences in device/driver resolution when up/down-grading between 2.6.24 and 2.6.26 kernels. Just google "2.6.26 Kernel panic - not syncing".

Now on to the next step...
aptitude install proxmox-ve
bhenderson

dietmar · Sep 30, 2009

bhenderson said:
Code:

kernel /boot/vmlinuz-2.6.26-2-amd64 root=UUID=/dev/sda1 ro quiet

try

Code:

kernel          /boot/vmlinuz-2.6.26-2-amd64 root=/dev/sda1 ro quiet

dietmar · Sep 30, 2009

bhenderson said:
Progress....

After installing the pve kernel I had to update the initramfs image:

Code:

update-initramfs -u -t -k 2.6.24-7-pve

I could then boot into the pve kernel....but my network interfaces were gone...

Please do not run update-initramfs.

bhenderson · Sep 30, 2009

oops, that was typo.

I did not have root=UUID=/dev/sda1. It was in fact root=/dev/sda1. The boot messages below that entry are correct and point to root=/dev/sda1.

other suggestions?

And what would be your recommended path to restoring the "official" pve image?

Thanks,
bhenderson

dietmar · Sep 30, 2009

What kind of disk is that (ide, sata,scsi, what driver) ?

bhenderson · Sep 30, 2009

It is a SATA II drive on an ICH10 controller. I'm having trouble finding an explicit "driver=???" statement anywhere but combing through the logs and the output beliw it looks like ahci is loading for the controller and sd_mod is loading for the disk.

Thanks
bhenderson

dmesg | grep -i -e ata -e disk -e scsi -e ahci

Code:

SCSI subsystem initialized
libata version 3.00 loaded.
ahci 0000:00:1f.2: version 3.0
ahci 0000:00:1f.2: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3f impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq sntf stag pm led clo pmp pio slum part
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
scsi4 : ahci
scsi5 : ahci
ata1: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffe900 irq 2298
ata2: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffe980 irq 2298
ata3: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffea00 irq 2298
ata4: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffea80 irq 2298
ata5: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffeb00 irq 2298
ata6: SATA max UDMA/133 abar m2048@0xf9ffe800 port 0xf9ffeb80 irq 2298
ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata1.00: ATA-8: ST3500320AS, SD15, max UDMA/133
ata1.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata1.00: configured for UDMA/133
ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata2.00: ATA-8: ST3500320AS, SD15, max UDMA/133
ata2.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ATA-8: ST31000340AS, SD15, max UDMA/133
ata3.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: configured for UDMA/133
ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata4.00: ATA-8: ST31000340AS, SD15, max UDMA/133
ata4.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata5.00: ATA-8: ST31000340AS, SD15, max UDMA/133
ata5.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata5.00: configured for UDMA/133
ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata6.00: ATA-8: ST31000333AS, CC1F, max UDMA/133
ata6.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata6.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST3500320AS      SD15 PQ: 0 ANSI: 5
scsi 1:0:0:0: Direct-Access     ATA      ST3500320AS      SD15 PQ: 0 ANSI: 5
scsi 2:0:0:0: Direct-Access     ATA      ST31000340AS     SD15 PQ: 0 ANSI: 5
scsi 3:0:0:0: Direct-Access     ATA      ST31000340AS     SD15 PQ: 0 ANSI: 5
scsi 4:0:0:0: Direct-Access     ATA      ST31000340AS     SD15 PQ: 0 ANSI: 5
scsi 5:0:0:0: Direct-Access     ATA      ST31000333AS     CC1F PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] Attached SCSI disk
sd 1:0:0:0: [sdb] Attached SCSI disk
scsi6 : pata_marvell
scsi7 : pata_marvell
ata7: PATA max UDMA/100 cmd 0xdc00 ctl 0xd880 bmdma 0xd400 irq 16
ata8: PATA max UDMA/133 cmd 0xd800 ctl 0xd480 bmdma 0xd408 irq 16
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 3:0:0:0: [sdd] Attached SCSI disk
sd 4:0:0:0: [sde] Attached SCSI disk
sd 5:0:0:0: [sdf] Attached SCSI disk
ata7.00: ATAPI: Optiarc DVD RW AD-7190A, 1.03, max UDMA/66
ata7.00: configured for UDMA/66
ata8.00: ATA-7: DriveXpert HDD0, 1.2569, max UDMA/133
ata8.00: 1250284896 sectors, multi 1: LBA48 NCQ (depth 0/32)
ata8.00: configured for UDMA/133
scsi 6:0:0:0: CD-ROM            Optiarc  DVD RW AD-7190A  1.03 PQ: 0 ANSI: 5
scsi 7:0:0:0: Direct-Access     ATA      DriveXpert HDD0  1.25 PQ: 0 ANSI: 5
sd 7:0:0:0: [sdg] Attached SCSI disk
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
sr 6:0:0:0: Attached scsi CD-ROM sr0
sd 0:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: Attached scsi generic sg2 type 0
sd 3:0:0:0: Attached scsi generic sg3 type 0
sd 4:0:0:0: Attached scsi generic sg4 type 0
sd 5:0:0:0: Attached scsi generic sg5 type 0
sr 6:0:0:0: Attached scsi generic sg6 type 5
sd 7:0:0:0: Attached scsi generic sg7 type 0

lsmod | grep -i -e ata -e disk -e scsi -e ahci

Code:

pata_marvell           16640  0
ata_generic            17156  0
ahci                   40964  7
pata_acpi              17152  0
libata                189616  4 pata_marvell,ata_generic,ahci,pata_acpi
scsi_mod              188984  5 sbp2,sg,sr_mod,sd_mod,libata

lspci>

Code:

00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1
00:1c.4 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 5
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 SATA controller: Intel Corporation 82801JI (ICH10 Family) SATA AHCI Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
03:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6121 SATA II Controller (rev b1)

lshw -c storage

Code:

        *-storage
             description: SATA controller
             product: 82801JI (ICH10 Family) SATA AHCI Controller
             vendor: Intel Corporation
             physical id: 1f.2
             bus info: pci@0000:00:1f.2
             logical name: scsi0
             logical name: scsi1
             logical name: scsi2
             logical name: scsi3
             logical name: scsi4
             logical name: scsi5
             version: 00
             width: 32 bits
             clock: 66MHz
             capabilities: storage msi pm ahci_1.0 bus_master cap_list emulated
             configuration: driver=ahci latency=0 module=ahci
           *-disk:0
                description: ATA Disk
                product: ST3500320AS
                vendor: Seagate
                physical id: 0
                bus info: scsi@0:0.0.0
                logical name: /dev/sda
                version: SD15
                serial: 9QM5HS15
                size: 465GiB (500GB)
                capabilities: partitioned partitioned:dos
                configuration: ansiversion=5 signature=e08d5c8f
              *-volume:0
                   description: EXT3 volume
                   vendor: Linux
                   physical id: 1
                   bus info: scsi@0:0.0.0,1
                   logical name: /dev/sda1
                   logical name: /
                   version: 1.0
                   serial: 3f565b95-c313-402f-8a3f-40629be5f3b2
                   size: 4769MiB
                   capacity: 4769MiB
                   capabilities: primary bootable journaled extended_attributes
large_files huge_files recover ext3 ext2 initialized
                   configuration: created=2009-09-29 17:28:46 filesystem=ext3 la
bel=root modified=2009-09-30 10:34:06 mount.fstype=ext3 mount.options=rw,relatim
e,errors=remount-ro,data=ordered mounted=2009-09-30 10:34:06 state=mounted

dietmar · Sep 30, 2009

ICH10 should be supported by our latest kernel in V1.4beta2 - Please can you test that?

bhenderson · Oct 1, 2009

I installed 1.4beta. When I booted into the new kernel it was not able to locate the root partition....just like I experienced with 2.6.247-pve

Code:

   root (hd0,0)
  file system type is ext2fs, partition type 0x83
  kernel          /boot/vmlinuz-2.6.24-8-pve root=/dev/sda1 ro quiet
    [Linuz bzimage setup=0x2c00 size=0x1ff538]
  initrd /boot/initrd.img-2.6.24-7-pve
    [Linuz initrd @ 372f4000, 0xcfbd20 bytes]

Proxmox startup
mounting proc filesystem
pumnting sys filesystem
commandline: root=/dev/sda1 ro quiet
loading filesystem drivers:
mount: mounting /dev/sda1 on /mnt failed: no such device or address
mount: mounting /dev/sda1 on /mnt failed: no such device or address
mount: mounting /dev/sda1 on /mnt failed: no such device or address
testing in 5 seconds

(repeat mount attempts 4 more times....)

switch_root: bad newroot /mnt
Kernel panic - not syncing: Attempted to kill init!

I'm currently booting into 2.6.24-7-pve (with the updated image as described previously) running 1/4beta....

So if the new kerel supports ICH10 it would seem that is not the issue.

I should point out that parts of this system (not the OS, which is installed on the first sata drive, /dev/sda1) are running as software raids. Some of those logical volumes are mounted in /mnt. I point this out since the kernels appear to be confusing /dev/sda1 and /mnt???

Ideas?

Thanks

bhenderson

Search

Search

Problem/Failure to install PVE over existing lenny

bhenderson

New Member

dietmar

Proxmox Staff Member

bhenderson

New Member

bhenderson

New Member

dietmar

Proxmox Staff Member

dietmar

Proxmox Staff Member

bhenderson

New Member

dietmar

Proxmox Staff Member

bhenderson

New Member

dietmar

Proxmox Staff Member

bhenderson

New Member

We value your privacy