LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 12-06-2009, 07:30 PM   #1
Dinobot
Member
 
Registered: Nov 2009
Location: Not far from Moscow, Russia
Distribution: Slackware (forever!)
Posts: 46

Rep: Reputation: 15
raid+kernel_update=KERNEL PANIC! Need help, guys!


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..
Attached Images
File Type: jpg pizdec.jpg (265.5 KB, 8 views)
 
Old 12-06-2009, 07:42 PM   #2
Simon Bridge
Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 197Reputation: 197
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.
 
Old 12-06-2009, 10:36 PM   #3
manwichmakesameal
Member
 
Registered: Aug 2006
Distribution: Slackware
Posts: 800

Rep: Reputation: 100Reputation: 100
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.
 
Old 12-07-2009, 12:22 AM   #4
Dinobot
Member
 
Registered: Nov 2009
Location: Not far from Moscow, Russia
Distribution: Slackware (forever!)
Posts: 46

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by manwichmakesameal View Post
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
 
Old 12-07-2009, 12:32 AM   #5
Dinobot
Member
 
Registered: Nov 2009
Location: Not far from Moscow, Russia
Distribution: Slackware (forever!)
Posts: 46

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Simon Bridge View Post
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?
 
Old 12-07-2009, 12:51 AM   #6
Daedra
Senior Member
 
Registered: Dec 2005
Location: Springfield, MO
Distribution: Slackware64-14.1
Posts: 1,225

Rep: Reputation: 187Reputation: 187
Have you tried statically compiling your raid driver and filesystem instead of using modules?
 
Old 12-07-2009, 01:42 AM   #7
Dinobot
Member
 
Registered: Nov 2009
Location: Not far from Moscow, Russia
Distribution: Slackware (forever!)
Posts: 46

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by Daedra View Post
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)
Attached Images
File Type: jpg 07122009.jpg (282.9 KB, 4 views)
 
Old 12-07-2009, 04:01 AM   #8
animeresistance
Member
 
Registered: Feb 2004
Distribution: Slackware
Posts: 192

Rep: Reputation: 20
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
 
Old 12-07-2009, 07:41 AM   #9
Dinobot
Member
 
Registered: Nov 2009
Location: Not far from Moscow, Russia
Distribution: Slackware (forever!)
Posts: 46

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by animeresistance View Post
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!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel Panic on boot related to software raid 6 mdrum Linux - Newbie 1 11-20-2008 02:41 PM
booting off RAID in debian (kernel panic - not syncing) guysoft Linux - Enterprise 0 02-01-2006 01:35 PM
Kernel Panic: Booting into RAID 1 elliotfuller Linux - Hardware 0 09-07-2005 03:01 AM
Kernel panic - HPT366 RAID breenbaron Linux - Hardware 14 10-07-2004 04:20 PM
Kernel 2.6, RAID-1 & reiserfs kernel panic Raptor Ramjet Slackware 2 01-04-2004 08:25 AM


All times are GMT -5. The time now is 08:14 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration