bug? : pve-kernel3.10.0.-7-pve don't boot - e1000e

B

badji

Renowned Member
Jan 14, 2011
236
35
93
My server does not boot with the kernel: pve-kernel-3.10.0.7-pve.

While the 2.6.32 kernel boot fine.

The message: e1000e: The NVM is Checksun Not valid.
Volume group "PVE" not found

with the command: cat / proc / modules
.
.
e1000e 268 333 0 - Live 0xffffffffa0014000 (0)

The problem is with the e1000e.

an idea to fix it? my bios is current.

thank's.
 
badji said:
My server does not boot with the kernel: pve-kernel-3.10.0.7-pve.

...
Volume group "PVE" not found
...
Click to expand...
Hi badji,
this sound more for an timeout problem (which I also have on other AMD-boxes with 3.10).

Can you try following entry in /etc/default/grub ? (update-grub after that of course)
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=30"

Udo
 
Hi,

Same problem here with 3.10.0-7.

Did not try 2.6.32, but 3.10.0-5-pve boots fine.

Christophe.
 
udo said:
Hi badji,
this sound more for an timeout problem (which I also have on other AMD-boxes with 3.10).

Can you try following entry in /etc/default/grub ? (update-grub after that of course)
Code: 
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=30"

Udo
Click to expand...

Thank's Udo it work's.

Merci beaucoup.
 
Also same problem here, added rootdelay did not help. Maybe 3.10.0-7 doesn't have support for my old HP P400 raid controller and thus don't see the root device(s) /dev/cciss/c0d0p? and thus don't get initialized mapper devices, anyone?
 
Maybe my issue with not finding VG pve is that my P400 smart array isn't supported by initrd image modules (hpsa / cciss) like in this old thread so howto ensure this in kernel 3.10.0-7... would this also be the case with new release 3.4 of pve ie what kernel comes with this release?
 
Seems I might be missing cciss in 3.10.0-7:

root@node7:/lib/modules# find . -type f \( -name 'cciss*' -o -name 'hpsa*' \)
./2.6.32-32-pve/kernel/drivers/scsi/hpsa.ko
./2.6.32-32-pve/kernel/drivers/block/cciss.ko
./3.10.0-7-pve/kernel/drivers/scsi/hpsa.ko
./2.6.32-37-pve/kernel/drivers/scsi/hpsa.ko
./2.6.32-37-pve/kernel/drivers/block/cciss.ko
root@node7:/lib/modules#

Howto get this for pve-kernel-3.10?
 
Will do only I believe this not to work as currently I have used ref to cciss device names and believe the hpsa will not name device as such. It is a scsi driver and thus will name devices like /dev/sdX...
 
stefws said:
Will do only I believe this not to work as currently I have used ref to cciss device names and believe the hpsa will not name device as such. It is a scsi driver and thus will name devices like /dev/sdX...
Click to expand...
Hi,
this should not matter, because grub use UUIDs and lvm-path:
Code: 
menuentry 'Proxmox Virtual Environment GNU/Linux' --class proxmox --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-s
imple-af77d1a1-ec57-4385-b97c-eb65ac7caf8d' {
        load_video
        insmod gzio
        if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt2'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 --hint='hd0,gpt2'  fc802804-3765-4e8e-9eaa-84aeee86df29
        else
          search --no-floppy --fs-uuid [B]--set=root fc802804-3765-4e8e-9eaa-84aeee86df29[/B]
        fi
        echo    'Loading Linux 2.6.32-37-pve ...'
        linux   /vmlinuz-2.6.32-37-pve [B]root=/dev/mapper/pve-root[/B] ro  quiet
        echo    'Loading initial ramdisk ...'
        initrd  /initrd.img-2.6.32-37-pve
}

## /boot:
blkid
/dev/sda2: UUID="fc802804-3765-4e8e-9eaa-84aeee86df29" TYPE="ext3"
Udo
 
Nope hpsa does not support my old P400 smart arrays even with hpsa_allow_any=1 it seems :/

Seems it would require the cciss module for 3.10...
Means I need to install a build enviroment on another piece of iron/VM that can boot the 3.10 kernel...
 
Anyone knows what might be wrong with my environment trying to compile latest cciss block driver module under PVE 3.4 w/kernel 3.10.0-7 with kernel.org settings?

Code: 
make -C /lib/modules/3.10.0-7-pve/build M=/root/src/cciss-4.6.28/drivers/block modules
make[1]: Entering directory `/usr/src/linux-headers-3.10.0-7-pve'
 CC [M]  /root/src/cciss-4.6.28/drivers/block/cciss.o
/root/src/cciss-4.6.28/drivers/block/cciss.c:225:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_interrupt_mode’
/root/src/cciss-4.6.28/drivers/block/cciss.c:226:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_enter_simple_mode’
/root/src/cciss-4.6.28/drivers/block/cciss.c:244:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_find_cfg_addrs’
/root/src/cciss-4.6.28/drivers/block/cciss.c:247:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_pci_find_memory_BAR’
/root/src/cciss-4.6.28/drivers/block/cciss.c:250:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:277:2: warning: initialization from incompatible pointer type [enabled by default]
/root/src/cciss-4.6.28/drivers/block/cciss.c:277:2: warning: (near initialization for ‘cciss_fops.release’) [enabled by default]
/root/src/cciss-4.6.28/drivers/block/cciss.c: In function ‘cciss_seq_open’:
/root/src/cciss-4.6.28/drivers/block/cciss.c:544:3: error: implicit declaration of function ‘PDE’ [-Werror=implicit-function-declaration]
/root/src/cciss-4.6.28/drivers/block/cciss.c:544:28: error: invalid type argument of ‘->’ (have ‘int’)
/root/src/cciss-4.6.28/drivers/block/cciss.c: At top level:
/root/src/cciss-4.6.28/drivers/block/cciss.c:600:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_procinit’
/root/src/cciss-4.6.28/drivers/block/cciss.c:2711:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_send_reset’
/root/src/cciss-4.6.28/drivers/block/cciss.c:3851:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_wait_for_mode_change_ack’
/root/src/cciss-4.6.28/drivers/block/cciss.c:3865:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
/root/src/cciss-4.6.28/drivers/block/cciss.c:3932:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_put_controller_into_performant_mode’
/root/src/cciss-4.6.28/drivers/block/cciss.c:3994:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_interrupt_mode’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4040:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_lookup_board_id’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4070:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_pci_find_memory_BAR’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4087:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_wait_for_board_state’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4115:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_find_cfg_addrs’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4131:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_find_cfgtables’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4160:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_get_max_perf_mode_cmds’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4181:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_find_board_params’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4243:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_pci_init’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4359:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4499:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4505:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4522:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘void’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4531:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4555:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4701:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4735:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4755:18: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘int’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4823:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_kdump_soft_reset’
/root/src/cciss-4.6.28/drivers/block/cciss.c:4878:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_init_one’
/root/src/cciss-4.6.28/drivers/block/cciss.c:5134:22: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_enter_simple_mode’
/root/src/cciss-4.6.28/drivers/block/cciss.c:5156:23: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘cciss_remove_one’
/root/src/cciss-4.6.28/drivers/block/cciss.c:5232:11: error: ‘cciss_init_one’ undeclared here (not in a function)
/root/src/cciss-4.6.28/drivers/block/cciss.c:5233:2: error: implicit declaration of function ‘__devexit_p’ [-Werror=implicit-function-declaration]
/root/src/cciss-4.6.28/drivers/block/cciss.c:5233:24: error: ‘cciss_remove_one’ undeclared here (not in a function)
/root/src/cciss-4.6.28/drivers/block/cciss.c: In function ‘cciss_cleanup’:
/root/src/cciss-4.6.28/drivers/block/cciss.c:5279:4: error: implicit declaration of function ‘cciss_remove_one’ [-Werror=implicit-function-declaration]
...
 
You must log in or register to reply here.
Top Bottom