Latest LQ Deal: Linux Power User Bundle
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 01-29-2004, 09:47 AM   #1
Registered: Nov 2003
Location: Finland
Distribution: Slackware current
Posts: 46

Rep: Reputation: 15
Kernel compile -> cannot boot reiserfs root

Well, the problem is that the new kernel I have compiled doesn't want to boot my reiserfs root. The kernel panics saying it is unable to open root on hda6, which is my root. I have tried to search the net and LQ for an answer to my dilemma, but no luck even if this seems to be a quite common problem.

There are some things I would like to get straightend out:

1. Even if you are only using Reiserfs partitions, do you have to include ext2/3 or maybe some other stuff when you compile?

2. Can the "unable to open.." problem be related to IDE drivers or something related to the manufacturer of the drive?

3. Does size matter? My hd is 80GB and I came across some option dealing with the 32GB limit, but I cannot remember what it said..does anyone know what this is?

I have a PIII 500, Abit 440BX chipset, matrox g400 and an 80GB IBM 120GXP if this might help.

I would be very grateful if someone can explain at least some aspects of this problem as it seems the problem can have _many_ solutions when you are reading the threads here..

Old 01-29-2004, 10:54 AM   #2
Registered: Dec 2003
Distribution: Gentoo
Posts: 66

Rep: Reputation: 15
You probably have reiserfs support compiled as a module, you should build it into the kernel instead of making a module if you want to boot from a reiserfs partition
Old 01-29-2004, 11:07 AM   #3
Registered: Nov 2003
Location: Finland
Distribution: Slackware current
Posts: 46

Original Poster
Rep: Reputation: 15
No, I have it built-in. Any other ideas?
Old 01-29-2004, 04:49 PM   #4
Registered: Nov 2003
Distribution: slackware 14
Posts: 542

Rep: Reputation: 33
can you post your lilo.conf file ?
Old 01-29-2004, 05:40 PM   #5
LQ Newbie
Registered: Jan 2004
Location: Poland
Posts: 3

Rep: Reputation: 0
Hi, everybody!
As far as I know, this problem arises from the fact, that ReiserFS, when mounted, is trying to keep some small parts of files ("file tails") - as it's described in the "mount" manual. Therefore I suggest using "notail" option wchich should be added to the /etc/fstab file. Please, let me know, if this worked fine.
Old 01-29-2004, 06:11 PM   #6
Registered: Jan 2003
Location: Philly, PA
Distribution: Slackware 10.2
Posts: 97

Rep: Reputation: 15
i was about to reccomend the same thing i have my /root partition as reiserfs, you should make sure that in your /etc/fstab you have noatime as an option, and also notail.

thats what i remember reading in a manual for gentoo that said if you are going to use reiserfs you need to include those options. if you google it i am sure you will find plenty of info on gettin it to boot correctly. oh yeah make sure that the partition is flagged as bootable in fdisk, or cfdisk.
Old 01-30-2004, 03:47 AM   #7
Amigo developer
Registered: Dec 2003
Location: Germany
Distribution: Slackware
Posts: 4,895

Rep: Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571Reputation: 571
You should keep support for ext2 in the kernel and have the e2fsutils installed, since e2fsck is run during boot-up. If it's not present the boot process stops, even if you are using other fs than ext2.
Shouldn't be any problem with HD size limits. Linux will work with drives over 200GB. One thing to realize is that, unlike Windows, Linux doesn't really use many of the BIOS calls. It does most of it's work through direct hardware calls, bypassing the BIOS.
Old 01-30-2004, 09:23 AM   #8
Senior Member
Registered: Sep 2002
Location: Arizona, US, Earth
Distribution: Slackware, (Non-Linux: Solaris 7,8,9; OSX; BeOS)
Posts: 1,152

Rep: Reputation: 49
e2fsck is only run if it's necessary. If you read the /etc/rc.d/rc.S, you'll see that the command run is actually fsck. This figures out what filesystem is being checked and does the Right Thing (tm). Not only that, but the freeze is occurring before "init 1", so he never gets to fsck his filesystem.

I run my root on reiserfs, and don't have anything but "defaults" for mounting. The error is likely to be in your /etc/lilo.conf (or in your initrd, if you're using that--man mkinitrd or read the docs for your bootsplash scripts to figure out how to create a usable initrd).
Post the contents of /etc/lilo.conf

I know you compiled in reiserfs support, but double check anyway. I've made the mistake of thinking something important was static, when it was, in fact, a module.


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
reiserfs invalid module format after kernel compile Phyrexicaid SUSE / openSUSE 4 09-22-2005 02:51 AM
compile 2.6.7 kernel and root=LABEL=/ not work? robert.china Fedora 3 07-06-2004 05:05 AM
VFS: not seeing root '/' as reiserfs only ext2 /boot kernel 2.6.5 mus335 Slackware 7 04-24-2004 09:06 PM
kernel compile: reiserfs module error geniarse Linux - Software 2 04-04-2004 06:37 PM
Kernel Compile Boot Loader? boot disk? SPMcRuube Linux - Newbie 3 12-03-2002 08:02 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:29 PM.

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