PTreHolme, thank you. Here is my /etc/fstab:

[root@localhost dev]# cat /etc/fstab
# This file is edited by fstab-sync - see 'man fstab-sync' for details
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/boot /boot ext3 defaults 1 2
none /dev/pts devpts gid=5,mode=620 0 0
none /dev/shm tmpfs defaults 0 0
none /proc proc defaults 0 0
none /sys sysfs defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0
/dev/hdc /media/cdrom auto pamconsole,fscontext=system_ubject_r:removable_t,exec,noauto,managed 0 0
/dev/fd0 /media/floppy auto pamconsole,fscontext=system_ubject_r:removable_t,exec,noauto,managed 0 0
[root@localhost dev]#

Here is my devices directory:

[root@localhost dev]# ls -ld /dev/disk*
ls: disk*: No such file or directory
[root@localhost dev]# ls -l /dev/hd*
brw-rw---- 1 root disk 3, 0 Dec 13 02:59 hda
brw-rw---- 1 root disk 3, 1 Dec 13 02:59 hda1
brw-rw---- 1 root disk 3, 2 Dec 13 02:59 hda2
brw-rw---- 1 root disk 22, 0 Dec 13 02:59 hdc
[root@localhost dev]# ls -l /dev/sd*
ls: sd*: No such file or directory

And here is my kernel version that works fine:

[root@localhost dev]# cat /proc/version
Linux version 2.6.9-5.EL (bhcompile@decompose.build.redhat.com) (gcc version 3.4.3 20041212 (Red Hat 3.4.3-9.EL4)) #1 Wed Jan 5 19:22:18 EST 2005
[root@localhost dev]#

Well, that clarifies the issue: /dev/hdc is you CD drive, and the "no media found" messages was because you didn't have a CD in the drive.

What I don't understand is why the "noauto" in the option string seems to have been ignored.

Can you boot if you put something in the drive? (Something non-bootable, of course.)

Error Kernel panic –not syncing attempted to kill init

my system linux system is not bootinh its giving the above error can some body help me to resolve this problem

......
insmod: error inserting '/lib/ext3.ko': -1 Operation not permitted
......
Kernel panic - not syncing: Attempted to kill init!

Like above, My kernel have been panic too. It's seem that some *.ko object was uninstalled by some reason.

Disk mount information booting previous kernel is below.
# ls -l /dev/disk/by-uuid
total 0
lrwxrwxrwx 1 root root 9 3月 20 01:53 1097d432-940c-4606-be8f-c20fadb0b498 -> ../../md0
lrwxrwxrwx 1 root root 9 3月 20 01:53 150bdd13-5de3-4243-ae47-b21c1f4c4ba3 -> ../../md2
lrwxrwxrwx 1 root root 10 3月 20 01:53 4a474940-8f1b-8bea-0ba6-694f76c0ca03 -> ../../sda6
lrwxrwxrwx 1 root root 9 3月 20 01:53 85a5ed9c-b2e3-4288-8f9b-a9e9609538fa -> ../../md4
lrwxrwxrwx 1 root root 9 3月 20 01:53 996247db-ac63-418b-b86e-c6173566f3aa -> ../../md1
lrwxrwxrwx 1 root root 10 3月 20 01:53 a709dfc3-8046-f006-18d2-1b532dd7d1e8 -> ../../sda1
lrwxrwxrwx 1 root root 10 3月 20 01:53 c6917b36-e7b6-9e8a-e11c-a6d7d8080df4 -> ../../sdb3
lrwxrwxrwx 1 root root 10 3月 20 01:53 d745c94b-dc24-de8e-b828-02051e59533c -> ../../sda2
lrwxrwxrwx 1 root root 10 3月 20 01:53 e8523c0f-844e-8a17-b6c0-54fe4d6ebb42 -> ../../sda5
#

Currently I have setup md RAID1 for all partitions including /boot partition. And some sd* devices are appeared too.

....
Please help me!

I solved this problem temporarily by steps below.

My kernel build steps.

rpm -ivh kernel-*.src.rpm
cd /usr/src/redhat
rpmbuild -bp SPECS/kernel-2.6.spec
cd /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.x86_64
cp (previous version directory)/.config .
make menuconfig
cp -a .config config_org
make mrproper
cp -a config_org .config
make oldconfig
make
make modules
make modules_install
make install # <--(It seems installing by prep image)
#? This install method is not bootable-->: installkernel 2.6.18-92.1.22.el5 arch/x86_64/boot/bzImage System.map
vi /boot/grub/grub.conf # edit grub menu item and default menu number(0-...).

Please test this method guys.

Regards,

Kernel Panic error comes mainly due to misconfigured /etc/fstab

You should go through ur /etc/fstab and check the entry for root partition. there may be problem with ur root partition LABEL.
Set the label for ur root again or edit the label in the file and provide the dev path for root.

I solved "kernel panic" by changing a Makefile entry.

# Makefile entries....
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 18
# EXTRAVERSION = -prep
EXTRAVERSION = -92.1.22.el5 <-- change this name.
.....

# make...
make
make modules
make modules_install
# 2.6.18-92.1.22.el5
# = ${VERSION}.${PATCHLEVEL}.${SUBLEVEL}${EXTRAVERSION} in Makefile
installkernel 2.6.18-92.1.22.el5 arch/x86_64/boot/bzImage System.map

When this new kernel is booted, modules are loaded from /lib/modules/2.6.18-92.1.22.el5/* directories.

It works fine.

Hey guys, i am getting the kernel panic too, how can i edit /etc/fstab since i cannot boot into linux..?

thanks.

the screen photo from my kernel panic is here http://www.onyro.com/panic.jpg

here is what i have done.

I had a dual boot ssd with Vista 64 and RHEL 4.6, I added a 2nd ssd and set up raid0 from within vista using intel matrix storage which did a nice data migration to form the raid0. The system was stable and booted normaly in both RHEL and Vista for 2 days.

Untill this morning for some reason i go this kernel panic... and obviously won't boot linux. Vista boots fine. your help is greatly greatly appreciated.

Hello, just going to bump this thread because it remains the first on the google list.

I am having the same problem and thought it was the HD so I switched it to another with a viable linux operating system on it. No luck. I thought it was the 2nd HD so I went online (w/another computer) and downloaded/burned linux puppy to a CD. I tried to run it on the legacy and it got as far as trying to put the kernal onto the HD and bam! (Attempted to kill init!)

I am going with the ram idea insofar as it gave no option to continue in RAM only so I am going to go with checking my RAM next - it appears I scrabbled the disk trying to work around the problem other ways. (fdsk - just say no!)

Dell 4600i 2GB ram HDs(varied)
Ubuntu(s) 10.10

PS - I vote sticky

Here's a specific description of this particular message:

• The init process is created by the system and it is not permitted to die for any reason. If it does, the kernel will panic (it has no choice...), and the somewhat-misleading message implies that "someone tried to kill it" which really isn't so.
• Any panic can occur when un-completed disk I/O operations are in progress ("syncing" = bad) or when they are not ("not syncing" = not-so-bad). In any case, this part of the message actually has nothing at all to do with(!) the other part.

yup, that was the problem - one of the ram memory modules went kaput. I removed it and left the rest. Linux Puppy now loaded and back to usual. I'll be partitioning and reinstalling linux OS from backup when I get the chance.

oh, almost forgot, I vote sticky