HELP: New kernel won't boot

HELP: New kernel won't boot

Post by Ohmste » Sun, 21 Oct 2001 13:40:01



I know that this is a networking group and if I can't get my new kernel
to boot, then I can't network. (Hows that for sneeking this question in?
<grin>)

I use Red Hat 7.1 on my system and it always works good, especially with
a little help now and then from this group. Been using kernel 2.4.3-12
and I got an email notice from Red Hat to update to kernel 2.4.9-6 and to
use the update agent to do this. So I went ahead and updated all kernel
files. Problem is the kernel won't boot at all. The last time I did this
to 2.4.3-12, I had a problem like this but used mkinitrd to make an image
file and put the root=/dev/hdb6 part into lilo.conf and then ran lilo
again. (Had to recompile the nvidia drivers again but this is not
related, just had to do it to make the driver work with new kernel.)

I tried doing these steps again only this time it did not help. I still
get a kernel panic and then cannot do anything.

Can somebody please, please help to figure out what the problem is and
how to fix it?

Tail of boot messages:
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
EXT2-fs: Unable to read superblock
isofs_read_superblock: bread failed, dev=09:02, iso_blknum=16, block=32
Kernel panic: VFS: Unable to mount fs on 09:02

...what in the heck does all that *mean? I can still boot to 2.4.3-12
because the lilo.conf file has that as linux.bak and it still works but
booting to "linux" is out now. I never saw this kind of problem before
and have no idea as to how to fix it? Where in the heck did "dev=9:02"
come from? Will paste in lilo.conf if it helps here. Tried to run "make
xconfig" from the /usr/src/linux-2.4.9-6 directory and it fails now. Will
not even bring up the xconfig window anymore. Get a make error with just
trying to get xconfig up.

Here is lilo.conf:

boot=/dev/hda
map=/boot/map
install=/boot/boot.b
prompt
timeout=50
message=/boot/message
linear
default=xp

other=/dev/hda1
        optional
        label=xp

image=/boot/vmlinuz-2.4.3-12
        label=linux.bak
        root=/dev/hdb6
        read-only
        initrd=/boot/initrd-2.4.3-12.img

image=/boot/vmlinuz-2.4.9-6
        label=linux
        root=/dev/hdb6
        read-only
        initrd=/boot/initrd-2.4.9-6.img
        optional

image=/boot/vmlinuz-2.4.9-6BOOT
        label=linux-BOOT
        read-only
        optional

...and if it helps, dir listing of /boot directory:

drwxr-xr-x    4 root     root         1024 Oct 19 23:25 .
drwxr-xr-x   20 root     root         4096 Oct 20 00:34 ..
-rw-r--r--    1 root     root          512 Jul  8 12:02 boot.0300
-rw-r--r--    1 root     root         5824 Feb 23  2001 boot.b
-rw-r--r--    1 root     root          612 Feb 23  2001 chain.b
-rw-r--r--    1 root     root       368358 Jul  8 12:02 initrd-2.4.2-2.img
-rw-r--r--    1 root     root       362366 Jul  8 19:04 initrd-2.4.3-12.img
-rw-r--r--    1 root     root       262458 Oct 19 23:26 initrd-2.4.9-6.img
lrwxrwxrwx    1 root     root           14 Oct 19 22:30 kernel.h -> kernel.h-2.4.9
-rw-r--r--    1 root     root          405 Oct 19 22:30 kernel.h-2.4.9
drwxr-xr-x    2 root     root        12288 Jul  8 11:47 lost+found
-rw-------    1 root     root        37888 Oct 19 22:31 map
-rw-r--r--    1 root     root        23108 Feb 23  2001 message
lrwxrwxrwx    1 root     root           19 Oct 19 22:30 module-info -> module-info-2.4.9-6
-rw-r--r--    1 root     root        13598 Jun  8 15:32 module-info-2.4.3-12
-rw-r--r--    1 root     root        13598 Oct 18 09:47 module-info-2.4.9-6
-rw-r--r--    1 root     root          640 Feb 23  2001 os2_d.b
lrwxrwxrwx    1 root     root           19 Oct 19 22:49 System.map -> System.map-2.4.3-12
-rw-r--r--    1 root     root       227071 Apr  8  2001 System.map-2.4.2-2BOOT
-rw-r--r--    1 root     root       428192 Jun  8 15:32 System.map-2.4.3-12
-rw-r--r--    1 root     root       437772 Oct 18 09:47 System.map-2.4.9-6
-rw-r--r--    1 root     root       257963 Oct 18 09:07 System.map-2.4.9-6BOOT
drwxr-xr-x    2 root     root         1024 Oct 19 23:25 .Trash-root
-rwxr-xr-x    1 root     root      1746520 Apr  8  2001 vmlinux-2.4.2-2BOOT
-rwxr-xr-x    1 root     root      2178832 Jun  8 15:32 vmlinux-2.4.3-12
lrwxrwxrwx    1 root     root           15 Oct 19 22:30 vmlinuz -> vmlinuz-2.4.9-6
-rw-r--r--    1 root     root       652144 Apr  8  2001 vmlinuz-2.4.2-2BOOT
-rw-r--r--    1 root     root       796703 Jun  8 15:32 vmlinuz-2.4.3-12
-rw-r--r--    1 root     root       979046 Oct 18 09:47 vmlinuz-2.4.9-6
-rw-r--r--    1 root     root       670847 Oct 18 09:07 vmlinuz-2.4.9-6BOOT

Sombody please help me get to booting in the new kernel.
TIA
~Ohmster

 
 
 

HELP: New kernel won't boot

Post by Eric P. McC » Sun, 21 Oct 2001 14:15:18



> Kernel panic: VFS: Unable to mount fs on 09:02

I have no idea what device that is, but it sure isn't in my /dev.

/dev/hdb6 is 3,70 on my system.  Are you trying to use devfs?  If so,
you need to give a root like /dev/discs/disc1/part6... although I
don't think devfs would cause this sort of oddity.

Regardless, you might try booting with devfs=nomount just to confirm
this isn't the problem.

--

"I woke up this morning and realized what the game needed: pirates,
pimps, and gay furries."  - Rich "Lowtax" Kyanka

 
 
 

HELP: New kernel won't boot

Post by Dean Thompso » Sun, 21 Oct 2001 19:27:40


Hi!,

Quote:> I use Red Hat 7.1 on my system and it always works good, especially with
> a little help now and then from this group. Been using kernel 2.4.3-12
> and I got an email notice from Red Hat to update to kernel 2.4.9-6 and to
> use the update agent to do this. So I went ahead and updated all kernel
> files. Problem is the kernel won't boot at all. The last time I did this
> to 2.4.3-12, I had a problem like this but used mkinitrd to make an image
> file and put the root=/dev/hdb6 part into lilo.conf and then ran lilo
> again. (Had to recompile the nvidia drivers again but this is not
> related, just had to do it to make the driver work with new kernel.)

What option are you typing into lilo to get the new kernel image to load ?
Did you do a: "make modules" and "make modules_install" as well ?
Finally, I presume the kernel was compiled on the machine which is having the
booting problems ?

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

HELP: New kernel won't boot

Post by Dean Thompso » Sun, 21 Oct 2001 22:18:26


Hi!,

Quote:> Negative. Kernel was not compiled locally. Red Hat does the rpm installs.
> Update agent in Red Hat downloaded the kernel, source, headers, etc., and
> installed the kernel itself like it did last time. These precompiled
> kernels always worked good untill this time. I see that I no longer have
> kernel source for 2.4.3-12 anymore, only a dead sym link from
> linux---->2.4.3-12 in the /usr/src directory (/usr/src/2.4.3-6 does not
> exsist anymore.). Make xconfig does not come up anymore.

> Can boot to the old kernel 2.4.3-12 but I doubt I can compile anymore
> because the kernel source and headers are gone now and replaced with a
> useless 2.4.9-6 source. System runs good with old kernel though.

> What would you recommend to get out of this mess? Use rpm to uninstall the
> 2.4.9-6 packages and look for the 2.4.3-12 headers and source, install
> those again to get my compiles to work again? Download the 2.4.9-6 rpm src
> package and do a "rpm --rebuild" on it to make a new kernel or just do the
> "configure, make, make dep, make install" stuff? Grab the tarball and do it
> that way? (ugh!) What is a good, recent kernel to use?

Personally, I would grab the kernel source code myself, and do my own compile
and install.  I normally don't trust automatic kernel updates, better to see
and do it myself.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

HELP: New kernel won't boot

Post by Karl Heye » Sun, 21 Oct 2001 22:44:42





>> Kernel panic: VFS: Unable to mount fs on 09:02

> I have no idea what device that is, but it sure isn't in my /dev.

hmmm. it's the scsi tape on my system st2,  so I suspect the root parameter
need setting up

linux root=/dev/hd<xy>    where x is the disk and y is the partition.

karl.

 
 
 

HELP: New kernel won't boot

Post by Dean Thompso » Sun, 21 Oct 2001 23:05:31


Hi!,




> >> Kernel panic: VFS: Unable to mount fs on 09:02

> > I have no idea what device that is, but it sure isn't in my /dev.

> hmmm. it's the scsi tape on my system st2,  so I suspect the root parameter
> need setting up

> linux root=/dev/hd<xy>    where x is the disk and y is the partition.

Ohmster's problem is that he has installed a precompiled kernel which seems to
have the wrong rdev settings for the root device.  Either issuing a rdev
command to reset it, or doing a recompile rather than using a precompiled
kernel should solve the problem.

See ya

Dean Thompson

--
+____________________________+____________________________________________+

| Bach. Computing (Hons)     | ICQ     - 45191180                         |
| PhD Student                | Office  - <Off-Campus>                     |
| School Comp.Sci & Soft.Eng | Phone   - +61 3 9903 2787 (Gen. Office)    |
| MONASH (Caulfield Campus)  | Fax     - +61 3 9903 1077                  |
| Melbourne, Australia       |                                            |
+----------------------------+--------------------------------------------+

 
 
 

HELP: New kernel won't boot

Post by Ohmste » Mon, 22 Oct 2001 02:17:41




Quote:> hmmm. it's the scsi tape on my system st2,  so I suspect the root
> parameter need setting up

> linux root=/dev/hd<xy>    where x is the disk and y is the partition.

> karl.

Karl,

Showed you the lilo.conf file in original post:

image=/boot/vmlinuz-2.4.9-6
        label=linux
        root=/dev/hdb6
        read-only
        initrd=/boot/initrd-2.4.9-6.img
        optional

...is that what you mean? This is a precompiled Red Hat kernel. Never had a
problem with them before but sure am having one now.

~Ohmster

 
 
 

HELP: New kernel won't boot

Post by Ohmste » Mon, 22 Oct 2001 02:44:03


..oh I feel like such an idiot. After I made an initrdrd image for the
new kernel and specified the root path in lilo.conf, I never ran lilo
since doing that. Am I retarded or what? <shrug>

That is what was wrong with the new kernel. Apparently Red Hat cannot
build a kernel to suite every configuration and some user setup is
required.

Okay, how about this one?
"make xconfig" still does not work, can someone give me a pullup as to
why it fails? Screendump enclosed below.
~Ohmster
P.S. Thank you to all that tried to help.


rm -f include/asm
( cd include ; ln -sf asm-i386 asm)
make -C scripts kconfig.tk
make[1]: Entering directory `/usr/src/linux-2.4.9-6/scripts'
cat header.tk >> ./kconfig.tk
./tkparse < ../arch/i386/config.in >> kconfig.tk
drivers/net/Config.in: 278: unknown command
make[1]: *** [kconfig.tk] Error 1
make[1]: Leaving directory `/usr/src/linux-2.4.9-6/scripts'
make: *** [xconfig] Error 2


> hmmm. it's the scsi tape on my system st2,  so I suspect the root
> parameter need setting up

> linux root=/dev/hd<xy>    where x is the disk and y is the partition.

> karl.

 
 
 

HELP: New kernel won't boot

Post by Karl Heye » Mon, 22 Oct 2001 03:25:42




> ..oh I feel like such an idiot. After I made an initrdrd image for the new
> kernel and specified the root path in lilo.conf, I never ran lilo since
> doing that. Am I retarded or what? <shrug>

easily done, bootloaders like the one used in mandrake IIRC grub helps as it
doesn't need the lilo re-running.

Quote:> That is what was wrong with the new kernel. Apparently Red Hat cannot build
> a kernel to suite every configuration and some user setup is required.

It's not a kernel issue, it's the linkage from the BIOS to starting the
kernel.

Quote:> Okay, how about this one?
> "make xconfig" still does not work, can someone give me a pullup as to why
> it fails? Screendump enclosed below. ~Ohmster P.S. Thank you to all that
> tried to help.

That problem is a TK issue, line 278 o fthe tkparse program, what I don't
know is if the RH specific kernel differs from the normal kernel wrt that
file, see if there is anything obviously wrong.  Failing that run make
menuconfig as an alternative.  Check that the TK/TCL packages are uptodate
for the kernel build, that could be another reason for failing.

karl.

 
 
 

HELP: New kernel won't boot

Post by Ohmste » Mon, 22 Oct 2001 14:07:13




Quote:> That problem is a TK issue, line 278 o fthe tkparse program, what I
> don't know is if the RH specific kernel differs from the normal kernel
> wrt that file, see if there is anything obviously wrong.  Failing that
> run make menuconfig as an alternative.  Check that the TK/TCL packages
> are uptodate for the kernel build, that could be another reason for
> failing.

> karl.

Will check this out Karl, thanks for the help.
~Ohmster
 
 
 

1. Help: Trouble recompiling kernel, won't boot from new Kernel

I have two linux machines: one is an IDE system and the other is SCSI.

On the IDE machine, I have just upgraded from Kernel 1.2.11 to 1.2.13.
I got a new kernel source and renamed the old kernel directory tree to
something like linux.old. then I went through the entire proceedure:

make config
make dep
make clean
make zImage

after the compile I did :

cd /usr/src/linux/arch/i386/boot
rdev -R zImage 1
rdev -v zImage -1
rdev zImage /dev/hda2
fdformat /dev/fd0H1440
cat zImage > /dev/fd0H1440

Everything *seemed* to work fine. BUT when I tried to boot off of the
hard disk and not the floppy, it clearly came up with Kernel 1.2.11,
which was the old one. When I booted from the floppy, it came up with
kernel 1.2.13, which was the new one .

There must be an additional step to set LILO to boot from the new
kernel, but I can find nothing about it in the documentation.

Also, with my SCSI machine, I have loaded linux for the first time. I
went through the whole proceedure and recompiled the kernel just as
above, with my other machine.

The problem is that when I boot up the system goes into AUTOPROBE. It
taked about 7 minutes for this to complete before the system fully
boots. I went through the recompile process again and was very careful
to NOT include the following step which looked suspicious to me:
"Probe all LUNs on each SCSI device".

I can boot from the hard disk without this happening. I am now
suspicious that I am not really booting from the recompiled kernel.

Please help

thank you

Tom


2. database login

3. New kernel won't boot

4. Using linux for a course?

5. Linux won't boot after installing new kernel...

6. scanout

7. Lilo won't boot after new kernel

8. Win modem under Linux ???

9. new kernel won't boot: Wrong loader, giving up

10. new kernel build won't boot

11. New kernel won't boot - how do I find out why?

12. New kernel won't boot