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:
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'?
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 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 am trying to install Fedora 11 from the full DVD iso on a system using an Intel D945GNT motherboard with a dual-core 3.2GHz Pentium D installed. The installation hangs quite quickly and produces the error "Kernel panic - not syncing"... The previous line is something along the lines of "EIP: [something] intel_i915_configure() [something else]". I have tried many different kernel boot options, such as acpi=off, nolapic, nommconf, and the like, but to no avail. It seems as though this has something to do with a memory mapping conflict due to the allocation of video memory for the on-board graphics chip, but I'm not at all certain about that.
I am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 220.127.116.11-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 18.104.22.168-56.fc13.i686.PAE.
/boot/conf/grub.conf contains: # 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 # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) code....
When I try and boot to the newer kernel I get an error like:
Kernel panic - not syncing VFS Unable to mount root fs on unknown block(0,0)
I read on the forum about a similar problem where the fix was to insert the line
but this file doesn't exist and so the boot then hangs with no messages, so I took this line out again. Here is contents of /boot:
$ ls -l total 21148 -rw-r--r--. 1 root root 111391 May 27 04:06 config-22.214.171.124-112.fc13.i686.PAE -rw-r--r--. 1 root root 112291 Sep 15 04:32 config-126.96.36.199-56.fc13.i686.PAE drwxr-xr-x. 3 root root 1024 Jan 23 2010 efi code....
As you may deduce from the above I haven't used the system much so the auto-update hasn't run for several months.
Any help on running / installing the newer kernel appreciated. Note that I am trying to install a wireless LAN card and am following instructions here: url
I got as far as
cd /lib/modules/`uname -r` ls -l
[root@localhost 188.8.131.52-112.fc13.i686.PAE]# ls -l total 3300 lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/184.108.40.206-112.fc13.i686.PAE drwxr-xr-x. 2 root root 4096 May 27 04:08 extra drwxr-xr-x. 11 root root 4096 Jun 3 00:52 kernel code.....
so I have the src files for the newer kernel not the one I am running. I thought it best to stop and think (and ask for help!) rather than break a working machine (but with no wireless LAN!)
I have a Compaq Presario 8000 with an Nvidia Geforce FX 5950 Ultra on which a year ago I upgraded from Fedora 6 to Fedora 9, and this broke the Nvidia driver, since Fedora 9 was shipped with an X server incompatible with Nvidia. I went back to the 2d driver to get X working, and it sat that way for the past year. But recently I wanted to do some 3D work and decided to install Fedora 12, which hopefully has an X server that works with Nvidia.
I decided to do a cold install, re-partitioning my 80G hard drive at the same time. I backed up my data, ran the install CDs with no errors, and booted the system, with an immediate kernel panic: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Doing a Google search, I found over 8,000 hits for that message combined with the keyword Fedora. Several of the hits were on Bugzilla: [URL] I then booted the install disk, chose rescue mode and did - chroot /mnt/sysimage
I'm running Fedora 10 on a HP Compaq 6710b laptop. It is by far the best OS I have ever used and have no complaints, but I seem to be having some trouble with the wireless at work. The office has a single Cisco Aironet 1131 configured for WPA2 using AES with a PSK. The SSID is not broadcast. The mode is B/G mixed. My wireless card is a built-in Intel PRO 3945ABG, the driver is IWL3945 (auto configured during the OS install).
I use the Network Manager to manually add my SSID and select "WPA & WPA2 Personal" on the security tab and enter the PSK in the password field. After a few moments the wireless connects and appears to be working fine. About every 3-5 minutes while using the office network I get the "kernel error" dialog in the bottom right hand corner of my screen and the wireless drops connection. It re connects after about 30 seconds and appears to work fine until the next kernel error.
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
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
sdb is my external hard drive in whick i also had 10.04 installed but never used it.
I recently upgraded from FC7 to FC10 (Also, the Kernel from 220.127.116.11 to 18.104.22.168).I did the upgrade through Yum (First installed the fc10 rpms, then did yum upgrade).Now the new Kernel won't boot.These are the options in GRUB for the new Kernel
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?
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now. It's been through several passes without errors. I'm going to let it run some more, but if that is dependable it's looking like the RAM sticks are not the problem.
Today I was upgrading my netbook with Ubuntu 10.10 on it to 11.04 via the Update Manager. I got a few errors and the Update Manager seemed like it wasn't continuing, so decided to exit it. It didn't respond so after a while I decided to restart the netbook. However the on/off/standby/restart, etc. button in the top right wasn't responding either, so I decided to force a shutdown with the power button on my netbook. Now Ubuntu doesn't start up, and gives me an error along the lines of:
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.35-28-generic #50-Ubuntu Now could I in some way repair my Ubuntu installation while still keeping the files I already have on my computer? Maybe via booting from a flash drive or something...?
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:
Kernel Panic - not syncing: VFS unable to mount root fs on unknown-block (0,0)
EDIT: Here's the content of grub.conf
# 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
What is peculiar on this grub.conf, is that the 22.214.171.124-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 126.96.36.199-147 kernel is also missing (i.e initramfs-188.8.131.52-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.
My computer AMD phemom II 955 X4 Black Edition 3,2 Ghz Asus M4A785TD-M EVO micro atx Kingston 4Gb Ram DDR3 1333 mhz (KVR1333D3N9K2/4G) Disco Duro Western Digital 1 terabyte LG GH24 Super Multi DvD rewriter
Orden (m para obtener ayuda):
I have Sata=AHCI
Sometimes it starts and sometimes not. the RAM is memtest OK. The test detects a firmware in the micro hole 15 to 16 mb of memory. The rest is OK.
I recently started to use Ubuntu in VWware player on my windows-XP. I installed ubuntu 10.04 few days ago, It was working fine.
Yesterday, I compile a new kernel, kernel 2.6.33 in my vmware ubuntu 10.04. Everything went well till I did reboot. before reboot I use the command "update-grub" to make it compatible to the new kernel. BUT... after rebooting, I have a problem in loading a grub correctly. it gives me following message " [2.149136 ]kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)" and I can not proceed further. I have my all data on it. I also tried to boot it from live CD but unfortunately, I can't mount the hard disk on it in order to get those data from my old Ubuntu set up.
I need to recover some data of the 'home' directory after kernel panic.I was upgrading ubuntu 11.04, [COLOR=blue !important][COLOR=blue !important]installed[/COLOR][/COLOR] on usb.Failed to upgrade because the main partition had no more space. I moved one directory of about 100Mb to other partition, but it seemed that in the main partition didn't appear those 100Mb free. i restarted the computer expecting those 100Mb free. And kernel panic.
[ 0.789567] Kernel panic - not syncing: VFS: Unable to mount root fs on unknow-block(8,1) [ 0.789646] Pid: 1, comm: swapper Not tainted 2.6.35-22-generic #33-Ubuntu [ 0.789716] [<c05c6468>] ? printk+0x2d/0x35
I have trawled through an extensive number of post on quite a few forums without even a step forward with this.
I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively) , swap is not raided.
I was doing an yum update through the software updater in gnome and the system froze.
I had to press reset to get any response from the machine.
Since then I have been getting the kernel panic above just after grub starts fedora.
I tried the previous kernel from the previous update and it has the same error.
At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead. Is there any way to access these partitions through a live CD or rescue environment?
Is there a method to bring this install back to life? or am I looking at a reinstall?
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.
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 just downloaded Wubi - To install Ubuntu on my computer. (Whether it's called Dual boot or running Ubuntu inside of Windows Vista I do not know.) Everything went fine, got a very easy little screen to ask what partition I wanted to install it on and how much size, etcetera, the download went fine, blablabla.
Problem: It asks me to reboot (This is the first reboot I got.), I say yes, it reboots, I get the booting screen where I get to pick between Windows and Ubuntu, I pick Ubuntu, and it gives me this 'error'.
Among other things it reads:
After this nothing happens - I waited about 25 minutes.
I manually turned off my computer - started it up again - once again chose Ubuntu and the same problem occured.
1. I looked around the Ubuntu folder inside my C a little, it shows the iso file as Ubuntu-10.04.1-desktop-amd64
2. Some other forum advised people with this problem to check their RAM, so I unplugged both, cleaned and switched them. (I have 2 GB ram total.) This didn't work. Same problem still occurs.
I recently decided to try out OpenSuSE after a few years of using kubuntu. However, upon lanuching the install disk I get the following kernel panic: "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(3,1)". I am using the 64-bit DVD install and I have verified the md5 of both the download and the disk itself. The specs for my computer are: