LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   raid+kernel_update=KERNEL PANIC! Need help, guys! (https://www.linuxquestions.org/questions/slackware-14/raid-kernel_update%3Dkernel-panic-need-help-guys-773861/)

Dinobot 12-06-2009 06:30 PM
raid+kernel_update=KERNEL PANIC! Need help, guys!
 
1 Attachment(s)
Hi guys. Sorry for my English, but I still hope you are understands me =).

I have slackware 13 x64 with the default kernel and all the stuff updated to CURRENT. Kernel is vmlinuz-huge-2.6.29.6 and all works fine with it.

My Disk Drive system is: adaptec 5405 raid controller + raid5 on it.

I got the last stable kernel from kernel.org and built it as usual with SCSI enabled and my RAID controller support added (SCSI->low level devices->Adaptec RAID aacraid)

But when I'm trying to boot system again, KERNEL PANIC happens! Root partition can not be mounted =\

P.S. I did the kernel update before. I can not get it working since I have RAID5+adaptec5405 as root disk system on my server... But the default kernel mounts raid as root partition ok!

Help me please..

Simon Bridge 12-06-2009 06:42 PM
Even though linux can boot from RAID, it is still good practise to put /boot an a normal (non-RAID) volume. This is true for all systems.

Sounds like your new kernel is not loading raid stuff early enough - did you compile in the capability or leave it as modules?

It can take quite a while to locate everything in the kernel tree, it is a good idea for you to get used to trawling through it though. What most people do is make a config for the old kernel, then use that as a point of departure to build the new one.

You should also check that grub is pointed at the correct volume.

manwichmakesameal 12-06-2009 09:36 PM
If it worked before with raid, how did you have your initrd.gz set up? Are you using one now? Maybe try using one. In the /etc/mkinitrd.conf, use RAID="0" along with any other options you need to use.

Dinobot 12-06-2009 11:22 PM
Quote:
Originally Posted by manwichmakesameal (Post 3782231)
If it worked before with raid, how did you have your initrd.gz set up? Are you using one now? Maybe try using one. In the /etc/mkinitrd.conf, use RAID="0" along with any other options you need to use.
Why should I use "RAID"=0?

man mkinitdir says:

Quote:
Examples:
RAID="0" # Do not add RAID support to initrd
RAID="1" # Add RAID support to initrd

Dinobot 12-06-2009 11:32 PM
Quote:
Originally Posted by Simon Bridge (Post 3782135)
Even though linux can boot from RAID, it is still good practise to put /boot an a normal (non-RAID) volume. This is true for all systems.

Sounds like your new kernel is not loading raid stuff early enough - did you compile in the capability or leave it as modules?

It can take quite a while to locate everything in the kernel tree, it is a good idea for you to get used to trawling through it though. What most people do is make a config for the old kernel, then use that as a point of departure to build the new one.

You should also check that grub is pointed at the correct volume.
Quote:
#cd /usr/src/linux
#make mrproper
#make menuconfig
#make bzImage
#make modules
#make modules_install
#make install
What's wrong with my modules?...

I'm using lilo and it looks to be set up correctly... Because I just need to replace /boot/vmlinuz with /boot/vmlinuz.old and call "lilo" to take me back to working kernel...

how can I use my old config to compile my new kernel from source? I think it can help me...

Is the trouble in the kernel config, or somewhere else?

Daedra 12-06-2009 11:51 PM
Have you tried statically compiling your raid driver and filesystem instead of using modules?

Dinobot 12-07-2009 12:42 AM
1 Attachment(s)
Quote:
Originally Posted by Daedra (Post 3782313)
Have you tried statically compiling your raid driver and filesystem instead of using modules?
Yes, now I built raid-controller driver inside my kernel...

And I get a new error) It can see my partition but can't mount EXT2 now =\

(see the picture below)

animeresistance 12-07-2009 03:01 AM
Something like this happened to me a long long time ago. But i just compiled the kernel, i didn't updated to current

You must make sure that you compile the kernel, and make sure that you have your modules loaded or you can compile the kernel with all the options you need.

Also make sure that your lilo.conf has the correct path to your mounting point (vi /etc/lilo.conf) and after you had checked your lilo.conf file, then reload lilo by typing lilo on the console environment ($: lilo)

Hope this helps.

Regards

Dinobot 12-07-2009 06:41 AM
Quote:
Originally Posted by animeresistance (Post 3782432)
Something like this happened to me a long long time ago. But i just compiled the kernel, i didn't updated to current

You must make sure that you compile the kernel, and make sure that you have your modules loaded or you can compile the kernel with all the options you need.

Also make sure that your lilo.conf has the correct path to your mounting point (vi /etc/lilo.conf) and after you had checked your lilo.conf file, then reload lilo by typing lilo on the console environment ($: lilo)

Hope this helps.

Regards
My problem fixed)

There are no EXT2 support in default kernel config... Just ext3 only.

Thank you, guys!


All times are GMT -5. The time now is 09:33 PM.