Ubuntu :: Unable To Boot After Kernel 2.6.32-24 Update
Sep 1, 2010
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 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".
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.
I had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
I have recently run an update and now we are unable to boot the newer kernel. We get stuck as below;
Memory for crash kernel (0x0 to 0x0) notwithin permissible range Red Hat nash version 5.1.19.6 starting Unable to access resume device (/dev/VolGroup00/LogVol06)
[Code]...
The kernel version we were at was 2.6.18-194.el5 and the update move us to 2.6.18-194.17.1.el5. I've done some googleing but I'm unable to work out exactly what I need to do. I'm guessing the new kernal is missing a module?
I am unable to boot my Fedora 14 after last nights kernel update. When I start the boot up and hit F2 the system fails after outputting the line : Starting vservers of type 'default'. At some point the console displays an error message :
serial8250 : Too much work for irq17
How do I restore my previous version? I know some people have suggested in the past - just modify the grub.conf but how? When I boot off the cd I only get access to the liveuser disk. I need to have access to my own /boot/grub/grub.conf file.
I have the following strange thing with a RHEL4 installation. Since last week, the system did a reboot and now something is really fucked up. During boot we get the following messages (don't care about 'strange' typo's, my colleague typed it 'blind' from the screen)
Code:
The strange thing is that we never see a 'could not mount blabla' or similar messages. First we thought it was a failing kernel update by plesk, but even after manually updating the kernel with RHN RPM's, still the same message. Booting with rescue mode and then chroot the system works. After that we even can start things like plesk and so on.
We double checked things with another RHEL4 install, and at least two things were odd:
1: the working machine has /dev/dm-0 and /dev/dm-1, the broken one doesn't
2: some files on /dev didn't have group root, but 252
We tried to recreate the /dev/dm-X nodes with [vgmknodes -v], output:
Code:
A fdisk /dev/sda shows: /dev/sda2 XX XXX XXXXX Linux LVM (I removed the numbers because this line is from another machine, but rest was identical)
We have a copy of the boot partition so if one need more info please let me know.
grub.conf:
Code:
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
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.
I have used Ubuntu since 8.04 LTS on my IBM T30 and A31 for almost three years now but recently all of them have problems with kernel updates(? maybe I am wrong but it was very clear that they failed after a kernel update). I have tried all three solutions provided by [URL] but none worked for me. My last A31 failed to boot yesterday after some updates (I noticed that there was a kernel update). It has 10.04 LTS on sda5. Dual boot (Windows XP on sda1 but rarely use it). Now it can't load kernel. What shows on the screen is:
GNU GRUB version 1.98-1ubuntu7 Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists possible device or file completions. On the other T30 I had the same problem. I installed Windows XP and clean installed Linux Mint 8 and so far it is working alright. But on this machine I have an unfinished project that I really want to save it.
Update manager reported some updates including kernel update to version 2.6.31-19.
after update system won't boot. it crashes into bash shell. I've manually loaded kernel version 16 with following command code...
same thing happened when version 17 came up. I definitely NEVER again going to update kernel. What do I need to do now? should I uninstall latest kernel...if that is possible?
I've just updated (through Update Manager) to the latest Linux kernel, (2.6.32-23, I believe) and now Ubuntu will not boot to the desktop.
It gets as far as finishing fsck on all of the drives, and successfully completes checks if necessary, but after that it just comes to a halt and won't proceed any further.
The last messages on screen when it freezes are (ignoring the fsck success reports):
init: ureadahead-other main process (954) terminated with status 4 init: ureadahead-other main process (959) terminated with status 4 init: ureadahead-other main process (970) terminated with status 4
These messages were appearing before, though.
The only way I seem to be able to boot now is by selecting the previous kernel (2.6.32-22) in GRUB.
Is anyone else seeing this, and does anyone know how to fix this Ubuntu update problem?
After getting everything running nicely on 10.10 (after dozens of installs - long story, partially raid problem, partially noob, partially partitioning and Windows), I'm stuck with an unbootable 10.10.I selected all the "important security updates" when the update manager told me I needed to update everything. Upon rebooting, and picking ubuntu in grub, I get:
Error: unknown command 'record fail'Error: cannot read the Linux header Error: you need to load the kernel first Not exactly sure why at this point. Can anyone point me in the right direction? I can probably get in either through a 10.04 version that I have on another HDD, or through the livecd.
Note: if it's important, I did not elect to install the ATI proprietary drivers, and this is also the first update that I've done after installing medibuntu - a few boot cycles in between, so I don't think it's related.
This week my ubuntu 10.10 was updated via update center. I obtained the new kernel headers 2.6.35-23-generic but now I can't boot using this kernel version and I have to select manually 2.6.35-22-generic in grub. I can see the ubuntu plymouth splash screen but it never rise gnome. where are the boot logs and how to activate them, In /var/log/ I have "boot" file but is empty and in "boot.log" I cant see any usefull information (I have BOOTLOGD_ENABLE=yes in /etc/defaul/bootlogd).
After a kernel update ubuntu would not boot. So found this procedure using the live update cd. Update grub.cfg & delete everything down to but not including the first line that starts with 'menuentry' . Then boot works ok. A couple of weeks ago it started on my notebook. Is anyone @ hq listening & able to fix this problem permanently?
I used the update manager to update the kernel and whatever the other recommended updates were yesterday. I shut the computer down overnight and now when i try to boot into Ubuntu 9.10 i get a basic grub shell and when i try commands like "boot" it tells me there is no kernel loaded. I installed Ubuntu with Wubi so it is a dual boot system.
I've tried to access the Linux volume with a live OpenSuse 11 CD but there is no device to mount. It sees the entire hard-drive as if it hasn't been partitioned. I don't necessarily need to fix the installation. I just need to get my files back.
So I ran the update manager to install the latest kernel. It goes fine and was sitting at the restart prompt. I was playing minecraft and the entire system locked up - couldn't restart X or anything. Hard restart and I get a multitude of errors mostly dealing with not being able to find things in /dev/... It gives me a command line but I'm lost as to where to go from here to repair my system
The most recent kernel update, to version 2.6.38-11 has been a horror. It hangs on boot up. Sometimes I can get to the log in screen, then it hangs there as well. However, after 3-5 reboots (which is absolutely annoying to do when I just want to use my computer), it sometimes loads up finally. However, if I go to older Linux version in the Grub menu, then I can select 2.6.38-10 and it runs just fine.
So I am looking for a way to fix this problem, whether it be removing the most recent kernel update, or making 2.6.38-10 boot up by default. I noticed that the kernels are listed in the synaptic package manager, but I am afraid to remove the most recent one via synaptic. Is it as simple as removing the Linux version and headers I don't want, or are there other things I need to do in order to make 2.6.38-10 my default kernel at start-up?
I just updated my kernel to kernel-2.6.29.5-191.fc11.x86_64 on my x64 system, after I reboot my machine, the Fedora loading bar comes up and finishes but then no gui comes up. I attempt to issue commands at the hanging prompt that comes up but nothing happens. I can boot into my older kernel just fine but not the updated one.
I've run today command: "sudo yum update" and I've noticed that the new kermel have been installed (2.6.31.12-174.2.3.fc12.x86_64). After that installation .. my camputer has several errors while booting and it doesn't want to start. So while booting I can see Code...
I ran the update through yum (replicated results twice) and whenever I boot to the new kernel it either freezes on the F logo or screen goes black right after f logo. No commands work whatsoever (tried em all). I can boot to an older kernel (2.6.33.3-85.fc13.x86_64). the ones that fail are: 2.6.33.6-147.fc13.x86_64 and 2.6.33.6-147.2.4.fc13.x86_64.
The Fedora error system gave me a bug report I submitted, here's what I got:
Package: kernel Latest Crash:Tue 03 Aug 2010 09:46:33 PM Command: not_applicable Reason: BUG: unable to handle kernel NULL pointer dereference at 00000000000005b8 Bug Reports:Kernel oops report was uploaded
After updating my kernel from 2.6.34.7-56.fc13.i686 to 2.6.34.7-61.fc13.i686 I can't boot anymore. The error message says: "No root device found Boot has failed, sleeping forever." I'm booting from 2.6.34.7-56.fc13.i686 now but I would like to sort this thing out. What should I do? File a bug? I never did that, so I don't know where to go.
I have 10.04 installed on my daughters Laptop. After running an update manager session, the system asked for a restart. After restarting the Laptop won't boot up. Get a black screen scrolling with lots of hex addresses then 3 unable to mount messages ( mounting to /dev /sys /prod ) then a no init found message, followed by entering a busybox shell session which leaves me at initramfs: I'm a newbie at this linux shell stuff and don't want to make it any worse by scrabbling along blindly! System is a dell Inspiron 1501, Ubuntu is installed on a clean formatted single partition.
I have recently updated my Fedora 11 installation which replaced my older 167 kernel with the newer 217 kernel. However, the 217 kernel will not boot completely. It will show the splash loading screen, and then will switch to a rapidly blinking cursor. This cursor blinks for about 5 seconds and then disappears. I can access terminals using ALT+F2, etc. I can log in to these terminals, but init commands do not complete (something about a binary handler). I'm not sure if something is conflicting with an update to X or what is wrong. The most recent kernel that I managed to get to work was Kernel 167, however I cannot find this kernel for download.
Sys info: AMD Athlon 64 X2 4800+ 3GB RAM nVidia GeForce 8600GT with proprietary drivers 320GB Hard Disk with windows and linux partitions Fedora 11 32-bit i586
I tried to update my f12 today. In the list it showed an update for kernel-2.6.31.6-145.fc12.x86_64 It all seemed to go OK but when I restated my computer it spit up an error and wouldn't boot"Could not load /lib/modules/2.6.31.6-145.f12.x86_64/modules.dep: No such file or directory"Luckily the old kernel still works.
I do have the disk encryption set, could this be related to that? Updated my laptop today with the xx.6-145.f12.PAE kernel and now it's borked to. Same problems.12/07/2009OK today's kernel update seemedto fix the problems and now all is well, execpt for my inkscape not working problem. But I put ubuntu 9.10 in a VBox and it works. So for now that's my work around.
Hello, i recently update the kernel in fedora through the GUI update manager and after restarting the new kernel wouldn't boot and i had to reboot into the old one. it freezes right after Plymouth finishes and the login screen should show up it just completely freezes, i do have proprietary nvidia drivers could it be that?
I upgraded the kernel of my machine with a yum update, and now it will not boot. I am running Fedora 14 on a 64 bit machine. I really really need it to boot. Help!
I did Ctrl+Alt+F2 and managed to log in. I have kernel x86_64 2.6.35.12-90.fc14 installed. How do I log in as usual? I never get to a login screen.
