| Re: ovzkernels not booting - where to look first [message #15474 is a reply to message #15472] |
Wed, 01 August 2007 13:33   |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
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.
2)
| Quote: |
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
| 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
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
Hope this helps.
Thank you,
Konstantin.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
