Find the answer to your Linux question:
Results 1 to 3 of 3
i just finished update Fedora Core 3, then its hang. I reboot it manually and then its stuck (hang). Please help me, i'm a new user... below are the boot ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Feb 2005
    Posts
    1

    Kernel Panic - Not syncing


    i just finished update Fedora Core 3, then its hang. I reboot it manually and then its stuck (hang). Please help me, i'm a new user... below are the boot sequence and error msg for yor references

    Booting Command-List
    root (hd1,0)
    filesystem type is ext2fs, partition type 0x83
    Kernel /vmLinuz-2.6.9-1.667 ro root =/dev VolGroup00/LogVol00 rhgb quiet
    [Linux-bzImage, setup=0x1400, size=0x155da5]
    initrd /initrd-2.6.9-1.667.img
    [linux-initrd@0x17ef4000, 0xebfc7 bytes]

    Uncompressing Linux... Ok, booting the kernel
    audit (1107559803.849:0): initialized
    Red Hat nash version 4.1.18 starting
    Reading all physical volumes. This may take a while...
    Found volume group "VolGroup00" using metadata type lym2
    2 logical volume(s) in volume group "VolGroup00" now active
    exec of init (/sbin/init) failed!!!:2
    umount /initrd/dev failed:2
    Kernel Panic - not syncing: attempted to kill init

  2. #2
    Just Joined!
    Join Date
    Jan 2005
    Posts
    1

    Same problem

    I have the same problem. I am quit new in linux world, just installed couple a days a go fedora 3, i all so have win xp on diferent hard drive in a dual boot configuration. Fedora worked fine for a couple a days then this happend. I am preety sure I did not do any thing stupid. I' ve heard that this could be a bug in fedora 3 but I could not find solution. If any one knows solution or how to a void this pleaese help Thx

  3. #3
    Linux Enthusiast
    Join Date
    Dec 2004
    Location
    Rockin' in the USA!!!
    Posts
    603
    It appears that it cannot execute the init sequence, which is odd since you say that it worked fine for a few days. Did you happen to shut down your comp improperly at all. It may have been corrupted, I suggest booting with knoppix or damn small linux to make sure that the /sbin/init script still exists and works, if that's not where it's stored, you need to add init=/path-to-init in the kernel arguments, you can do this from the grub boot screen by pressing 'a' at the menu.

  4. $spacer_open
    $spacer_close

Posting Permissions

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