Ubuntu Installation :: Unable To Boot After Kernel Upgrade
Feb 13, 2011
I had problems with booting my PC after kernel updates several times. In the past I just reinstalled Ubuntu and after several tries with running Update Manager things were working again.This time I applied another recommended set of updates, including a kernel upgrade and got the usual "Kernel Panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)"After booting from a LiveCD and running boot_info_script I rebooted again and this time I am getting tons of errors which seem to be generated while running grub. After a few minutes of 'error: syntax error' and 'error: Incorrect command' scrolling through my screen, grub gives my a grub> prompt... Not what I expected!Here is the output of the boot_info_script:
Code:
Boot Info Script 0.55 dated February 15th, 2010
============================= Boot Info Summary: ==============================
=> Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in
partition #1 for (,msdos1)/boot/grub.
=> Grub 2 is installed in the MBR of /dev/mapper/isw_cagifdjehe_Volume0 and
[code]...
I have two RAIDed disks (mirrored and showing OK during POST). The disk shows above as a6071eb5-6fc6-45b3-babb-c1a2156278d7. Ubuntu 10.10 installs fine from a LiveCD, but gets broken by kernel updates. I can see the original 1 TB disk when I start with the LiveCD and I can access all the files.
I use a pretty fresh installed RHEL 5.4, which should be very similar to Fedora. After the basic installation I installed xen and xen-kernel via yum with no errors. I can select the xen-kernel at boot time. But after booting the normal kernel shows up.
Upgraded to latest kernel 2.6.32-23. Ubuntu 10.04 I run a twinview video configuration of 2 screens @ 1920x1200. On booting, X wanted to go to low res for the session, which reverted to one screen (that is, I lost the twin view), but actually kept the 1920x1200 res on the one. I restarted X on got both screen working with the second as a replica of the first. Something has changed in this version of the kernel. Reverted to the previous Kernel version (22) and all is sweet (twin view is back working). But this can only be a temporary workaround.
I had 9.10 installed on my IBM Lenovo Thinkpad, x301. I was performing updates as normal, and chose the Upgrade button to upgrade me to 10.04. Everything started fine, but upon reboot, no bueno, Kernel Panic!
The exact message was "Kernel Panic ubuntu - not synching VFS Unable to mount root fs".
I thought this was a grub issue. Since grub2 now is installed... But it was not. I think it ended up being a problem with some of my configuration files.
I have three kernels I tried: 1. 2.6.32-22 2. 2.6.31-21 3. 2.6.31-20
The first threw me into the kernel panic. The second would hang on "init crypto disks" The third would hang on "checking battery state"
I noticed (from reading another thread) that while these are loading up that you can click on alt-ctl-F1 thru F6 and get prompt. (I also had my home directory encrypted, thought that was part of the problem, but it wasnt).
Once I get passed the loging, I am able to poke around. I tried manually start Gnome via "sudo service gdm start", but it failed. Said it was missing a configuration file. Then I tried on "sudo dpkg-reconfigure gdm" and it would not work. Saying some configuration files are missing or broken. It also said something about dpkg --configure -a, I am assuming this configures everything...
So I tried "sudo dpkg --configure -a" And selected 'y' to every option. Which basically installs the package creators default settings, and viola! Works.
Just wanted to share that knowledge for the other stuck in the upgrade hell.
Normally I would just copy my files off and reinstall, but it was encrypted... Another headache. I guess good in case someone stole my laptop.
I've been trying to get Ubuntu on my beloved 4 year old Acer desktop that's been chugging like a tank. However, after either a fresh install or upgrade, I would get the following error:"Kernel panic - not syncing: VFS: Unable to mount to root FS on unknown-block(0,0)".I've looked here and there, and one of the issues it would seem is the kernel not recognizing my hard drive if I'm correct. One of the suggestions was to upgrade the kernel however, I have no idea how to do such a thing if I can't get into the OS.
I just upgraded to 10.10 and now I am faced with a choice at boot up of which kernel I would like to boot (or recovery mode, or memtest).I am wondering how to default to the newest kernel without this prompt.
I've been running Ubuntu 10.04 AMD64 on our home theater PC through a wubi installation. Yesterday the system update installed a new kernel and today there is a problem booting the computer so I'm reluctantly using Windoze to type this. there isn't much information: the computer has always booted fine before the kernel update. When I select Ubuntu in the boot menu the screen goes black and the computer restarts. No error messages, no GRUB menu, just a blank screen before restart.
Upgrade from Karmic - was using EasyBCD in Vista. Tried upgrading to Grub2, reinstalling Grub - but can not boot to either. Here is my Results.txt file from [URL]
Code:
Boot Info Script 0.55 dated February 15th, 2010 ============================= Boot Info Summary: ============================== => No boot loader is installed in the MBR of /dev/sda => Windows is installed in the MBR of /dev/sdb
I have Ubuntu Mavrick installed on windows vista using wubi. it has been running smoothly since RC, when i installed it. now, after I updated using Update Manager last night I was asked to reboot. Upon rebooting i was not able to use ubuntu. the Ubuntu option is there on the windows boot menu but after i select it gruub does not appear. instead it reboots again. is there any way to fix this problem so i can use ubuntu again? if not how can i recover my ubuntu files and folders? Please help because i dont really want to reinstall after all the tweaking and stuff.
I updated my pc today, all went well no errors during upgrade. But I am unable to boot. I get the splash screen with Ubuntu and 4 coloured dots, then it goes and i get a page of txt. *starting apparmor profiles skipping profile in /etc/apparmor.d/disable: usr.bin.firefox plymouthd: ply-keyboard.c:384: ply_keyboard_watch_for_input: Assertion `keyboard != ((void*)0)' failed. *Setting sensors limits rather than invoking int scripts through /etc/init.d, use the service ( utility, e.g service s20plymouth-splash start Since the script you are attempting to invoke has been converted to an upstart job. you may also use the start ( utility, eg. start s20plymouth-splash Start: uknown job S20plymouth splash
If i leave it the screen just goes black I can get to ttyl by using ctrl&alt&f7 and log in.but thats about it startx just tells me no screens found I expect because xorg isn't used. If i go into recovery mode, failsafe graphics won't load either. So i select netroot and the enter startx which will give me a root desktop. I tried reinstalling grub, but no change. Not sure where to go from here i suspect it is something to do with plymouth? but i am no expert even tho i've been a user for 4 years
First I installed Windows 7 which worked without any problems. After that I wanted to install Ubuntu 10.10. (32 bit) The installation worked fine and the first boot also worked without any problems. Since then I get strange errors nearly everytime I try to boot up. I'm posting a "screenshot" as an attachment which shows the bottom end of the output before the system stops to work (Alt+Print+B is still working). I also get the same error when trying to boot up from a Live USB-Stick. It's quite random, around 25% of my tries are successful and the system boots up normally.
Things I already tried:
- Testing my RAM (no errors) - Booting with just one RAM block (same error, also tried a different one) - Installing 10.04/BIOS Reset/Installing from CD (same problem)
So what do you think? A hardware defect? Then I wonder why Win7 works fine.I would like to post a complete boot log, how can I do that?
I just updated my ubuntu 10.10 installation inside windows (wubi) and after that I shut down my computer. Later on I switched it on again and was unable to boot ubuntu. Ususally I first get the 'Windows boot menu' and after i select ubuntu i get the grub menu. Now, when I select ubuntu in the windows boot menu I dont get grub after that but instead the computer restarts. Is there any way to fix this issue without reinstalling ubuntu.
Today morning I was upgrading ubuntu 10.10 to 11.04. When the packages were downloading it was showing 20m left to download. At that time I had a battery of 2 hrs. As I had to go so I left my laptop on and went( the charger unplugged ). When I came back I get the following message code... I had Widows 7 also. Thank god its fine so that I am able to ask question.
It's become a tradition since I've installed FC6 on my machine: after each Fedora upgrade, the PC hangs at reboot because of a badly make initrd !
I found this post a while ago that helped me to solve the problem by rebuilding the initrd with the right librairies in it: [url]
So for each upgrade I've done the last 2 years I had to follow again these instructions to rebuild the initrd.
I've just finished the upgrade from F9 to F10 and I faced the following friendly message:
Code:
Allright, not a surprise in fact. While rebuilding the initrd I discovered there's no more /lib/i686/nosegneg/ directory in Fedora10's initrd. Therefore I reinstalled the libm-2.9.so library as follows:
Code:
Once the initrd rebuilt, I rebooted and faced a second friendly message:
Code:
I searched for posts reporting problems with segfault in ld-2.9.so but didn't find anything. So now I'm with a successfully upgraded fedora 10 system that refuses to boot.
By the way, I've done the upgrade using the netinstall CD, all the packages have been retreived online without errors and I think I've therefore the latest versions.
I recently performed a reinstall of ubuntu after mucking up my partitions, and I am running it dual booted with windows 7.
I recently performed a grub-pc update, but I didn't know what it was asking me to do during the process itself of updating the process.
It asked me at one point where to install grub, and I selected all my partitions because it suggested that if I didn't know. I think that may have damaged my windows section, which was also selection.
I've attached the output for:
Code:
Problem symptoms:
1) Weird upgrade error in apt-get 2) Unable to boot windows 7 3) Unable to activate proprietary drivers 4) Perpetually being reminded to restart
yestoday,after I upgrade,unable to boot windows xp. if I use grub ,windows xp can boot up.but now I want to use grub2, boot info script's results.txt is at below.
Boot Info Script 0.55 dated February 15th, 2010
Boot Info Summary: => Grub 2 is installed in the MBR of /dev/sda and looks on the same drive in partition #6 for /boot/grub. sda1: File system: vfat Boot sector type: Fat16 Boot sector info: No errors found in the Boot Parameter Block.
I am using DEBIAN 6.0 and I wannna update my kernel from 2.6.32 to 2.6.38. Every time, I do it but after the installation & rebooting into the new kernel it gives me error "UNABLE TO BOOT INTO THE KERNEL".
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?
After upgrading kernel package to 2.6.32-5 NVIDIA installation gave me ERROR:Unable to load the kernel module 'nvidia.ko'. This happens most frequently when this kernel module was built against the wrong or improperly configured kernel sources, with a version of gcc that differs from the one used to build the target kernel, or if a driver such as rivafb/nvidiafb is present and prevents the NVIDIA kernel module from obtaining ownership of the NVIDIA graphics device(s), or NVIDIA GPU installed in this system is not supported by this NVIDIA Linux graphics driver release.
Can't boot after upgrade to 2.6.31-19 kernel. Boot procedure stops on "Mounting root file system..." stage with message: /init: line 218: syntax error: 0xhda1.
I updated ubuntu and installed the latest linux kernel. I rebooted back into ubuntu, then finished up some work and went to reboot into windows 7. The "starting windows" logo comes up then it blue screens and says "cannot boot %hs missing" (hard to read because it flashed on the screen then reboots).I ran startup recovery but that didnt do anything. I also tried downgrading the kernel but that didnt change anything.
I am trying to upgrade from 10.4 to 10.10. I have never had a problem upgrading before with the Update Manager. Now I get an error message when using the Update Manager. The message says, "Could not calculate the upgrade". See screenshots. I also checked the package manager for broken packages and came up with nothing.
vmware virtual machine, the system is centos 5.4 want to upgrade the kernel 2.6.32. make menuconfig is based on the default. make; make modules_install; make install no problem, reboot the system to choose a new kernel, new kernel can not boot, the following is vastly map, right in the / boot directory, there is no 2.6.32 of the config files, do not know how the matter , in the compilation before I put / boot directory of the original system config files to the source directory cp The following is the contents of the screenshot
This morning, I booted into my administrator account and checked for updates. There were a number (bogofilter, for one) but also a update to the 2.6.32-24 kernel. I installed the updates and rebooted the system. When I rebooted, the thought occurred to me (from reading another thread) that one of the reasons my Zareason desktop boots slower than my laptop (55 seconds vs 35) was that I have an external floppy drive attached, and perhaps the delay was a difference in my system checking for a bootable floppy.
So I went into the BIOS when it was booting to check to see if the floppy was enabled (it wasn't). Then I selected "Exit without saving" and resumed booting. What happened next was instead of seeing the Ubuntu icon and the six dots, I see "Ubuntu 10.04" and four dots. Then I get on the black screen these errors (sorry for any mistyping, I wrote them down on a sheet of paper as I had no other computer available to troubleshoot):
udevadm trigger is not permitted while udev is unconfigured udevadm settle is not permitted while udev is unconfigured udevadm settle is not permitted while udev is unconfigured udevadm settle is not permitted while udev is unconfigured
ALERT! /dev/disk/by-uiid/939af864-c1a8-41d7-9b24-91d25685b6 does not exist. Dropping to shell Busybox v1.13.3 (Ubuntu 1:1.13:3-1ubuntu11 built-in shell (ash). Enter 'help' for built-in commands initramfs
Googling around once I got into work and had computer access, it seems that the problem is GRUB has lost track of what partition I should boot from? Here is a thread which might be relevant: [URL]. Before I left for work, I went into the BIOS again and looked at the CMOS settings--everything looked normal. I once again exited without saving anything. I was going to try selecting an earlier kernel from the GRUB menu on boot, but couldn't remember the key to press.
I found out later today, to enter GRUB 2 it's been changed to the shift key, and not the F2 key like it used to be. One poster on the aforementioned thread said his system would boot ok to the earlier kernel. The thread above has as its solution to either try to tell GRUB where your boot partition is and/or re-installing GRUB. I have /home on a separate partition, so if I need to do a re-install I can do so without it being a major pain. Sda1 is the partition which has the OS.
I cant boot into Fedora 10 using the latest kernel. It just hangs after grub, I can still boot into an older kernel. The problem is its a fresh install that I ran a full update on straight away, and now I cant install videoaudio drivers because the kernel-header packages (and others) are installed for the latest kernel. Is there any boot parameters I can try to add when booting that might help?
I know that error 15 means "file not found", but not how to figure out which file it is or how to point correctly to it.
I have tried to install the system on partitions on two separate disks, with the same end result. on the original disk I had some trouble getting through grub install, but on the other disk there were no indications of trouble during setup. can this a problem with the MBR on the first drive?
I have one drive connected by PATA, the rest by SATA, will SATA1 be (hd0)[grub] and /dev/sda [linux], is it the PATA drive, or some other means to determine this without examining the make and model of each drive?
I messed up my install so now I can't boot it. I get errors. I doubt I'll be able to fix it. I messed up the upgrade of the kernel images... I'm not sure whether there's something I could do in the Grub config file... I have one other Linux OS I can use in the meantime (plus Windows OS) so I thought maybe boot that up and check the Debian partition in case there's any files I want to save/keep. If I re-install, is Debian Squeeze LXDE still a good choice? I'm going to install something different in the partition where the other Linux OS is. Right now, it's grub is handling the boot loader. The computer is an old laptop, a Thinkpad T41. The HDD is 160GB.
I am running Debian squeeze. A while ago I upgraded my kernel to 2.6.38 from backports. Just now I thought it would be good to upgrade to 2.6.39 from backports. Upgrade went fine, but after rebooting I get a kernel panics rightaway.
"No filesystem could mount root, tried:" "Kernel panics = not syncing: VFA: Unable to mount root fs on unkown-block(0,0)."
This is the first time one of Linux installations halts/panics on booting, so I don't know what to do now. I tried booting the recovery entry from the grub boot menu, but same result.
After running update last night from 2.6.35.9-64 to 2.6.35.10-68 my laptop fails to start. Boot process goes most of the way to startup and then hangs just before login screen. Not sure what else to give as far as info.
