LinuxQuestions.org
LinuxAnswers - the LQ Linux tutorial section.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices



Reply
 
Search this Thread
Old 10-28-2006, 11:49 AM   #1
vengadesan
LQ Newbie
 
Registered: Oct 2006
Posts: 2

Rep: Reputation: 0
Thumbs up Kernel panic -not syncing:Attempted to kill init!


Dear Friends,

I have loaded Fedora core 5 with Onboard Host RAID, its loading and booting everything is fine. I have created RAID levlel 1 (disk mirroring) using two HDD. Consider one of the HDD gets failed, i am connecting new Harddrive in that place. now i am booting the system it shows the error message as "Kernel panic-not syncing:Attempted to kill init! Has anyone experienced this type of message and what did you do to fix the problem?


Thanks & Regards,

A.Vengadesan.
 
Old 10-31-2006, 08:39 AM   #2
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 331Reputation: 331Reputation: 331Reputation: 331
I just had this problem. I caused the problem by changing the file system type on the root partition and then restoring the system files from backup.

The problem was caused by the fact that the initrd image did not have the proper driver for the new file system type, or that the root partition was listed with the wrong file system type.

The answer is to create a new initrd image. Here is what I did.
1) boot Linux from another partition or from a live CD.
2) mount the hard disk partition for the broken root file system to a temporary mount point.
3) mount the live /dev and /proc directories in the broken root file system.
4) use chroot to create a new environment on the broken root file system.
5) run mknitrd.

The following commands will fix a broken root file system on /dev/hda1.

Code:
mount /dev/hda1 /mnt
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
chroot /mnt /bin/bash
mkinitrd -d /dev/hda1 / ext3
mkinitrd -m ext3
I had previously been using the XFS file system for the root parition. I reformatted it in ext3 and then restored from backup. The new initrd image expects the root file system to be ext3 instead of XFS.

In your case you probably have to include some RAID module in the initrd. More information is available in the man page for mkinitrd.

Last edited by stress_junkie; 10-31-2006 at 08:50 AM.
 
  


Reply

Tags
initrd, mkinitrd


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Kernel panic - not syncing: Attempted to kill init! potsilui Linux - Kernel 28 05-09-2012 12:46 PM
Kernel Panic - Not Syncing: Attempted To Kill Init! tegralens Linux - Software 13 06-23-2008 04:15 PM
kernel panic - not syncing: Attempted to kill init! k5knt Linux - General 39 07-18-2007 01:47 AM
Kernel panic-not syncing:Attempted to kill init skie_knite007 Linux - General 3 10-02-2006 11:46 PM
kernel panic - not syncing attempted to kill init KennyS Fedora 1 02-22-2006 08:51 PM


All times are GMT -5. The time now is 04:00 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration