LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 09-11-2008, 01:23 AM   #1
strange.friend007
LQ Newbie
 
Registered: Sep 2008
Posts: 1

Rep: Reputation: 0
Thumbs down filesystem not found ext3 Kernel Panic ! attempted to kill init


hi,

last night i was creating swap sapce on my linux enterprises 4

i creat swap and label /dev/hdc1 to root by e2label command, after that i tried same on /dev/HDC2 which was swap partion, but this command did not work on it,

i then tried mke2fs-L <label name> on /dev/hdc2, mistakenlly during running this command (mke2fs-L) i was in root@/etc directory.

after running this command it format that swap partion, and within one minute i was unable to do anything on my PC. i just restart it and it is not booting

it is giving errors like:


kernel/vmlinuz-2.6.9-5 EL or root=/dev/volgroup00/logvol00 rhgb quiet
[Linux -bzimage,setup=0x1400,size=0x15cb84]
initrd/initrd-2.6.9-5-EL.img
[linux_initrd@0xf6f2000,0xed7f2 bytes]
uncompressing linux ok booting the kernel
audit(1221088194 . 860:0): initialized

redhat nash version 4.1.18 starting

File discriptor 3 left open
filetype is ext2 partion type ox83


reading all physical volumes. this may take a while..

no volumegruop found

File discriptor 3 left open

reading all physical volumes. this may take a while..

no volumegruop found
File discriptor 3 left open

reading all physical volumes. this may take a while..

no volumegruop found

Mount: error6 mounting ext3
mount: error2 mounting none

switch root : mount failed : 22
unmount/initrd/dev failed :22




Will some one give me solution that how to recover such a problen

i could go only in Grub now.
Kernel panic - not syncing : attempted to kill init !
 
Old 09-11-2008, 01:53 AM   #2
Simon Bridge
LQ Guru
 
Registered: Oct 2003
Location: Waiheke NZ
Distribution: Ubuntu
Posts: 9,211

Rep: Reputation: 198Reputation: 198
Quote:
Originally Posted by strange.friend007 View Post
hi,

last night i was creating swap sapce on my linux enterprises 4
Which distro? There are many "enterprise" flavours.

Quote:
i creat swap and label /dev/hdc1 to root by e2label command, after that i tried same on /dev/HDC2 which was swap partion, but this command did not work on it,
So /dev/hdc1 is your root partition?
So /dev/hdg2 is your swap partition?

Note - e2label vill not work to label a swap partition because swap is not an ext file system.

Quote:
i then tried mke2fs-L <label name> on /dev/hdc2, mistakenlly during running this command (mke2fs-L) i was in root@/etc directory.
So now, /dev/sdc2 is some ext file system and not swap?

Quote:
after running this command it format that swap partion, and within one minute i was unable to do anything on my PC. i just restart it and it is not booting

it is giving errors like:


kernel/vmlinuz-2.6.9-5 EL or root=/dev/volgroup00/logvol00 rhgb quiet
[Linux -bzimage,setup=0x1400,size=0x15cb84]
initrd/initrd-2.6.9-5-EL.img
[linux_initrd@0xf6f2000,0xed7f2 bytes]
uncompressing linux ok booting the kernel
audit(1221088194 . 860:0): initialized

redhat nash version 4.1.18 starting

File descriptor 3 left open
filetype is ext2 partition type ox83


reading all physical volumes. this may take a while..

no volume group found
File descriptor 3 left open
Looks like you have Redhat Enterprise Linux 4, is this correct?

Try booting to rescue mode and running fsck.
You can probably also use this to restore your swap partition.

However - this is a guess... need more info. For eg. Why were you creating a new swap? Why did you feel you needed to label your root partition - is it new?
 
Old 09-11-2008, 02:07 AM   #3
jschiwal
LQ Guru
 
Registered: Aug 2001
Location: Fargo, ND
Distribution: SuSE AMD64
Posts: 15,733

Rep: Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671Reputation: 671
Use "mkswap /dev/sdc2" to recreate your swap partition. Did you change any of the other swap partitions?

I'm wondering if there is a "resume=/dev/sdc2" entry in grubs kernel line entry. This might cause a problem because the resume device should be a swap partition. Another possibility is if you changed the partitioning scheme on the drive and a device such as the root partition has changed numbers. However from your description, it doesn't seam to be the case.

while you are in the rescue disk, explore around with your devices. For example, use fdisk -l to examine the partitions.

Also run lvscan.

I think what happened has little to do with trashing your swap partition. Maybe running e2label on your root partition did something to the lvm volume or volume label. You may need to run lvrename, but I'm just guessing now.
 
Old 09-11-2008, 03:01 AM   #4
jay73
LQ Guru
 
Registered: Nov 2006
Location: Belgium
Distribution: Ubuntu 11.04, Debian testing
Posts: 5,019

Rep: Reputation: 130Reputation: 130
Well, if you executed mke2fs on /, then / may be gone. mke2fs creates a brand new file system, unlike tune2fs -L, which only assigns a label. Still, if / was mounted, you should have been warned.

Last edited by jay73; 09-11-2008 at 03:03 AM.
 
Old 09-11-2008, 09:21 PM   #5
sundialsvcs
LQ Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 8,154
Blog Entries: 4

Rep: Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717Reputation: 2717
"attempted to kill init" actually means, "the 'init' process died." (Basically, this process is not allowed to die.)

It seems to me that filesystem-support for 'ext3' is not properly included in your kernel, and/or the startup-sequence is not loading whatever kernel-module is needed to support it.

Check all of the messages carefully, working backward from the point where 'init died.'

Background Information:
When Linux (or any Unix-like system) finishes booting, it auto-creates one process: 'init,' the so-called "process #1." This process has a central role in that it starts all other processes and monitors their execution. Without it, Linux could not function. Therefore, if for any reason this process does die, the kernel panics.
 
  


Reply


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: Attempted to kill init ! tinylinux Linux - Kernel 1 05-14-2006 11:56 AM
exec: 431: chroot not found, kernel panic, Attempted to kill init! WalGrom Linux - Software 0 12-11-2005 01:37 PM
<0>Kernel Panic Attempted to kill init! cheeseboy123 Red Hat 3 10-30-2005 08:06 PM
Kernel panic: Attempted to kill init! theMagus Linux - Newbie 0 06-02-2004 03:02 PM
Kernel (and me) panic. Attempted to kill init! LinuxBlackBox Linux - General 2 10-29-2003 04:24 PM


All times are GMT -5. The time now is 07:28 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration