Find the answer to your Linux question:
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
i just compiled the latest 2.6.20 kernel on my FC5 box ...but am getting kernel panic on rebooting with the new kernel...i get the following error messages Unable to access ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Unhappy kernel panic


    i just compiled the latest 2.6.20 kernel on my FC5 box ...but am getting kernel panic on rebooting with the new kernel...i get the following error messages

    Unable to access resume device(LABEL=SWAP-sda10)
    mount : could not find filesystem '/dev/root'
    setuproot : mounting /dev failed:no such file or directory
    setuproot : error mounting /proc:no such file or directory
    setuproot : error mounting /sys failed:no such file or directory
    switchroot: mount failed
    kernel panic - not syncing: attempted to kill init

    moreover when i select my old kernel at the grub prompt it boots fine..its just the new kernel...any help would be greatly appreciated ..thanks....

  2. #2
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Unhappy

    i am not sure if i did the mkinitrd right...this is what i did...

    mkinitrd /boot/initrd-2.6.20.img 2.6.20

    fdisk -l shows this...
    /dev/sda1 * 1 1912 15358108+ 7 HPFS/NTFS
    /dev/sda2 1913 19456 140922180 f W95 Ext'd (LBA)
    /dev/sda5 1913 7649 46082421 7 HPFS/NTFS
    /dev/sda6 7650 12111 35840983+ 7 HPFS/NTFS
    /dev/sda7 12112 16573 35840983+ 7 HPFS/NTFS
    /dev/sda8 16574 17848 10241406 b W95 FAT32
    /dev/sda9 17849 17861 104391 83 Linux
    /dev/sda10 17862 17990 1036161 82 Linux swap / Solaris
    /dev/sda11 17991 19456 11775613+ 83 Linux

  3. #3
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Unhappy

    output of my fstab file

    [root@localhost ~]# cat /etc/fstab
    LABEL=/ / ext3 defaults 1 1
    LABEL=/boot /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    LABEL=SWAP-sda10 swap swap defaults 0 0

  4. $spacer_open
    $spacer_close
  5. #4
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    post the contents of grub.conf file.
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  6. #5
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17
    ..heres my grub.conf...


    [root@localhost ~]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,8 )
    # kernel /vmlinuz-version ro root=/dev/sda11
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=2
    timeout=30
    splashimage=(hd0,8 )/grub/splash.xpm.gz
    hiddenmenu
    title Fedora Core (2.6.20.1_FC5smp)
    root (hd0,8 )
    kernel /vmlinuz-2.6.20.1 ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.20.1.img
    title Fedora Core (2.6.15-1.2054_FC5smp)
    root (hd0,8 )
    kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.15-1.2054_FC5smp.img
    title Win XP
    rootnoverify (hd0,0 )
    chainloader +1

    its the first one 2.6.20.1 thats giving the problem...

  7. #6
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    grub.conf

    kernel /vmlinuz-2.6.20.1 ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.20.1.img

    fdisk -l
    /dev/sda9 17849 17861 104391 83 Linux
    /dev/sda10 17862 17990 1036161 82 Linux swap / Solaris
    /dev/sda11 17991 19456 11775613+ 83 Linux
    there is any LVM ( Linux extended partition ) listed in output of fdisk -l command but grub.conf is refering to LVM only. change value of root in kernel line.
    Code:
    kernel /vmlinuz-2.6.20.1 ro root=/dev/sda11 rhgb quiet
    edit /etc/fstab file too.





    Casper
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  8. #7
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Question

    sorry i am a bit of a newbie what exactly do you want me to edit in /etc/fstab......

  9. #8
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Unhappy

    here are the new contents of my grub.conf and fstab...

    [root@localhost ~]# cat /boot/grub/grub.conf
    # grub.conf generated by anaconda
    #
    # Note that you do not have to rerun grub after making changes to this file
    # NOTICE: You have a /boot partition. This means that
    # all kernel and initrd paths are relative to /boot/, eg.
    # root (hd0,8 )
    # kernel /vmlinuz-version ro root=/dev/sda11
    # initrd /initrd-version.img
    #boot=/dev/sda
    default=2
    timeout=30
    splashimage=(hd0,8 )/grub/splash.xpm.gz
    hiddenmenu
    title Fedora Core (2.6.20.1_FC5smp)
    root (hd0,8 )
    kernel /vmlinuz-2.6.20.1 ro root=/dev/sda11 rhgb quiet
    initrd /initrd-2.6.20.1.img
    title Fedora Core (2.6.15-1.2054_FC5smp)
    root (hd0,8 )
    kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=LABEL=/ rhgb quiet
    initrd /initrd-2.6.15-1.2054_FC5smp.img
    title Win XP
    rootnoverify (hd0,0 )
    chainloader +1


    [root@localhost ~]# cat /etc/fstab
    /dev/sda11 / ext3 defaults 1 1
    /dev/sda9 /boot ext3 defaults 1 2
    devpts /dev/pts devpts gid=5,mode=620 0 0
    tmpfs /dev/shm tmpfs defaults 0 0
    proc /proc proc defaults 0 0
    sysfs /sys sysfs defaults 0 0
    /dev/sda10 swap swap defaults 0 0


    i still get the same annoying messages...ive actually compiled a newer version of the kernel 2.6.20.1...no luck....

  10. #9
    Super Moderator devils casper's Avatar
    Join Date
    Jun 2006
    Location
    Chandigarh, India
    Posts
    24,729
    if earlier version is booting up correctly then no need to mess with grub.conf or /etc/fstab file. problem is in Kernel Compliation only. did you change anything in default config?
    It is amazing what you can accomplish if you do not care who gets the credit.
    New Users: Read This First

  11. #10
    Just Joined!
    Join Date
    Feb 2007
    Posts
    17

    Question

    ...um yes i included support for ntfs as a module....i read on the net somewhere that make install usually comes thru without problems..i am doing it manually currently...

    $ cp arch/i386/boot/bzImage /boot/bzImage-KERNEL_VERSION
    $ cp System.map /boot/System.map-KERNEL_VERSION
    $ ln -s /boot/System.map-KERNEL_VERSION /boot/System.map

    should i go ahead and do a make install ..i mean what will happen to my old vmlinuz and initrd files and the corresponding entry in grub if i do go ahead and do make install...

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
  •