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..

Thanks!

hello slacken,

i had *exactly* the same problem as you when i recompiled my suse 8.2 kernel last week. thankfully, after posting some questions here and on other forums, i was rewarded with a helpful answer which worked, and which also made sense.

here's the problem:

reiserfs support is loaded as a module; however, the module is stored on your root (reiser) filesystem - bit of a catch 22!

so what you need to do is make a startup ram disk. different distros use different tools for this - with red hat and its derivatives, it's mkinitrd, i don't know about slackware..

anyway, hope gives you the general idea.

Hmm. I must say I'm not with you.. is Reiserfs loaded as a module even if you specify it to be built-in when you compile a new kernel?

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 mi know, if this worked fine.