Ubuntu :: Kernel Panic - Not Syncing: VFS: Unable To Mount Root Fs On Unknown-block (0,0)?
Apr 20, 2011
I am currently running the latest version of Ubuntu (10.10 I believe) and recently installed a new, vanilla 126.96.36.199 kernel on my machine. Then, all I did was run update-grub (I'm not sure if this is correct as I am new to GRUB2 :/), rebooted and tried to boot into the new kernel, but I got the above error on boot. Does anyone know why this is happening?
I was updating my Ubuntu 9.10 Karmic Koala when i decided that i should reboot my computer. All the downloads were done. When i rebooted it booted in normally but when it got into the kernel loading part, Linux-Bzimage and initrd loaded fine, But then Kernel Panic - not syncing : VFS: Unable to mount root as fs on unknown-block (8,1) came up. This is a wubi install also, and i have never had any troubles before.
[ 0.719079] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I was installing updates on my Ubuntu 9.10 and one of them was the upgrade to the new 10.04 LTS. So I said, okay, great! Installed the updates, upgraded my Ubuntu (even though it informed me that some packages had errors). I restarted my PC and then I get this error. I don't know what happened, but that's the error I get when I turn my PC on. Nothing else happened.
PC Specs Compaq, 32-bit processor, 2GB ram, ATI Xpress 200 graphics, Realtek soundcard. PS/2 keyboard, USB mouse. SyncMaster 920Nx flat-panel monitor.
What I did to try to fix this, regardless of it not worked:I tried resetting the BIOS. Didn't do anything. I still get the error.Tried running from CD. It didn't detect the CD or anything, I guess, because I still get the error and it didn't let me run the CD.
I screwed up trying to install a new kernel Now, when I try to boot up, it says: kernel panic not syncing VFS unable to mount root fs on unknown block My system:
-encrypted LVM with encrypted home -10.04 ubuntu system
What's the easiest/fastest way recover the documents on my encrypted home folder? I have the home folder encryption passphrase. I just want to recover and backup those documents, even if after that I have to reinstall the whole system. I have a live CD and also another 10.04 system on a second computer. I've managed to mount the hard drive in this second system and see everything on it, except the contents of the user home folder (Private). Everything I see on the internet is about encrypted home, but not top of a LVM encrypted.
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 188.8.131.52-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 184.108.40.206-147 kernel is also missing (i.e initramfs-220.127.116.11-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.
I have an ongoing issue that I've not been able to troubleshoot. Upon bootup I get the following text and error, and it stops. ACPI: Aborted because bad gzip magic numbers MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
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?
i am just learning about computers and know nothing at all except how to turn it on. i just booted up linux and recieved message:  Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown - block (8,1)
im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,4) i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3. but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. edit this is my lilo.conf
# LILO configuration file # generated by 'liloconfig' # # Start LILO global section # Append any additional kernel parameters: append=" vt.default_utf8=0" boot = /dev/sda3 [Code]...
I am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 18.104.22.168-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 22.214.171.124-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-126.96.36.199-112.fc13.i686.PAE -rw-r--r--. 1 root root 112291 Sep 15 04:32 config-188.8.131.52-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 184.108.40.206-112.fc13.i686.PAE]# ls -l total 3300 lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/220.127.116.11-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!)
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 have attempted to install kernel 2.6.34 and 2.6.33 kernels with this Debian howto [url] Everything worked without any errors until I went to boot into the new kernel. When I receive this kernel panic output Kernel panic - not syncing VFS: unable to mount root fs on unknown-block(0,0)
It also spits out something about being unable to access ext2 FS. I googled this symptom and have seen that it is fairly common, but everyone's error seems somewhat unrelated. I used the same kernel configuration as the one that is currently working, to keep things simple.
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 using Xubuntu and this is the swecond time this has happened the fist time was on the same computer but with ubuntu installed i had to reinstall it. The error message is "[6.063214] Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown block(8,3)" Both times it has happened after i went onto my windows vista partition.
I have upgraded from 10.4 to 10.10, and when I restart I get the error "kernel panic - not syncing: VFS: unable to mount root fs on unknown block".I've done some googling and found this is a pretty common problem, but no existing solutions have worked for me.Right now I am using the 10.4 live CD.
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:
I started installing the beta of Maverick a few days ago, but the update server was running inordinately slow, so I canceled it. Several times, I have attempted to continue the installation, but I've been unable to reach the server. Shortly after this happened, I could no longer boot normally--I get the error:
Code: Kernel Panic - not syncing:VFS:Unable to mount root fs on unknown-block(0,0) Choosing the previous kernel fixes the problem.
So, I obviously want to upgrade to the release version now. When I open the update manager, I get asked if I want to do a partial upgrade to complete the install. I'm a bit leery of doing this since I only have one previous kernel to go back to (my list got really long and I have another operating system entry underneath, so I set my automagic boot manager to only keep two), and if I can no longer boot after the upgrade, I'll have to use Windows until it gets fixed... So, should I finish the upgrade, try to troubleshoot the error, or do something else to jump right to the latest release, after being partway through the upgrade?
I am trying to install debian on my windows PC but am receiving some errors with it. I have downloaded "debian-506-amd64-DVD-1.iso" from debian website and am seeing that the md5 sum is correct. I am getting following error when I choose Graphical Install or install.
[ 1.480788] crc error [ 1.569788] kernel panic -not syncing:VFS: Unable to mount root fs on unknown block(253, 52)
Description of my PC: I have 2 hard disks
1. IDE hard disk (80 GB) -> windows is on this drive 2. SATA hard disk(250GB) -> I intend to install debian on this drive. 3. MSI motherboard & AMD 64 processor with 1 GB RAM. 4. NVidia external graphics card based on AGP slot(256 MB)
EDIT:: This time I got one more error message prior to the 2 shown above [some number] PCI:Cannot allocate resource region 0 of device 0000:00:00.0
When booting, I can choose 2 from 2 options (ignoring recovery mode):
- Ubuntu, with Linux 2.6.32-22-generic - Ubuntu, with Linux 2.6.32-21-generic
(and then Windows Vista and Ubuntu 9.10 a couple of times) The newer version appeared with an update from Ubuntu a couple of days after installation. When booting from the first I get the following message:
Kernal panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) When booting from the second, Ubuntu loads without a problem.
I downloaded the ubuntu-9.10-desktop-i386.iso file from the website, extracted it, and ran the Wbiu.exe file - it prompted to get my info and then restart. Upon restarting, I then had the choice to run Windows or Ubuntu, and I've been running Ubuntu ever since.
I ran into some speed-bumps. Upon entering the Ubuntu option at my start-up prompt, I go to another prompt asking me to choose from: Ubuntu, linux 2.6.31-20 Generic Ubuntu, linux 18.104.22.168 Recovery mode Ubuntu, linux 2.6.31-14 Generic Ubuntu, linux 2.6.31-14 Recovery mode Windows 7 installer Windows Vista installer I've been choosing the very first one, the 31-20 generic, but just this morning after downloading some programs from the Synaptic and transferring a few Gbs of music, I received this error prompt: Code: [2.879604] Kernel panic -- not syncing: VFS : Unable to mount roof fs on unknown--block (8,2) After that, I've been running the 2.6.31-14 generic installer. I have no idea what any of this means and I've spent time crawling through threads trying to figure it out. I mean, it still WORKS but I just help but think I've done something very wrong. ALERT: SUDO PASSWORD QUESTION
I hope the cautionary sign above has dispelled any annoyed gurus who have answered this question dozens of times before. I've crawled through my fair share of threads concerning this, the best corollary being the following: forum/linux-newbie/157773-solved-sudo-password-errors-usb-internet-issues.html; which, strangely enough, was never really solved. Like the user in that thread, when I access the terminal and type in a command, the next line invariably states "[sudo] password for jacob' -- when I hit enter and type in the long list of possibilities I've read (read: sudo, su, su root, su passwd, sudo passwd, sudo root, et al.), alas, nothing happens but the same statement.
I've been using Ubuntu now for 4 years and apart from getting the wireless card working on this laptop it has worked perfectly until now. I just loaded the updates and now problems, after switching on and selecting Ubuntu the next screen gives options
2.6.31-20 generic 2.6.31-20 recovery mode down to 2.6.31-16 generic
if I hit return or let 20 load the next screen reads 1.414518 Kernal panic-not syncing :vfs : unable to mount root fs on unknown - block (8,2) Caps light starts flashing and only way out is to power down. If I select 20 recovery I get a screen full of info and then caps light flashing and only way out is the power button, if I select 19 it loads and works as normal. Is there a simple way to get it auto loading again as the rest of the family use this and are now Ubuntu converts and will not realise whats going on and will reluctantly load up windows.......
i am getting the error msg as follows when i run my own kernel ,kernel panic - no syncing unable to mount root fs on unknown-blockit my pc info :ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, strippedWhat does this mean
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've been having problems with the system ever since I replaced the motherboard. Moving slow and just generally acting 'wonky.' Well the other day I reached my frustration limit and wiped the HDD. Up to this point the HDD had been in 2 partitions, one for the DELL diagnostics and one for the OS, XP Pro.
I decided that I wanted to set up the system in a dual-boot during the rebuild so I created a two partitions using the Windows install. Partition one is the DELL Diagnostic partition, partition 2 is the XP Pro partition and partition 3 is to be the Linux partition. All seemed to go well with the Windows install. I got the OS up and running and got all the updates done and drivers installed.
I only have the one HDD in the system so I was going to have to make this dual-boot off of one HDD.
I had previously, within the past week or two, downloaded the .iso and created the disk for FC11.
I went through the install process and successfully installed Linux on the 3rd partition, or so I thought. When I attempted to boot into Linux I got the Kernal Panic error.
My grub file as it exists now is:
If I leave the file as is, I get the kernal panic error but the splash image works fine. If I try to change the 'splash image' and 'root' references from '(hd0,2),' then neither works.
I can boot into Windows XP from the setup as it is now.
I if I boot using my LoaS (FC 11 made at the same time as the images for the cds were downloaded) I can see the hdd and multiple partitions. There seems to be a 'boot' partion, the Linux OS partition, a swap partion, as well as the Dell and XP partions. Now I've tried changing the references in the grub file to reflect the different partitions, basically I've tried 2, 3, 4 and 5, everything but 0 (the dell diagnostics) and 1 (the XP Pro).
I've also re-wiped the HDD and started the whole process over from scratch, thinking maybe I'd hosed something up the first time, but being a firm believer in 'Always do what you've always done and you'll always get what you've always gotten,' and that one of the definitions of insanity it keep performing the same actions over and over and expect different results, I seem to be at impasse here.