Problems booting ovzkernel-2.6.8-022stab045.1
Hi, I have a machine running CentOS 4.2, which runs sucessfully ovzkernel-2.6.8-022stab044.1 (Note: 44.1!) When I try to run ovzkernel-2.6.8-022stab045.1 (Note: 45.1!), I get a kernel panic during boot: ------------------snip------------------------ md: ... autorun DONE. Creating root device Mounting root filesystem EXT3-fs: unable to read superblock mount: error 22 mounting ext3 mount: error 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic: Attempted to kill init! ------------------snip------------------------ I am using software-RAID 1 for all filesystems (created a simple mirror of two SATA discs). As mentioned, the kernel downloaded from http://download.openvz.org/kernel/022stab044.1/ovzkernel-2.6 .8-022stab044.1.i686.rpm runs fine, but http://download.openvz.org/kernel/022stab045.1/ovzkernel-2.6 .8-022stab045.1.i686.rpm does not work. A screenshot of the kernel panic (shown via the remote-manamgent-card of the machine) is attached. regards, Werner
Re: Problems booting ovzkernel-2.6.8-022stab045.1
wfisher, we'll check it. thanks for the report.
Hello wfisher, could you please give me (or dev) via pm an access to your node? I would like to see bootlogs from 022stab044.1 kernel and to check the content of initrd image from 022stab045.1 kernel. Thank you, Vasily Averin
Hello Vasily Averin, thanks for your reply. I have attached the first part of the bootlog when booting with 022stab044.1. I have used the provided binary packages from http://download.openvz.org/kernel/022stab045.1/ovzkernel-2.6 .8-022stab045.1.i686.rpm - so the used initrd is from this RPM. Unfortunately I can currently not setup remote access. Is the supplied information helpful? greetings, Werner Fischer
Hello wfisher, unfortunately I cannt found useful information in your attach file. Could you please do following: 1) boot into 022stab044.1 kernel 2) send me /var/log/dmesg file 3) send me /var/log/messages.* files 4) send me initrd images both for 022stab044.1 kernel and for 022stab045.1 kernel It should give me all the possible information about your problem. Thank you, Vasily Averin
Thank you for your reply, unfortunatly I'm just leaving for a business trip and will be back on friday in the office. I'll post the needed information then. Sorry for the delay, thanks for your support, Werner Fischer
Sorry for the delay - unfortunately I was not able to do any further checks. Meanwhile 2.6.8-022stab050.1 is released, so I will continue to test with this kernel and post my experience afterwards.
Hello Vasily Averin, the problem still exists with stab50.1-smp kernel. To ensure that the problem is reproduceable at my server, I did the following: -> installed CentOS 4.2 from scratch (with a single SATA disk, no software RAID this time) -> installed ovzkernel-smp-2.6.8-022stab044.1.i686.rpm and booted it (works fine) -> installed ovzkernel-smp-2.6.8-022stab050.1.i686.rpm and tried to boot it (didn't work again) -> booted into ovzkernel-smp-2.6.8-022stab044.1.i686 again, and grabbed the files you requested: 2) send me /var/log/dmesg file 3) send me /var/log/messages.* files 4) send me initrd images both for 022stab044.1 kernel and for 022stab045.1 kernel (I attached the stab050.1 initrd image, 'cause I'm testing with 050.1/044.1 now) I have attached the files. I have also included a screenshot of the kernel panic of stab050.1smp-kernel. The dmesg and messages files should be clearly readable (because of the complete fresh installation, there is no old/confusing information in there). Thank you very much for your efforts! best regards, Werner Fischer PS: in the server we have the following Intel Mainboard: SE7221BK1-E (http://www.intel.com/design/servers/boards/SE7221BK1-E/)
Hello, I want to report that we too are having the same exact issue. Have CentOS 4.2, with 2 SATA Disks in Software Raid 1. Will run on Kernel ovzkernel-2.6.8-022stab044.1, but anything later upto the latest 05.1 results in the same Kernel Panic.
Sehr geehrter Herr Fisher, sorry for a long delay. I've investigated your files. Looks like our new kernels cannot found partition with LABEL=/ Let's try to set root=/dev/sda1 for the new ovzkernels in the grub.conf file. I hope it help yous to resolve this issue. To be sure could you please send me your /etc/grub.conf file. Mit freundlichen Gruessen Vasily Averin
Hello Vasily Averin, thank you for your reply. Unfortunately changing to root=/dev/sda1 does not help - the kernel panic still occurs. I have attached the grub.conf files (the one before I did the modification, and the one after I did the modification). I can setup remote access for you now, if it helps. Just let me know - and I'll send you the remote access data via the private mail function of the forum. We have a Peppercon eRIC remote management card installed, so you can also go into the BIOS, power on / power off the server remotely... Thanks for your friendly assistance, we appreciate it very much, best regards, Werner
I've also tried this, root=/dev/sda1 same kernel panic at boot with ovzkernel-smp-2.6.8-022stab050. When we reverted back to the old ovzkernel-smp-2.6.8-022stab044.1 kernel, we had stability problems. The system would boot fine, but when under heavy load the kernel would crash. EFLAGS: 00000246 Not Tainted (ovzkernel-smp-2.6.8-022stab044.1-smp) EIP = 0060
Sehr geehrter Herr Fischer, Could you please send me remote access data via PM. Thank you, Vasily Averin
Could you provide us with a remote access to your node? If yes, please send the login credentials via PM to either me or vaverin and will will investigate the issue. Thanks.
Sehr geehrter Herr Fischer, mintra, It seems I'm understand the cause of your troubles: in .45 kernel we have moved support for SATA controller with PCI ID 8086:2652 and 8086:2653 from ata_piix subdriver to ahci subdriver. However due misprinting we have not enabled the compilation of ahci subdriver in our kernels. Looks like you have mentonied SATA controllers, and the boot is failed because of our .45 and .50 kernels have not support for these devices. This error is fixed already and we're going to release new kernel soon. Thank you for your bugreports, Vasily Averin
Thank you very much for investigations. I noticied that I have forgotten to also send you the root password of server - it seems that you did solve the problem without it. I'm looking forward to the new kernel - if I have time, perhaps I'll try to compile 050.1 on my ownwith ahci enabled meanwhile (if I do, I'll post my experiences in this thread). Thanks a lot again for your great support! have a nice weekend, Werner
Thank you for investigating this. Look forward to trying out the new Kernel
We have just released 056 kernel, please try it out.
Excellent work guys, the new Kernel works with the SATA and Software Raid. Last week when we were in limbo about what to do, it was decided to try out XEN Virtualization. From what is written in the press the Xen system has alot of promise, Features such as opensource with live migration and backups sounds great; but was far too complicated to get working in our configuration. OpenVZ was the only virtualserver system that was simple to install and get working. Thanks again.
Glad, to hear that! Hope you keep being with us And we'll bring new features for you! BTW, migration on OpenVZ can be implemented _very_ easily... And live migration is present in Virtuozzo.
The 056 kernel works for us, too. Thanks again very much for your support, Greetings from Austria, Werner
This problem still exists with the ovzkernel-smp-2.6.8-022stab056.1.i686.rpm kernel. The error is below: [root@vz1 install]# rpm -ihv ovzkernel-smp-2.6.8-022stab056.1.i686.rpm warning: ovzkernel-smp-2.6.8-022stab056.1.i686.rpm: V3 DSA signature: NOKEY, key ID a7a1d4b6 Preparing... ########################################### [100%] 1:ovzkernel-smp ########################################### [100%] WARNING: No module ata_piix found for kernel 2.6.8-022stab056.1-smp, continuing anyway WARNING: No module mptscsih found for kernel 2.6.8-022stab056.1-smp, continuing anyway WARNING: No module raid1 found for kernel 2.6.8-022stab056.1-smp, continuing anyway
These are warnings only, caused by the face that OpenVZ kernel has Disk drivers builtin in kernel, not in modules.
So is it OK to try to boot that? Just curious. I actually compiled the kernel source, but I'd like to go back to the RPM version.
Hi, Yep, it worked with the RPM version. Sorry for the confusion. Regards,
no problem! better worry, than sorry )))