Find the answer to your Linux question:
Page 2 of 4 FirstFirst 1 2 3 4 LastLast
Results 11 to 20 of 31
I should have waited before posting the previous message; I've just done man grub and info grub and learned how to re-install grub on the MBR . It now works ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Linux Newbie
    Join Date
    Jun 2004
    Posts
    220

    I should have waited before posting the previous message; I've just done man grub and info grub and learned how to re-install grub on the MBR . It now works fine, but I'm getting the same error as before:

    mounting root filesystem
    mount: error 19 mounting ext3
    pivotroot: pivot_root (/sysroot, /syroot/initrd) failed: 2
    umount /initrd/proc failed: 2
    freeing unused kernel memory: 252K freed
    kernel panic: no init found. try passing init= option to kernel.


    Here is my grub.conf file, in case there is anything wrong with it.
    Code:
    # 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,0)
    #          kernel /vmlinuz-version ro root=/dev/hda2
    #          initrd /initrd-version.img
    #boot=/dev/hda
    default=1
    timeout=10
    splashimage=(hd0,0)/grub/splash.xpm.gz
    title Red Hat Linux (2.6.6)
            root (hd0,0)
            kernel /vmlinuz-2.6.6 ro root=/dev/hda0=/
            initrd /initrd-2.6.6.img
    title Red Hat Linux (2.4.20-8)
            root (hd0,0)
            kernel /vmlinuz-2.4.20-8 ro root=LABEL=/
            initrd /initrd-2.4.20-8.img
    Mod edit - fixed the code tags
    N3WO

    There are 10 types of people; those who count in binary and those who don\'t...

  2. #12
    Linux Enthusiast Opnosforatou's Avatar
    Join Date
    Dec 2003
    Location
    Vleuten, The Netherlands
    Posts
    552
    Read Here.



    Example:

    title Fedora Core (2.6.5)
    root (hd0,5)
    kernel /boot/bzImage-265 ro root=/dev/hda6 rhgb
    # initrd /boot/initrd-2.6.5.img
    Yours would become:
    Code:
    title Red Hat Linux (2.6.6)
            root (hd0,0)
            kernel /vmlinuz-2.6.6 ro root=/dev/hda0
    #        initrd /initrd-2.6.6.img
    ---[ MS09-99896 - Vulnerability in All MS Windows OS ; Using Windows Could Allow Remote Code Execution. ]---
    Hardware: Asus P4P800, 1GB, P4-3Ghz, Asus V9950, Maxtor ATA HD\'s, 3Com GBit lan, Audigy ZS Plat.

  3. #13
    Linux Newbie
    Join Date
    Jun 2004
    Posts
    220
    I don't know how the smiley got into the grub.conf file, but the line should look like "redhat 2.4.20-8"
    N3WO

    There are 10 types of people; those who count in binary and those who don\'t...

  4. #14
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Remove that "initrd" line from the 2.6.6 kernel entry and try again.

  5. #15
    Linux Newbie
    Join Date
    Jun 2004
    Posts
    220
    Alright, I've managed to get rid of the other errors (pivot root, etc) but am still stuck with "no init found..." I've tried removing the initrd line from my grub.conf, but that doesn't help. Is there more I need to do? It looks like it is mounting ext3fs just fine, and I know that I compiled the ext3fs drivers into the kernel.
    BTW, my root= line only works if it looks like this
    Code:
    kernel /vmlinuz-2.6.6 ro root=/dev/hda1
    Thanks for sticking with me for so long...
    N3WO

    There are 10 types of people; those who count in binary and those who don\'t...

  6. #16
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    I don't think that it is /dev/hda1 that it should be, since /dev/hda1 is your boot partition (or at least so it looks from your grub.conf).

    Double check what partition your root filesystem resides on.

  7. #17
    Linux Newbie
    Join Date
    Jun 2004
    Posts
    220
    You're right, /dev/hda2 solved all the initial bootup problems ("no init found, etc) But now when I boot up, a little way into the list of items with "OK" to the right, comes
    Code:
    mounting root filesystem: error: ext3 fs not supported by the kernel
    I said yes to the boxes in the "filesystem" section of the config program (xconfig) that said ext3 and ext3 extended attributes and something else.

    Is there anywhere else I might have missed an ext3 config question? (I've re-compiled three times now to check...)
    N3WO

    There are 10 types of people; those who count in binary and those who don\'t...

  8. #18
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    That's a bit strange. Can you check if ext3 is present if you run "cat /proc/filesystems"?

  9. #19
    Linux Newbie
    Join Date
    Jun 2004
    Posts
    220
    Code:
    nodev	rootfs
    nodev	bdev
    nodev	proc
    nodev	sockfs
    nodev	tmpfs
    nodev	shm
    nodev	pipefs
    	ext2
    nodev	ramfs
    	iso9660
    nodev	devpts
    	ext3
    nodev	usbdevfs
    nodev	usbfs
    	vfat
    When booted into 2.4.20-8

    ext3 is not present in /proc/filesystems when booted into 2.6.6
    I am unable to post the exact output because I'm using a usb flash drive formatted with vfat, which the kernel also said is not supported!!
    N3WO

    There are 10 types of people; those who count in binary and those who don\'t...

  10. #20
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    OK - can you boot back into 2.6 and check the output of the following commands?

    Code:
    cat /proc/sys/kernel/modprobe
    modprobe -V
    And one command that you can check from either kernel, at your choice:

    cd into the kernel source directory of the 2.6.6 kernel and check the following command:
    Code:
    grep EXT3 .config

Page 2 of 4 FirstFirst 1 2 3 4 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
  •