Hello,
i did a clean install of proxmox following the wiki to 3.1, everthing worked.
After upgrading to 3.3-5 i can not boot onto the pve kernel anymore.
By chainloading into grub2 the following is shown on the terminal and it freezes.
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/grub/core.img
[Multiboot-kludge, loadaddr=0x100000, text-and-data=0x6585, bss=0x0, entry=0
x100950]
ÿLoading, please wait...
do_IRQ: 3.240 No irq handler for vector (irq -1)
do_IRQ: 2.240 No irq handler for vector (irq -1)
do_IRQ: 1.240 No irq handler for vector (irq -1)
do_IRQ: 0.240 No irq handler for vector (irq -1)
When i manually selec kernel 2.6.32-26-pve from grubs menu it freezses after a while again saying:
Initalizing network drop monitor service
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper veid: 0 Not tainted 2.6.32-26-pve #1
Call Trace:
[<ffffffff81537aa0>] ? panic+0xa7/0x167
[<ffffffff81c35202>] ? mount_block_root+0x1ce/0x27f
[<ffffffff81002930>] ? name_to_dev_t+0x750/0xe20
[<ffffffff81c3544c>] ? mount_root+0x57/0x5b
[<ffffffff81c355bd>] ? prepare_namespace+0x16d/0x1a6
[<ffffffff81c34f70>] ? kernel_init+0x28e/0x293
[<ffffffff8100c22a>] ? child_rip+0xa/0x20
[<ffffffff81c34ce2>] ? kernel_init+0x0/0x293
[<ffffffff8100c220>] ? child_rip+0x0/0x20
Booting on the "normal" debian kernel works without problems.
Hopefully soneone can help me
i did a clean install of proxmox following the wiki to 3.1, everthing worked.
After upgrading to 3.3-5 i can not boot onto the pve kernel anymore.
By chainloading into grub2 the following is shown on the terminal and it freezes.
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/grub/core.img
[Multiboot-kludge, loadaddr=0x100000, text-and-data=0x6585, bss=0x0, entry=0
x100950]
ÿLoading, please wait...
do_IRQ: 3.240 No irq handler for vector (irq -1)
do_IRQ: 2.240 No irq handler for vector (irq -1)
do_IRQ: 1.240 No irq handler for vector (irq -1)
do_IRQ: 0.240 No irq handler for vector (irq -1)
When i manually selec kernel 2.6.32-26-pve from grubs menu it freezses after a while again saying:
Initalizing network drop monitor service
md: Waiting for all devices to be available before autodetect
md: If you don't use raid, use raid=noautodetect
md: Autodetecting RAID arrays.
md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
VFS: Cannot open root device "sda1" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Pid: 1, comm: swapper veid: 0 Not tainted 2.6.32-26-pve #1
Call Trace:
[<ffffffff81537aa0>] ? panic+0xa7/0x167
[<ffffffff81c35202>] ? mount_block_root+0x1ce/0x27f
[<ffffffff81002930>] ? name_to_dev_t+0x750/0xe20
[<ffffffff81c3544c>] ? mount_root+0x57/0x5b
[<ffffffff81c355bd>] ? prepare_namespace+0x16d/0x1a6
[<ffffffff81c34f70>] ? kernel_init+0x28e/0x293
[<ffffffff8100c22a>] ? child_rip+0xa/0x20
[<ffffffff81c34ce2>] ? kernel_init+0x0/0x293
[<ffffffff8100c220>] ? child_rip+0x0/0x20
Booting on the "normal" debian kernel works without problems.
Hopefully soneone can help me