Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 15
hi everybody, i have compiled the 2.6.10 kernel and there were no errors while compiling. when i restart and boot the new version i get the message: Code: VFS: Cannot ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Jan 2005
    Location
    madrid
    Posts
    9

    kernel 2.6.10 panic: not syncing: VFS: ...


    hi everybody,

    i have compiled the 2.6.10 kernel and there were no errors while compiling. when i restart and boot the new version i get the message:

    Code:
    VFS: Cannot open root device "hdc2" or unknown-block(0,0)
    Please append a correct "root=" boot option
    kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
    hdc2 is the correct partition and i guess menu.lst (grub) is ok:

    Code:
    title        Debian GNU/Linux, kernel 2.6.10
    root        (hd0,1)
    kernel     /boot/vmlinuz-2.6.10 root=/dev/hdc2 ro
    initrd       /boot/initrd.img-2.6.8-2-386
    savedefault
    boot
    i compiled this way:

    Code:
    make-kpkg clean
    make-kpkg --revision=786:linux-2.6.10 kernel_image
    then i did:

    Code:
    dpkg -i kernel-image-2.6.10_MyKernel2.6.10_i386.deb
    finally i take a look of my menu.lst and it looks like i show you above.

    what can be gone wrong?
    skotperez[/list]

  2. #2
    Linux Guru Flatline's Avatar
    Join Date
    Feb 2005
    Posts
    2,204
    It looks like you're using the initrd.img from your old kernel in that boot configuration.
    There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.

    - Jeremy S. Anderson

  3. #3
    Just Joined!
    Join Date
    Jan 2005
    Location
    madrid
    Posts
    9
    in grub i added the line

    Code:
    initrd       /boot/initrd.img-2.6.8-2-386
    because i have no initrd.img-2.6.10... or i haven't found in anyplace. i guess it would be save in /boot like the others.

    maybe i did something wrong during the compilation and make doesn't create init.rd-2.6.10...[/code]

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Feb 2005
    Location
    UK
    Posts
    20
    I am getting the exact same error, and I am sorry but I still havent sussed it out. what is getting me is succesfully copying the new image over the old one, in order to make the new bzimage, bootable. Help anyone

  6. #5
    Linux Guru Flatline's Avatar
    Join Date
    Feb 2005
    Posts
    2,204
    Waryreacter: You shouldn't have to copy the new image over the old one...they can exist in the same directory as long as their filenames are different. You just have to specify the new image in your bootloader.

    Skotperez: Try:

    Code:
    cp /usr/src/linux-2.6.10/System.map /boot/System.map-2.6.10
    mkinitrd -o /boot/initrd-2.6.10 /lib/modules/2.6.10
    I think that will make an initrd image for you.
    There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.

    - Jeremy S. Anderson

  7. #6
    Just Joined!
    Join Date
    Jan 2005
    Location
    madrid
    Posts
    9
    thanks a lotk, Flatline.

    your solution works!!
    i think that the way i compiled didn't create the initrd image. why? or maybe it was anything in relation with 2.6.10 kernel. what do you think?

    skotperez

  8. #7
    Linux Guru Flatline's Avatar
    Join Date
    Feb 2005
    Posts
    2,204
    I think it's just one of the many options in your config (although I haven't compiled a kernel from scratch in probably a year, so don't hold me to that)...there's so many that it's easy to miss one.
    There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.

    - Jeremy S. Anderson

  9. #8
    Just Joined!
    Join Date
    May 2005
    Posts
    4
    hi i had recompiled the kernel with 2.6.11 , everything went fine while installing but in the end it has shown so many dependencies. after i restarted my machine through new kernel it got strucked giving
    "Mounting root file System
    mount : error 19 mounting ext3
    pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed:2
    umount /initrd/proc failed: 2
    Freeing unused kernel memory : 268k freed
    Kernel panic - not syncing: No init found . Try passing init = option to kernel "
    I tried the above procedure it didn't wrk
    for "mkinitrd -o /boot/initrd-2.6.10 /lib/modules/2.6.10"
    it had accepted only "mkinitrd /boot/initrd-2.6.11.img 2.6.11" and given 2.6.11 is already there .

    CAn any one could help me to recttify this problem.

  10. #9
    Linux Guru Flatline's Avatar
    Join Date
    Feb 2005
    Posts
    2,204
    So you have created an initrd.img file? Is it specified to load in your bootloader config?
    There are two major products that come out of Berkeley: LSD and UNIX. We don't believe this to be a coincidence.

    - Jeremy S. Anderson

  11. #10
    Just Joined!
    Join Date
    May 2005
    Posts
    4
    "cp /usr/src/linux-2.6.11/System.map /boot/System.map-2.6.11"
    it copied tht system.map-2.6.11 to boot
    after that
    " mkinitrd /boot/initrd-2.6.11.img 2.6.11"
    this option it took but given tht 2.6.11 is already there

    i am new to this i don't know rather than the above
    Help me what is initrd??? what 's the purpose of tht??

Page 1 of 2 1 2 LastLast

Posting Permissions

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