LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
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
 
LinkBack Search this Thread
Old 07-05-2007, 08:35 AM   #1
ErV
Senior Member
 
Registered: Mar 2007
Location: Russia
Distribution: Slackware 12.2
Posts: 1,202
Blog Entries: 3

Rep: Reputation: 62
Slackware 12: trouble booting 2.6.21.5-smp kernel. initrd problem?


Hello!
I"ve just installed slackware 12, and I've got following problem: I can boot only using huge-smp (or just "huge") kernel. While booting "normal" ("non-huge") kernel, booting fails with:
1) "no filesystem could mount root partition" (if I'm trying to boot kernel without initrd" or
2) "no /sbin/init found on rootdev (or not mounted). Trouble ahead". (if I'm trying to use initrd.

I'm using ext3 for root partition. initrd was created using mkinitrd that comes with slackware 12 (mkinitrd -c -k 2.6.21.5-smp -m ext -f ext -r /dev/hdc3) but it looks like inintrd images doesn't work.

It looks like one of the solutions is to compile kernel with builtin ext3 support. But what are the ways to load "non-huge" kernel without recompiling it?

Thanks.

Last edited by ErV; 07-05-2007 at 08:52 AM.
 
Old 07-05-2007, 08:42 AM   #2
tramni1980
Member
 
Registered: Jul 2006
Location: Tübingen, Germany
Distribution: Slackware64-13.37
Posts: 733

Rep: Reputation: 37
have you toggled /dev/hdc3 bootable?
 
Old 07-05-2007, 08:43 AM   #3
Michielvw
Member
 
Registered: May 2005
Location: Leicester,UK
Distribution: Slackware
Posts: 108

Rep: Reputation: 19
Well it looks like your mkinitrd command is a bit faulty. Have a good read of the mkinitrd manual page, the /boot/README.initrd and also see mkinitrd --help.

I am going to give you two hints here, that may help you solve the problem:
1) Look at the file system you are specifying
2) Look at the kernel for which you are building your initrd

Good Luck
 
Old 07-05-2007, 09:15 AM   #4
ErV
Senior Member
 
Registered: Mar 2007
Location: Russia
Distribution: Slackware 12.2
Posts: 1,202
Blog Entries: 3

Original Poster
Rep: Reputation: 62
Quote:
Originally Posted by tramni1980
have you toggled /dev/hdc3 bootable?
Yes, it boots with "huge" kernels (I've added a selection of kernel into /etc/lilo.conf, and only thing that boots is "huge" kernel.) I suppose that booting without initrd doesn't work because ext3 support is compiled as a module and isn't available at boot time. (I remember that Slackware 11 was somehow first mounting root partition as ext2 and then was remounting it as ext3).

Quote:
Originally Posted by Michielvw
Well it looks like your mkinitrd command is a bit faulty. Have a good read of the mkinitrd manual page, the /boot/README.initrd and also see mkinitrd --help.

I am going to give you two hints here, that may help you solve the problem:
1) Look at the file system you are specifying
2) Look at the kernel for which you are building your initrd

Good Luck
Ok, thanks.
 
Old 07-05-2007, 09:34 AM   #5
Carpo
Member
 
Registered: Aug 2003
Location: Somewhere
Distribution: Gentoo (for now)
Posts: 364

Rep: Reputation: 30
hint - ext3
 
Old 07-05-2007, 09:50 AM   #6
ErV
Senior Member
 
Registered: Mar 2007
Location: Russia
Distribution: Slackware 12.2
Posts: 1,202
Blog Entries: 3

Original Poster
Rep: Reputation: 62
Well, I'm not sure what was wrong before. Maybe I've made same misprint as in a first post (ext instead of ext3), or that was an initrd made from chrooted /mnt/ folder of slackware bootdisk. Anyway, everything works now ("mkinitrd -c -k 2.6.21.5-smp -m ext3 -f ext3 -r /dev/hdc3"). Problem solved, thanks for the help.
 
Old 07-05-2007, 09:57 AM   #7
Michielvw
Member
 
Registered: May 2005
Location: Leicester,UK
Distribution: Slackware
Posts: 108

Rep: Reputation: 19
most likely the typo. Because you tried to load modules for an "ext" filesystem, instead of ext3. So your kernel is trying to load something, then tries to find your disk that has the rest of the modules/programs/etc, and screams in panic because it can't read the disk.

Glad it's working now
 
Old 07-07-2007, 12:41 AM   #8
hutyerah
Member
 
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware
Posts: 39

Rep: Reputation: 16
Don't you also need the "jbd" module for ext3 to work?
 
Old 07-07-2007, 09:23 AM   #9
ErV
Senior Member
 
Registered: Mar 2007
Location: Russia
Distribution: Slackware 12.2
Posts: 1,202
Blog Entries: 3

Original Poster
Rep: Reputation: 62
Quote:
Originally Posted by hutyerah
Don't you also need the "jbd" module for ext3 to work?
mkinitrd adds all modules required by this one automatically.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
smp kernel: uncompressing Linux ..ok booting the kernel krissb Linux - General 1 11-16-2005 06:31 PM
Booting problem, initrd Drassk Linux - Software 3 03-06-2005 01:56 PM
deb kernel trouble and initrd ssfrstlstnm Debian 8 02-05-2005 08:57 AM
Network trouble with SMP kernel Cerbere Slackware 3 05-10-2004 12:49 AM
hda lost interrupt when booting SMP kernel nitewing98 Linux - Hardware 3 06-19-2003 03:23 AM


All times are GMT -5. The time now is 04:05 AM.

Main Menu
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