I've just installed for the first time Centos 5.3 on my machine. everything goes in harmony except : 1-when I power off, everything seem to be terminated smoothly but at last I get this annoying error "kernel panic not syncing : fatal exception" 2-my Ethernet card won't get operational; its detected already but when I try to activate it I get this error " eth0 seems not to be present. Initialization delayed"
System Information:
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: 965P-DS3
BIOS: Award Modular BIOS v6.00PG
Processor: Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz (2 CPUs), ~2.4GHz
After update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
exec of init (/sbin/init) failed!!! : 2 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! My server is at remote end which I access through Public IP.
I got the following error after compiling kernel version 2.6.38.2 from sources with this Howto:[URL].. Creating root device.
Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults
First off let me say thanks psy_unix and fuji, the pci=nomsi allowed me actually finish install on my laptop. (Read this post)
Problems do not stop here however...Now, when it reboots after install all I get is a "Machine Check Exception" followed by a "Kernel Panic". I had to switch back to Vista Home finally (not happy about that).
I just bought it and it runs happily under Vista, I just don't run happily under Vista.
I am getting an error when I try to boot my ubuntu 10.4 system (64 bit). Error:Kernel Panic- Not syncing: VFS: Unable to mount root fs on unknown-block(0,0).I installed Sbackup and tried to create a backup of the home, var, usr/local folders. I started the backup and it ran for about 30 minutes then I got a message from the system that indicated that I was out of hard drive space, then the system froze. I restarted the system and then I got the above mentioned error.
I get this Kernel Panic when I start my PC once in a while. After a restart or two it boots normally. I have included a screenshot taken with my camera. Anybody have any idea what this is and how I can get rid of it?
I tried using gparted on a live cd to shrink a windows partition to make room for ubuntu. Then windows failed to boot. I deleted the entire disk and tried to install ubuntu 10.10. It seemed to install fine, but now when I start up I get
[ 0.869364] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
and a bunch of other stuff that doesn't look good. I saw some other posts about this error, and people are talking about lilo. I'm not sure what to do
I've been using Linux for a few years, but this is my first time using Fedora. I installed it on an old computer last night and rebooted, and everything seemed good. I let it start to install updates, but after they were about half done I stopped it, turned the computer off, and went to bed. I know that was stupid of me, and I'm afraid it screwed something up because now when I boot I get the error "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(0,0)".
When I looked up the error on Google it seems a lot of people get this after installing a kernel incorrectly, so could stopping the update in the middle perhaps screwed with my kernel? Could I simply chroot into the installation from the live CD and run 'yum install kernel26'?
In my internal disk i had installed 10.04 and 10.10. 2 days ago after a restart my system did not boot and i got the message: kernel panic:not syncing VFS unable to mount root fs on unknown block(0,0).
For 2 days i tried to solve the problem without success and today i installed 10.04 in the entire internal disk but the problem(message above mentioned) remains.
the result of the sudo fdisk -l command is this
Quote:
ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes
[Code]....
sdb is my external hard drive in whick i also had 10.04 installed but never used it.
I tried to upgrade Empathy from 2.28 to 2.30 via Synaptic but the upgrade always failed as there were some errors to do with the dependencies (libglib2.0* and others). The dependency issues were odd as it told me that Empathy wanted to install files that were older than the existing ones. So I decided to uninstall Empathy and all its dependencies, and re-install the whole (updated) package and it's dependencies from scratch via Synaptic. After the install, Ubuntu told me that there were broken packages and Update Manager kept on popping up asking me to run a partial upgrade to fix these broken packages. Well, the partial upgrade also failed (due to the same dependency issues , I suspect) so I decided that I'll run a full system update (as Update Manager had being bugging me prior to my failed Empathy upgrade). 486 Mb later, Ubuntu no longer wants to boot - it freezes on the splash screen.
When I start it in recovery mode, it spews out the various processes being loaded. Trying to run earlier kernels (2.6.31-19 / 17 / 14) from GRUB, in both normal mode and recovery mode does not seem to help.I am running Ubuntu 9.10, kernel 2.6.31-20-generic.
a) Is the problem to do with the kernel - did the update try to update the kernel as I note that there is a new stable release (2.6.33-2)? However, GRUB still indicates that the kernel is 2.6.31-20. b) Would updating the kernel to 2.6.33-2 help? If so, how do I do this? c) Is the problem, as I suspect, to do with the libglib* files? If so, how do I fix it?
this is a dual boot XP/UBUNTU 10.04. while using XP, the computer rebooted itself. the GRUB's screen appears, but neither the ubuntu nor the XP option works.
Ubuntu gives this error message:
Code: 0.797795 kernel panic-not syncing: vfs: enable to mount root fs on unknown-block (0,0)
XP hangs on a black screen... and that is it (thanks for support windows!) UBUNTU 10.04 live CD hangs when the 5 processing dots appears bellow the ubuntu logo. hangs the same way with the processing bar in UBUNTU 9.04 live CD. memory check (memtest86) is showing thousands of errors right from the start.
I used ubuntu in my ARM board. but now i rebooted it says that "kernel panic - not syncing: Attempted to kill init!" i have to reinstall my OS or any other way to get retify?
Our email server and fax server configured in a Linux server.2day mornin onwards i am getting the error.kernal panic -not syncing : attempted to kill init.
Bootin "powerserver"(Centos-4 i386)-up( 2.6.9-11 EL) root (hd0,0) Filesystem type is ext2fs,partition type 0*fd
How to resolve "kernel panic not syncing attempted to kill init" problem in Linux?? And why this error occurs? In my case, this error occurs when i boot my computer and after this error my computer goes on rebooting..
am trying to interface ade7758(adc) to at91sam9261...i have written a sample code which registers an spi driver and sends an address to ade7758 and receives a data...every thing is fine.My device is registered but kernel is giving a crash message....below is the message....
I've just started using Linux Ubuntu. I had a frightening error message, I don't know why. But after browsing some replies to something similar on this site, I simply opened a previous session and found that all worked fine and I hadn't even lost any of my downloads and adaptations. ś Yes I've still got my third level key and everything.
I was able to copy the iso file and tried the installation however I stubbled upon the same problem I had when I tried installing Fedora 11. The message I received was "(1) (0.048001) MP-BIOS bug:8254 timer not connected to IO-APIC (2) (0.064001) Kernel panic-not syncing:IO-APIC + timer doesn't work Book with apic debug and send a report. Then try booting with the 'no apic-option'.
I had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10 (hd0, 1) 120GB : /home (hd0, 2) 30GB : / > First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
Problems arose when I updated today, after not booting(updating) for a couple of days. Message originally said "Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(8, 1)"
After searching other similar posts I have not found an answer. I have recently installed Ubuntu 10.4.1 after reformatting the computer from the previous Ubuntu Edgy. When rebooting get this msg (in title). I used the live CD to get into the grub files to see if I could ad 'noacip' option. But was looking for 'menu lst' file and found none. Currently when I boot I don't get any menu list and therefore no options at the bottom. Should be an easy problem to resolve Powerspec B364/160gb/856Ram/ATI raedon 200 express onboard/Geforce 8400GS PCI-e
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5 VmWare - using ESX 4.0 OS - Red Hat Enterprise Linux 4 ES Update 5 x64 kernel - 2.6.9-55.0.9.ELsmp
I'm getting the following when I try to boot on the new virtual machine. I'm thinking it has to do with the fact that it's new hardware and it's having trouble either finding the right drivers or pointing to the correct place.
"No Volume Groups found Volume Group "Volgroup00" not found ERROR: /bin/lvm exited abnormally! (pid505) mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!" I was able to boot into Linux rescue mode using the boot CD. Then I typed: #chroot /mnt/sysimage
Here's all the info from the commands I typed: #ldd /bin/bash libtermcap.so.2 => /lib64/libtermcap.so.2 libdl.so.2 => /lib64/libdl.so.2 libc.so.6 => /lib64/tls/libc.so.6 /lib64/ld-linux-x86-64.so.2 #uname -a Linux localhost.localdomain 2.6.9-89.EL x86_64 #df -h ....
I've tried the following: 1. mkinitrd -v -f /boot/initrd-2.6.9-55.0.9.EL.img 2.6.9-55.0.9.EL 2. modified the device.map to point to /dev/sda3 3. changed the SCSI controller in Vmware to use BusLogic instead of LSI Logic. (didn't work because I'm running 64 bit.. gave me an error message) 4. grub-install --recheck /dev/sda 5. tried booting to differerent OS versions (i.e. 2.6.9-55.0.6, etc.). I tried all of the versions listed in the boot menu. None of these worked.
i study computational systems engineering.. and in my school (itlp) we've got fedora 12 installed in some of the computers.. and we use it to learn network administration and security. the reason of this message.. is that i want to install fedora 12 in my notebook (dv4-1525la vu068la).. but an error keeps poping up.. the error is the next one..
DMAR: No ATSR found DRDH: handling fault status reg f0003d63 Kernel panic - not syncing: DMAR hardware is malfunctioning
and though i have looked in bugzilla.. there is no help for me there.. they say.. "press tab in the welcome bootscreen when you are about to select whether to install or restore an existing system and write intel_iommu=off and press enter" but that does not really helps.. it just does the same.. in some blogs they say "upgrade your bios".. but i say.. then why i can not install the olders distributions with my "old" bios.
I just installed the DVD iso of Fedora 13...and did a "sudo yum update" after the installation got finished. After 3 hours of waiting, I restarted. I was greeted by Fedora with a kernel panic, right after it boots up.
Here's the message:
Code:
Kernel Panic - not syncing: VFS unable to mount root fs on unknown-block (0,0)
EDIT: Here's the content of grub.conf
Code:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that
[code]....
What is peculiar on this grub.conf, is that the 2.6.33.6-147 boot conf is missing an initrd line...I looked in the /boot directory...and I found out that the initramfs file that matches the 2.6.33.3-147 kernel is also missing (i.e initramfs-2.6.33.3-147.fc13.i686.PAE.img).
My Fedora 14 box is no longer starting. I am getting a message at startup - "Kernel panic - not syncing:
VFS: Unable to mount root fs on unknown-block(0,0)".
Unfortunately, I don't know what I did before I got the message. I mean, I have made various installations, including some kernel drivers (such as a wifi card and a sound card). Also I did need to update the kernel-devel package as a requirement for some install or other. I know that is not very helpful, but let's get to the important bit...
What does the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" mean? What has broken?
And how does on recover from it? I have been reading around, and of course I am able to boot the machine from a live CD, but I am not sure what I should do with grub.conf, what I should rebuild, how to do it and so on.
