Find the answer to your Linux question:
Results 1 to 6 of 6
Below is the error we get - we can't get the computer to boot completely it gives this error and we are 'done' PLEASE Advise - any help much appreciated!!! ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2003
    Posts
    2

    Kernel Panic


    Below is the error we get - we can't get the computer to boot completely it gives this error and we are 'done' PLEASE Advise - any help much appreciated!!!


    ERROR: /bin/insmod exited abnormally
    Loading jbd module
    Journalled Block Device drive loaded
    Loading ext3 module
    Mounting/proc filesystem
    Creating root device
    Mounting root filesystem
    Mount: error 19 mounting ext3
    pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed:2
    Freeing unused kernel memory: 244k freed
    Kernel Panic: No init found. Try passing init=option to kernel.

  2. #2
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Can you please describe your partition layout, and tell us what distro and boot loader you're using?

  3. #3
    Just Joined!
    Join Date
    Aug 2003
    Posts
    2

    Kernel Panic

    Our partitions are laid out like:
    All are on the /dev/sda
    Mount Point Size Type
    Sda1 /boot 47 ext3
    Sda2 swap 2047
    Sda3 /usr 49160 ext3
    Sda4 18662 extended
    Sda5 /home 17979 ext3
    Sda6 / 384 ext3
    Sda7 /var 259 ext3

    We are using the GRUB bootloader version 0.90
    Linux is Version 2.4.9-e.12
    FYI:
    I tried to use the installation disk after completing a non-bootable "bad" installation utilizing the 'Linux rescue' command at the prompt. I get a message that states there are no Linux partitions! We have used the Linux DD command so that we could install the disk drivers and the disks appear in the setup application correctly. It almost appears that the drivers are not staying loaded or the system is not saving the configuration.

  4. $spacer_open
    $spacer_close
  5. #4
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    Indeed; it seems that the initrd doesn't contain the SCSI driver. My suggestion is as follows: Get a LiveCD distro like Knoppix (which is bound to have a SCSI driver, or at least I hope so =) ), boot from it, mount the Linux root partition, extract the correct SCSI driver modules from /lib/modules/<kernel version>/kernel/drivers/scsi. Make sure that you get them from the hard drive and not Knoppix' SCSI drivers, since Knoppix' drivers will be incompatible. Then get the initrd from the boot partition, unzip it, mount it through a loop device, put the SCSI drivers, and modify /linuxrc on the initrd to load them. Then unmount the initrd, rezip it and copy it back to the boot partition, reboot and rejoice if it works. I don't know how experienced you are with Linux, but just reply back if there's something that you don't know how to do.

  6. #5
    Just Joined!
    Join Date
    Aug 2003
    Posts
    26

    Re: Kernel Panic

    Quote Originally Posted by VisualSolution
    Below is the error we get - we can't get the computer to boot completely it gives this error and we are 'done' PLEASE Advise - any help much appreciated!!!


    ERROR: /bin/insmod exited abnormally
    Loading jbd module
    Journalled Block Device drive loaded
    Loading ext3 module
    Mounting/proc filesystem
    Creating root device
    Mounting root filesystem
    Mount: error 19 mounting ext3
    pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed:2
    Freeing unused kernel memory: 244k freed
    Kernel Panic: No init found. Try passing init=option to kernel.
    Do you have filesystem support added to te kernel as a module? It seems like that you didn't burn them into the kernel ..?

  7. #6
    Linux Guru
    Join Date
    Oct 2001
    Location
    Täby, Sweden
    Posts
    7,578
    I don't think he made his own kernel at all. Or am I wrong?
    In any case, it isn't the filesystem module that's missing. errno = 19 is ENODEV, so it's the device drivers that are missing.

Posting Permissions

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