Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: stian on November 01, 2006, 01:27:42 PM
-
I see in the boot splash screen that it is the CentOS (2.6.9-34.0.2.ELsmp) kernel that is booting. Is that correct? I did a fresh install from 7.0stable and the yum update. I get an Kernel panic - not syncing: Attempted to kill init! when i boot with the new kernel.
I have an Areca hardware raid card that I must load a driver for during install of 7.0stable. Works fine until the yum update and reboot to the new kernel. Is that the problem? That the driver for the raid-card is not included in the new kernel? Is there any easy way to "copy" the driver over to the new kernel before rebooting?
If I choose to boot with the kernel SME Server (2.6.9-34.ELsmp) at the splash screen all works fine again, but is this "safe"?
-
See related thread here
http://forums.contribs.org/index.php?topic=33825.0
and here
http://forums.contribs.org/index.php?topic=33780.0
This may not seem to be related until you look at the bug report on how the kernel is selected after a yum upgrade. See the bug report here.
http://bugs.contribs.org/show_bug.cgi?id=1930
The short answer to your question is, Yes it is safe and you should be booting the SME Server version of the kernel instead of the CentOS version.
Royce H.
-
I just reread your post and saw this,
CentOS (2.6.9-34.0.2.ELsmp)
Kernel booted after install.
You then changed to
SME Server (2.6.9-34.ELsmp)
I would suggest that you try booting SME Server (2.6.9-34.0.2.ELsmp)
I am not sure if this will work but it might. (this would put you into the current version of the kernel.)
-
The SME Server (2.6.9-34.0.2.ELsmp) kernel is not one of the options at my boot screen.
I only have:
CentOS (2.6.9-34.0.2.EL)
CentOS (2.6.9-34.0.2.ELsmp)
SME Server (2.6.9-34.EL)
SME Server (2.6.9-34.ELsmp)
-
what does uname -a show?
If it is Linux <servername> 2.6.9-34.ELsmp I believe you are on the latest SME7 kernel.
The last option on your screen
CentOS (2.6.9-34.0.2.EL)
CentOS (2.6.9-34.0.2.ELsmp)
SME Server (2.6.9-34.EL)
SME Server (2.6.9-34.ELsmp)
Is correct and the latest kernel for a multi processor system.
If this boots and works correctly you should not need to do anything with the raid card drivers to get onto the current kernel.
I believe GRUB will boot this kernel from now until another update or a different kernel is manually selected at startup
-
It shows:
Linux vinstra 2.6.9-34.ELsmp #1 SMP Wed Mar 8 00:27:03 CST 2006 i686 i686 i386 GNU/Linux
-
Just found another post where someone has posted the output of uname -a:
Linux sme7 2.6.9-34.0.2.EL #1 Fri Jul 7 19:24:57 CDT 2006 i686 i686 i386 GNU/Linux
From this thread: http://forums.contribs.org/index.php?topic=33825.0
So it looks like he has a newer kernel than I do...
-
He was booting the CentOS version of the kernel. If you go back into that post he ended up at the same place as you are now booting the
SME Server (2.6.9-34.ELsmp) Kernel.
How do I know? That was me. :?
(That just goes to show I should have known better then this post:
I just reread your post and saw this,
Quote:
CentOS (2.6.9-34.0.2.ELsmp)
Kernel booted after install.
You then changed to
Quote:
SME Server (2.6.9-34.ELsmp)
I would suggest that you try booting SME Server (2.6.9-34.0.2.ELsmp)
I am not sure if this will work but it might. (this would put you into the current version of the kernel.))
But I couldn't quite remember how the boot screen looked and didn't want to reboot my production server to see.
Good day and Good Luck with SME,
Royce Holdeman
-
Thanks! :-)
-
I would suggest that you try booting SME Server (2.6.9-34.0.2.ELsmp)
I am not sure if this will work but it might. (this would put you into the current version of the kernel.)
See this bug here it would seem the Centos 2.6.9-34.0.2.ELsmp is not being renamed to SME Server...
http://bugs.contribs.org/show_bug.cgi?id=1996
-
NOW MY HAIR IS TURNING GREY
CentOS (2.6.9-34.0.2.EL)
CentOS (2.6.9-34.0.2.ELsmp)
SME Server (2.6.9-34.EL)
SME Server (2.6.9-34.ELsmp)
byte,
Per your post we should be booting option #2-CentOS (2.6.9-34.0.2.ELsmp). Is the bug confirmed well enough that we KNOW this is correct?
If so stian does have a driver issue with his raid card.
Royce Holdeman
-
Ok...
I have tried this I found on the areca faq site:
http://faq.areca.com.tw/modules/smartfaq/faq.php?faqid=224
I went through this before doing the yum update. Also did the sam for smp-kernel. It did not help. Is there anything I should modify to this to get it work on smeserver?
Also this:
http://faq.areca.com.tw/modules/smartfaq/faq.php?faqid=191
Is there any way to describe how i can do this?
-
Is the bug confirmed well enough that we KNOW this is correct?
I would have said so but I'm no core dev.
I think from seeing various posts on here it is, but we really need people to report these to the Bug Tracker and/or open a new bug if it doesn't exist.
-
Stian,
We need to wait for an answer from Byte on the kernel version before we get to far along with this. If the SME kernel should be at version 2.6.9-34.0.2 you have an issue that you are not running the latest kernel. I and I think Byte also was under the impression that the latest kernel in SME was 2.6.9-34.
Byte has much more experiance then I do and I am suspicious that you do also (I have never attempted to build a 3tb server)
In the meantime does your server boot and work without errors with the old SME 2.6.9-34 kernel?
Royce H.
-
I and I think Byte also was under the impression that the latest kernel in SME was 2.6.9-34.
No, the latest in the default yum repo's are with 2.6.9-34.02 which when downloaded via YUM are left as Centos label and not SME Server.
Please report your findings via the bug tracker the more people who report the better outcome the bug will have.
-
Ok. But what bug should I report? That the kernel is labeled wrong at the bootloader or that the kernel 2.6.9-34.02 gives me kernel panic for my hardware raid?
mercyh: Yes it seems to work under the old SME 2.6.9-34 kernel, but the server is not in "production" so it is not very stressed...
-
In my opinion the kernel panic for your hardware raid is not a bug in SME. It is either a result of hardware that is not supported "out of the box" by CentOS or if the hardware is listed as supported it is a CentOS bug.
I don't know how much work you have done on customizing this server but it looks like if you want to use this hardware you will need to reinstall the current version from an ISO and build the driver like you did the first time. If I understand the directions from the areca website you will need to be sure and rebuild the driver for the correct kernel BEFORE you do any yum upgrades in the future.
On my end it looks like I need to reboot my server with the latest kernel :oops:
-
Is there by any chance any way to download an iso containing the updates? With the latest kernel included? That would solve my problem until the kernel is updated again.
I am not a linux expert and do not know how to rebuild the driver for the correct kernel while I am in the "old" kernel...
Can anyone maybe point me to some directions?
-
Not that I can really help, but what model card do you have ?
Also, you said the FAQ did not help..
a. Before they want to isntall 2.6.9-34.0.2EL, do a
mkdir -p /lib/modules/2.6.9-34.0.2EL/updates
cp -R /lib/modules/2.6.9-34.EL/updates/* /lib/modules/2.6.9-34.0.2EL/updates
b. now install the new 2.6.9-34.0.2EL kernel RPM
Was the 2.6.9-34.0.2 kernel already on the system before you did the above ?
-
No, tried that before I did the yum update.
-
Tried again now and saw this during the update:
Installing: kernel ##################### [ 6/131]
WARNING: No module arcmsr found for kernel 2.6.9-34.0.2.EL, continuing anyway
Updating : kernel-module-slip ##################### [ 7/131]
AND:
Installing: kernel-smp ##################### [ 2/131]
WARNING: No module arcmsr found for kernel 2.6.9-34.0.2.ELsmp, continuing anyway
Updating : chkconfig ##################### [ 3/131]
And then I found out that it was a type error at the Areca support site...
They were missing a puncture between ...02EL. It should be ...02.EL.
So the correct commands for Smeserver should be:
mkdir -p /lib/modules/2.6.9-34.0.2.EL/updates
cp /lib/modules/2.6.9-34.EL/updates/* /lib/modules/2.6.9-34.0.2.EL/updates
mkdir -p /lib/modules/2.6.9-34.0.2.ELsmp/updates
cp /lib/modules/2.6.9-34.ELsmp/updates/* /lib/modules/2.6.9-34.0.2.ELsmp/updates
The server now boots up in the new kernel.... :-) :-) :-)
-
Very Good.
The next kernel sitting in the smeupdates-testing repo is 2.6.9-42.0.2.EL .
Hmm.. I wonder... ;)
-
I`ll test it over the weekend.
-
Works fine:
mkdir -p /lib/modules/2.6.9-42.0.2.EL/updates
cp /lib/modules/2.6.9-34.EL/updates/* /lib/modules/2.6.9-42.0.2.EL/updates
mkdir -p /lib/modules/2.6.9-42.0.2.ELsmp/updates
cp /lib/modules/2.6.9-34.ELsmp/updates/* /lib/modules/2.6.9-42.0.2.ELsmp/updates
Does anyone know if theres any chance for Areca Card-drivers to be build in to the kernel?
-
Hi All,
I am sorry to butt in on this thread but I am easily confused :D If I run uname -a I get myserver 2.6.9-34EL is this the correct kernel for a single CPU system, the reason I am confused is I have tried most options at boot up because Asterisk doesn't start on boot since I did the last yum update (and I got a message yesterday telling me there were some more updates!) So I have completly lost myself as to what the kernel was booting before yum updated it :shock:
Regards,
Del
-
del
2.6.9-34.EL was the origional.
I you have a look at this thread it has the work around for your asterisk problem .... look at last post of mine.
http://forums.contribs.org/index.php?topic=33194.0
I have tested this with the new kernel as well and works fine.
Regards,
Tib
-
If I run uname -a I get myserver 2.6.9-34EL is this the correct kernel for a single CPU system
The latest kernel shows like this in the boot menu
CentOS 2.6.9-34.0.2 EL
(this is the single processor version)
I ran the latest update from 11/7/06 and did not get a kernel upgrade.
Part of what makes this so confusing is that the ISO (used for the initial install) identifies the kernel as SME and any kernel that is brought in as a yum update is labeled as CentOS.
If you would like to see this changed. Leave your thoughts on the bugtracker here.
http://bugs.contribs.org/show_bug.cgi?id=1996
-
So I have completly lost myself as to what the kernel was booting before yum updated it
Another thing to be aware of. Grub will not automatically boot the correct kernel after an update. It is setup to boot the kernel that updated last.
If you are running a multiprocessor system and the last kernel upgraded was the single processor kernel, the single processor kernel will boot.
See bug here;
http://bugs.contribs.org/show_bug.cgi?id=1930
-
I ran the latest update from 11/7/06 and did not get a kernel upgrade.
I have done some more research and find that there was an upgrade on the 11/7/06 update. However GRUB did not boot into the new kernel.
See newest thread here
http://forums.contribs.org/index.php?topic=34532.0
and bug here
http://bugs.contribs.org/show_bug.cgi?id=2061