Kernel panic after compiling new kernel... help!

Kernel panic after compiling new kernel... help!

Post by Raja Wurttembe » Sun, 07 Feb 1999 04:00:00



This might be a simple problem for someone to answer but I have just
installed Slackware 3.6 and I recompiled my kernel to upgrade from
2.0.35 to 2.0.26. I added my new kernel to lilo so I wouldn't trash my
system. When I rebooted and selected my new kernel it started booting
and loading properly but then it dies with the following error
message:

Kernel panic: VFS: Unable to mount root fs on 08:00

What is this error and how do I recover from it?? Thanks in advance!

Raja Wurttemberg

/* To prevent SPAM my e-mail address been modified */
/* Delete the "x.nospam" to e-mail me. */

 
 
 

Kernel panic after compiling new kernel... help!

Post by Juergen Hein » Sun, 07 Feb 1999 04:00:00



>This might be a simple problem for someone to answer but I have just
>installed Slackware 3.6 and I recompiled my kernel to upgrade from
>2.0.35 to 2.0.26. I added my new kernel to lilo so I wouldn't trash my
>system. When I rebooted and selected my new kernel it started booting
>and loading properly but then it dies with the following error
>message:

>Kernel panic: VFS: Unable to mount root fs on 08:00

08:00 is the 1st SCSI disk ... the *whole* disk, so either you've
got no SCSI at all anyway or it must read ...
08:01, 08:02 or something like that ...
Quote:

>What is this error and how do I recover from it?? Thanks in advance!

...
rdev /boot/vmunix /dev/sda3
... where vmunix is your kernel and sda3 your root device with 1 the
1st partition, 2 the second and so on.

You can do that on the lilo command line already ...
boot: /boot/newkernel root=/dev/sda3
... for instance and the take a look into your lilo.conf too, typo
perhaps.

Cheers,
Juergen

--
\ Real name     : Jrgen Heinzl                 \       no flames      /

  \ Phone Private : +44 181-332 0750              \                  /

 
 
 

Kernel panic after compiling new kernel... help!

Post by Mike Werne » Sun, 07 Feb 1999 04:00:00



> This might be a simple problem for someone to answer but I have just
> installed Slackware 3.6 and I recompiled my kernel to upgrade from
> 2.0.35 to 2.0.26. I added my new kernel to lilo so I wouldn't trash my
> system. When I rebooted and selected my new kernel it started booting

Did you rerun /sbin/lilo after editing lilo.conf and before rebooting?
If not, that is your problem.
--
Mike Werner  KA8YSD           |  "Where do you want to go today?"
ICQ# 12934898                 |  "As far from Redmond as possible!"
'91 GS500E                    |
Morgantown WV                 |

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1

 Y+ R+ !tv b+++(++++) DI+ D--- G e*>++ h! r++ y++++
------END GEEK CODE BLOCK------

 
 
 

Kernel panic after compiling new kernel... help!

Post by Raja Wurttembe » Mon, 08 Feb 1999 04:00:00


Juergen,

I just wanted to let you know that you hit it right on the head! I did
the command line option with the "rdev" command and that fixed the
problem. After I tested the kernel several times I typed:

rdev -R /[kenelname] 1

Just like it says in the "Linux Unleashed (2nd ed.)" book on page 103.
I've had this book for a while and I never even opened it! Auuggh!
hahaha! Thanks again for your help.

-Raja

P.S. I've noticed quite a few people in these Linux newsgroups with
this EXACT problem. I hope some of them read your post.




>>This might be a simple problem for someone to answer but I have just
>>installed Slackware 3.6 and I recompiled my kernel to upgrade from
>>2.0.35 to 2.0.26. I added my new kernel to lilo so I wouldn't trash my
>>system. When I rebooted and selected my new kernel it started booting
>>and loading properly but then it dies with the following error
>>message:

>>Kernel panic: VFS: Unable to mount root fs on 08:00
>08:00 is the 1st SCSI disk ... the *whole* disk, so either you've
>got no SCSI at all anyway or it must read ...
>08:01, 08:02 or something like that ...

>>What is this error and how do I recover from it?? Thanks in advance!
>...
>rdev /boot/vmunix /dev/sda3
>... where vmunix is your kernel and sda3 your root device with 1 the
>1st partition, 2 the second and so on.

>You can do that on the lilo command line already ...
>boot: /boot/newkernel root=/dev/sda3
>... for instance and the take a look into your lilo.conf too, typo
>perhaps.

>Cheers,
>Juergen

 
 
 

1. compiling ANY new kernel gives "Kernel Panic"...HELP!

Can someone out there help me?  I've been compiling new kernels for a while now
but I can't compile any newer or older ones right now.  I've been running
1.3.25 for a long time now.  Here's what happens:

1.  I compile a new kernel just fine and re-lilo.  But when I reboot into the
        new kernel, it just gives me a kernel panic saying it can't find the
        root device.

2.  I've done an rdev on them and they all think my root partition is where it
        actually is.  So why can't any of the others find it, yet the old kernel
        (1.3.25) will.

Here's what rdev outputs:

  {area1s24:/} /sbin/rdev vmlinuz
  Root device /dev/hdb3
  {area1s24:/} /sbin/rdev vmlinuz.new
  Root device /dev/hdb3

Please help!

                                                        Thanks,

                                                        Michael

--
Michael David Knight           God wanted man                  \    /
Georgia Tech (404)206-0194     to fly, that's              _____-/\-_____
Aerospace Engineering          why he invented                 \_\/_/    

2. What technology for Web apps?

3. kernel panic on a 2.2.5 kernel new compile

4. Frequently Asked Questions about Unix - with Answers [Monthly posting]

5. Help!I just compiled kernel 2.0.1 and now I get a kernel panic!

6. BAD!=32bit+per.swap++-+&&+notebook1100

7. Help meeee!!I just compiled kernel 2.0.1 and now I get a kernel panic!!

8. req: best/recommended ATA100 controller on 2.2.xx or 2.4.xx

9. Help!I just compiled kernel 2.0.1 and now I get a kernel panic!!

10. Help!I just compiled kernel 2.0.1 and now I get a kernel panic!

11. Problems when boot new kernel 2.5.66 kernel panic

12. Kernel panic on running newely compiled kernel

13. I just compiled kernel 2.0.1 and now I getr a kernel panic!