Help answer threads with 0 replies.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!


  Search this Thread
Old 06-12-2004, 07:11 AM   #1
Registered: Jun 2004
Posts: 40

Rep: Reputation: 15
boot failure with RH9 2.6.6 - mount: error 19 mounting ext3

I've built 2.4.20 and 2.4.25 a dozen times with no problem, and booted the
various versions with grub also (mostly :-) without problems. This is all on

But trying 2.6.6 has not gone so well. I built 2.6.6 by
load the tar
copy over the .config from 2.4
make oldconfig (take the default on all new options)
make modules modules_install install (all no problem)
grub config line matches what I've used for 2.4 (/boot is hdb1, / is hdb2)
root (hd0,0)
kernel /vmlinuz-2.6.6 ro root=/dev/hdb2
initrd /initrd-2.6.6.img

but booting 2.6.6 blows out with

VFS: Mounted root (ext2 filesystem).
Red Hat nash version 3.4.32 starting
Mounting /proc filesystem
Creating block devices
Creating root device
Mounting root filesystem
mount: error 19 mounting ext3
pivorroot: pivot_root(/sysroot,/sysroot/initd) failed: 2

Since 19 is "no such device", then it can't find /dev/hdb2? If I add a showlables in
linuxrc both 2.4 and 2.6 seem to have the same view of devices and I assume the
mkrootdev worked the same in both, but hard to check with no ls.

Also I don't grok whats going on in linuxrc where just after the
mkrootdev /dev/root
there is
echo 0x100 >/proc/sys/kernel/real-root-dev,
how can this be 0x100 if this is supposed to be major*256+minor, but it works in 2.4
this way so...??

Anyway if this all rings a bell I'd love to hear about it. I've seen lots of "init not found" errors
discussed, and this does end up that way as well, but this device confusion seems the root cause.

update: I added /bin/ls and its libs to my initrd..img file and added a ls -l /dev/root /dev/hdb2
to linixrc just before it attempts the mount and it shows the both are the same (and correct) major/minor so this devices DOES exist. ext3 is configured. what else is likely to be generatring this error?

Last edited by jg167; 06-12-2004 at 10:26 PM.
Old 06-12-2004, 10:42 PM   #2
Registered: Jun 2004
Posts: 40

Original Poster
Rep: Reputation: 15
So this looks to be a RH9 2.6.6 module issue. (not confirmed but certainly looks like it as ext3 was configured as a module).

1) It seems perfetly reasonable that the kernel would build with an incompatible module environment on the build system, since you could be targeting a different system. So two could you be altering the boot setup such that even the make install does not know for sure this will fail, but its a good guess so I'd vote for making the make FAIL at this point and have an override to ignore this failure mode. i.e. its just too easy to hit this.

2) I'm skeptical of the related issue mentioend in the halloween-2.6.txt doc pertaining to RedHat's rc.sysinit . That doc mentions that since /proc/ksyms does not exist in 2.6 you must modified the script to force /proc/sys/kernel/modprobe to be "/sbin/modprobe". However the srcipt actually tests /proc/ksyms early on and uses it to set USEMODULES which is in turn used several places. Thus it seems what you really need to do is to force USEMODULES="y" and that in turn will cause the modprobe pointer to be setup.

3) It is not yet clear to me if I install the new module-init-tools (as the make file warned me about, but I just didn't notice, i.e. point 1 above) if this will screwup my ability to boot 2.4 (i.e. then I'd be screwed if 2.6 also does not come up)

4) The kernel not being able to load a module resulting in error 19 (no such device) seems pathetic (the ying and yang of linux from my point of view, its still such a hack in many ways, but I couldn't be doing this project without it either!).

All of which is as yet unverified (I'm building a monolithic 2.6.6 kerenl as the easiest way to check this out), but since I appear to be answering my own questions on this one, I thought I'd add the current theory.
Old 06-13-2004, 04:00 AM   #3
Registered: Jun 2004
Posts: 40

Original Poster
Rep: Reputation: 15
Yep, modules was the issue. If I build a no-modules kernel 2.6.6 does boot. A few points on doing so
1) make install will look like it failes with an error about /lib/modules/<kernelname> not existing, but it installs the kernel in /boot anway.
2) you need to add the "nomodules" parm to the kernel line for grub so it now reads kernel /vmlinuz-mumble nomodules ro root=/dev/<root partitoin>
3) not having moduels disables the runing log of OK or FAIL when you come up (not clear why) but it did boot. So it looks like it is dead right off the bat, but the disk is still going crazy so just wait and then X comes up.

Now on to see if the new init-module-tools will work and hopeful not kill 2.4 (but now at least I have a moduless kernel to fall back on if it does).
Old 06-13-2004, 04:10 AM   #4
LQ Guru
Registered: Aug 2003
Location: Sydney, Australia
Distribution: Gentoo
Posts: 1,796

Rep: Reputation: 47
If you read the module-init-tools documentation it mentions something about "make moveold", which renames your current modutils(for 2.4) to *.old, and they'll be used whenever you boot a 2.4 kernel.
Also if you're going to use an initrd (eg you compile ide chipset/filesystem support as modules)make sure you have the latest mkinitrd

this is a good guide on upgrading to 2.6 in rh9:

Last edited by Demonbane; 06-13-2004 at 04:13 AM.
Old 06-13-2004, 05:14 AM   #5
Registered: Jun 2004
Posts: 40

Original Poster
Rep: Reputation: 15
Thanks for the tips (the hoops I jump through to try and get 802.11g working..., which I did not mange to do in 2.4.25 but looks more promising in 2.6.6).
Old 06-15-2004, 04:28 AM   #6
Registered: Jun 2004
Posts: 40

Original Poster
Rep: Reputation: 15
2.4 / 2.6 compatible rc.sysinit

As a final postscript on this issue, since the various goodies you need to update in RH9 with 2.4 to get 2.6 running seem backward compatbile (e.g. new glibc and its fellows, module-init-tools) I thoiught it would be handy to have a /etc/rc.d/rc.sysint and /etc/rc.d/init.d/halt that would do the right 4 or 5 things for either kerenl, so I made one. You can get them here. It seems to work for me between 2.4.25 and 2.6.6 but of course use at your own risk.

Last edited by jg167; 06-15-2004 at 04:30 AM.


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
error mounting ext3 filesystem... mount: /dev/hdd1: can't read superblock versaulis Linux - Software 5 11-26-2006 09:34 PM
Mount : error 6 mounting ext3.. and kernal panic Asificare Mandriva 2 01-15-2005 04:31 PM
mount: error 6 mounting ext3 an0nym0us Linux - General 4 03-31-2004 09:37 AM
Kernel won't boot.. error mounting ext3 SirRobbin Linux - Newbie 2 07-24-2003 08:18 AM
mount: error 6 mounting ext3 cknaresh Linux - Newbie 2 11-18-2002 07:35 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 03:56 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