Results 1 to 5 of 5

Thread: kernel panic after kernel update

  1. #1
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    3

    Default kernel panic after kernel update

    I've followed hxxp://forums.remote-exploit.org/showpost.php?p=79341&postcount=1 guide to upgrade the kernel, everything worked fine... although now when i boot with the new kernel i get:

    kernel panic - not syncing : VFS: unable to mount root FS on unknown-block

    my lilo.conf is this:
    Code:
    lba32
    boot = /dev/sda
    prompt
    timeout = 60
    change-rules
    reset
    vga = 788
    
    #images begin
    
    image = /boot/vmlinuz-old
    root = /dev/sda8
    label old
    
    image = boot/vmlinuz
    root = /dev/sda8
    label = new
    read-only
    
    #windows
    
    other = /dev/sda1
    label = windows
    table = /dev/sda
    can someone point me in the right direction?

  2. #2
    Member
    Join Date
    Sep 2008
    Posts
    306

    Default

    This problem was already discussed on the forums:

    Add this to your lilo.conf:
    Code:
    append = ”rootdelay=10”
    Here the associated thread:
    http://forums.remote-exploit.org/sho...ghlight=append
    Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

    * post your question to a forum where it's off topic
    * post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
    * cross-post to too many different newsgroups
    * post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem

  3. #3
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    3

    Default

    done that... didnt solved the problem... :\

    edit: is it possible that on the new kernel my partition is hda8 and not sda8?

  4. #4
    Member
    Join Date
    Sep 2008
    Posts
    306

    Default

    Quote Originally Posted by Suthi View Post
    done that... didnt solved the problem... :\
    After you edited your lilo.conf, you did also re-run "lilo -v" with root privileges?
    If so, search for "kernel panic" there are some other advices to solve this problem.
    Be sensitive in choosing where you ask your question. You are likely to be ignored, or written off as a loser, if you:

    * post your question to a forum where it's off topic
    * post a very elementary question to a forum where advanced technical questions are expected, or vice-versa
    * cross-post to too many different newsgroups
    * post a personal e-mail to somebody who is neither an acquaintance of yours nor personally responsible for solving your problem

  5. #5
    Just burned his ISO
    Join Date
    Aug 2008
    Posts
    3

    Default

    Quote Originally Posted by terminal86 View Post
    After you editet your lilo.conf, you did also re-run "lilo -v" with root privileges?
    If so, search for "kernel panic" there are some other advices to solve this problem.
    yes of i did lilo -v

    although check the edit i've done on my previous post!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •