OpenVZ Forum


Home » General » Support » ovzkernels not booting - where to look first
Re: ovzkernels not booting - where to look first [message #15481 is a reply to message #15474] Wed, 01 August 2007 19:38 Go to previous messageGo to previous message
ugob is currently offline  ugob
Messages: 271
Registered: March 2007
Senior Member
finist wrote on Wed, 01 August 2007 09:33

Hello Ugo,

1) can you please check that the processor supports the PAE?
# cat /proc/cpuinfo
...
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext lm 3dnowext 3dnow pni
...

e.g. 'pae' flag should present.



flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse pni syscall mp mmxext 3dnowext 3dnow

So it looks OK.

finist wrote on Wed, 01 August 2007 09:33


2) it may be initrd related issue. are you sure that initrd image for new kernel has been created correctly?

Could you please check the /etc/grub.conf (or lilo.conf if you are using lilo). There should be an entry for the newly installed ovzkernel-PAE-2.6.18-8.1.8.el5.028stab039.1
Do those files mentioned in 'kernel' and 'initrd' sections exist in /boot? Could you please try to recreate initrd file using the following command? Are there any errors reported?
# mkinitrd -v -f /boot/initrd-2.6.18-8.1.8.el5.028stab039.1PAE.img 2.6.18-8.1.8.el5.028stab039.1PAE



All files are there. I tried recreating the file like you suggested, no error.

Creating initramfs
Looking for deps of module scsi_mod
Looking for deps of module sd_mod        scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module unknown
Looking for deps of module 3w-xxxx       scsi_mod
Looking for deps of module scsi_mod
Looking for deps of module ide-disk
Looking for deps of module ext3  jbd
Looking for deps of module jbd
Using modules:  ./kernel/drivers/scsi/scsi_mod.ko ./kernel/drivers/scsi/sd_mod.ko ./kernel/drivers/scsi/3w-xxxx.ko ./kernel/fs/jbd/jbd.ko ./kernel/fs/ext3/ext3.ko
/sbin/nash -> /tmp/initrd.n19895/bin/nash
/sbin/insmod.static -> /tmp/initrd.n19895/bin/insmod
/sbin/udev.static -> /tmp/initrd.n19895/sbin/udev
/etc/udev/udev.conf -> /tmp/initrd.n19895/etc/udev/udev.conf
copy from /lib/modules/2.6.18-8.1.8.el5.028stab039.1PAE/./kernel/drivers/scsi/scsi_mod.ko(elf32-i386) to /tmp/initrd.n19895/lib/scsi_mod.ko(elf32-i386)
copy from /lib/modules/2.6.18-8.1.8.el5.028stab039.1PAE/./kernel/drivers/scsi/sd_mod.ko(elf32-i386) to /tmp/initrd.n19895/lib/sd_mod.ko(elf32-i386)
copy from /lib/modules/2.6.18-8.1.8.el5.028stab039.1PAE/./kernel/drivers/scsi/3w-xxxx.ko(elf32-i386) to /tmp/initrd.n19895/lib/3w-xxxx.ko(elf32-i386)
copy from /lib/modules/2.6.18-8.1.8.el5.028stab039.1PAE/./kernel/fs/jbd/jbd.ko(elf32-i386) to /tmp/initrd.n19895/lib/jbd.ko(elf32-i386)
copy from /lib/modules/2.6.18-8.1.8.el5.028stab039.1PAE/./kernel/fs/ext3/ext3.ko(elf32-i386) to /tmp/initrd.n19895/lib/ext3.ko(elf32-i386)
Loading module scsi_mod
Loading module sd_mod
Loading module 3w-xxxx
Loading module jbd
Loading module ext3


finist wrote on Wed, 01 August 2007 09:33


Quote:

Could you please try to install RHEL5/CentOs5 kernel on the node?


Well, could you try to install a stock kernel from CentOS 5 and boot in it?
For example that one: http://isoredirect.centos.org/centos/5/updates/i386/RPMS/ker nel-PAE-2.6.18-8.1.8.el5.i686.rpm



Can't install:
[root@bibitte ~]# rpm -ivhf kernel-PAE-2.6.18-8.1.8.el5.i686.rpm
warning: kernel-PAE-2.6.18-8.1.8.el5.i686.rpm: V3 DSA signature: NOKEY, key ID e8562897
error: Failed dependencies:
        initscripts >= 8.11.1-1 is needed by kernel-PAE-2.6.18-8.1.8.el5.i686
        mkinitrd >= 4.2.21-1 is needed by kernel-PAE-2.6.18-8.1.8.el5.i686
        ppp < 2.4.3-3 conflicts with kernel-PAE-2.6.18-8.1.8.el5.i686
        e2fsprogs < 1.37-4 conflicts with kernel-PAE-2.6.18-8.1.8.el5.i686
        procps < 3.2.5-6.3 conflicts with kernel-PAE-2.6.18-8.1.8.el5.i686
        udev < 063-6 conflicts with kernel-PAE-2.6.18-8.1.8.el5.i686
        iptables < 1.3.2-1 conflicts with kernel-PAE-2.6.18-8.1.8.el5.i686


It is quite troubling, that, according to the sysadmin at the colocation facility, even the -smp kernel, which was running fine before the upgrade, doesn't boot anymore...

finist wrote on Wed, 01 August 2007 09:33


3) If all of this won't work, please, try to attach a serial console to the node or at least KVM. This will allow us to collect the boot logs or at least to see the last messages. If you are going to the colocation facility, please, take a photo with you and take a photo of a screen of a hanged node. If we are lucky the last messages can contain useful information.
http://wiki.openvz.org/Remote_console_setup


Hmmm, I don't have my digital camera with me, only my cell. Not sure if I have a null modem cable. I'll see. I will have, for sure, a paper notepad, and a pen Smile.


Thanks!


Please read the manual before asking questions:
http://download.openvz.org/doc/OpenVZ-Users-Guide.pdf

Please have a look at the wiki before asking questions:
http://wiki.openvz.org/Main_Page

[Updated on: Wed, 01 August 2007 19:39]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: reiser4
Next Topic: Activated NFS and now the ve won't bring up network
Goto Forum:
  


Current Time: Wed Sep 10 16:55:22 GMT 2025

Total time taken to generate the page: 0.07341 seconds