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
View 2 Replies
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:
Code:
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?
View 9 Replies View RelatedI 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.
Dual Boot: Fedora 12 and XP Dell 505I've had trouble with the latest kernel update.I updated a bunch of packages recently (including Xorg and kernel), and noticed a severe flickering after the update on my center monitor (Samsung T260 - the laptop display did not exhibit the flickering behavior). I backed out all the changes and started updating package by package. After I updated the kernel (again) I rebooted and here's where the fun part is -
I no longer get anything, except the cursor. No grub menu, no grub prompt. I rebooted and ran the rescue disk and followed the procedurery and point grub at the right boot partition - see here. However (obviously or I wouldn't be posting) that failed to work. I still get a blinking cursor and dead system on boot up.
I am unable to boot with kernel 2.6.35.13-92.fc14.x86_64 which was installed while applying software updates. It hangs with the last message issued "Registering binary handler for Windows Applications". Searching led to it being related to a problem with the nvidia drivers. I followed the directions in several posts - delete /etc/X11/xorg.conf, reboot, run nvidia-xconfig, reboot and all is fine, but not in my case. The first reboot works but the screen is wrong. There is a 1 inch wide black border around the presentation window. If I then do the nvidia-xconfig and reboot, i am back to where I was before - boot hangs after issuing "Registering...". If I boot to the last good kernel, everything works fine. This happened to me once before and I was able to fix it by rebuilding the nvidia kernel (I think that was what I had to do), but I can't find out how to do that. I have akmod and kmod installed which are supposed to take care of this problem. I booted to kernel 13-92 recovery mode, deleted the xorg.conf file and ran nvidia-xconfig from there. Still fails. I don't know what to list here, but I will do my best to supply whatever is necessary.
View 1 Replies View RelatedSo I just installed Karmic onto my netbook that used to have Jaunty on it. As usual I did a system update after the clean install finish. In that update it included a kernal update to 2.6.31.19. As far as I know the update went fine.So when I restarted, after the usual bios screen, it just freezes. Some gibberish comes up and nothing happens. I did a hard reset. Then when bios came up again, I chose boot option, and then clicked to boot from my hard drive. GRUB came up (finally) and I chose the old kernal and it booted fine.
Just for good measure I tried booting from 2.6.31.19 and the same strange freezing thing that I mentioned in paragraph two happened.
even from a terminal it wouldn't update? Maybe because I put my bootsector as ro ?
I don't know here is the message:
I was updating the kernel and left the computer to let it do its business. There was power failure and I don't know if the update completed or if it was in the middle of it. Now if I start the computer, it freezes up at the login screen. I tried to recover from grub, by selecting "Ubuntu, with Linux 2.6.32-21-generic (recovery mode)". There were no prompts for input after this. The recovery screen is not updating anything after:
[2.348886] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
[2.349015] EXT4-fs (sda1): write access will be enabled during recovery
[2.577641] EXT4-fs (sda1): recovery complete
[2.578072] EXT4-fs (sda1): mounted filesystem with ordered data mode
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
Done.
When I come out of that screen (ctrl-alt-del), the problem repeats.
I admit, my knowledge of LINUX isn't that great. That said, I thought I'd be able to pull off a basic upgrade (clean install of a whole new kernel, not patching the existing one) from the latest 2.6.31 in the ubuntu repo (I think it's 2.6.31-19.54 to be exact) to 2.6.33 (kernel --latest-stable) from source. I got all the config done, compiled it, and updated GRUB, rebooted to find that it had a "2.6.33.old" entry in the menu (not particularly relevant, I admit) even though I only ran the "make install" command once. Anyway, when I selected the non-old entry, it churned for a moment, gave a couple of weird screens for <1 sec each, and then gave me an error about a missing graphics module (I'll look for how to automate loading modules on my own, and see if I can port the existing NVIDIA module from my working kernel to the newer one) and gave me a list of options like "boot into graphics safe-mode" "boot to login shell", etc. and the mouse wouldn't work, so I had to use the keyboard to work the screen (i chose the shell login, since I didn't feel like seeing ubuntu's butchered face while it's in "graphics safe-mode"). I managed to get the computer to boot into the stock kernel, and am now wondering the following:
1). Do any of you guys out there think it's worth trying to save this kernel update?
2). How do I go about removing the "2.6.33.old" kernel & entry? (i've tried synaptec, the "make remove" and "make auto-remove" commands with no success.)
So when upgrading to 10.04 there were a few errors and now the machine will not boot up. All I am trying to do now is recover some pictures from the HD so I can to a clean install. I used the Ubuntu 9.04 install disk to gain access to the HD and was able to backup some of the files but other files are locked somehow. When trying to copy them it says that "folder content could not be displayed. You do not have the permission necessary to view the contents." The files in question have orange X's on them.
View 3 Replies View RelatedI'm experiencing some rather severe problems after updating my Centos 5.4 system (Virtual Xen guest). What happens is that when the system boots it complains about missing .so files which prevents about 50% of the services installed from running.
I'm suspecting that it has something to do with selinux for two reasons: 1. The first services to go down complains about the security context of some files, and 2. selinux was kinda the reason I decided to update in the first place as it was disabled when it shouldn't be (enabled in system-config-securitylevel, disabled when running sestatus).
The whole boot-sequence ends with alot of "INIT: Id 'X' respawning too fast: disabled for 5 minutes"-messages (including all runlevels) before it goes stale, and I can do nothing.
The server in question had undergone very little tinkering from my part, pretty much none at all, the only services installed after installation was apache, mysql and webmin.
Details:
CentOS 5.4 is installed on both the host and guest.
The guest runs on an lvm-partition.
I have two other vm's(also CentOS) running just fine, altough I'm a bit weary of updating them .
Attached are some screenshots of the boot-process.
I hope some one here can share some insight on this problem. It's making me pretty nervous seeing that our whole network is run by CentOS-installations (not that I'm certain that CentOS is the culprit).
Lately I'm encountering a somewhat annoying malfunction: almost every boot, my desktop is stuck, HD red led is constatnly on, and i get a message from kerneloops that I had a kernel failure. I can move the cursor a little and slowly or not at all. Few violent reboots and I get a clean boot. Running Debian Lenny kernel 2.6.26-2-686 on a Pentium 4 2.0 GHz with 250 MiB ram.
View 4 Replies View RelatedI have just updated my kernel and immediately struck trouble. The kernel update is marked as security update.
When booting I get a multiple warnings " deprecated config file /etc/modprobe...", then "no root device found" followed by "boot has failed, sleeping forever"!Clearly something is amiss with this update, so figured the best thing might be to remove it and wait on a fix, but attempting to remove the kernel via the package manager would cause a whole lot of other packages to be removed as well.Instead, I edited grub.conf, commenting out all the kernel-2.6.34.7-63 lines, so that the default is now the previous kernel (2.6.34.7-61).
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.
Computer: Dell Hybrid 140G, Intel Core 2 Duo T5800, 4GB RAM
How do I install an additional kernel in Linux Ubuntu 10.10, in case of a boot failure? Also how do I make the Grub Menu Visible, so that I am able to select multiple kernels. There is an older solution below, but is there a way to do this in Linux Ubuntu 10.10. I just suffered an update failure, possibly due to a corrupt kernel upgrade, which made my system unbootable. The cursor just flashed continuously.
Solution of 2007[URL].... "The next obvious rescue aid is to always have a working kernel installed. I usually work from a kernel updated via yum. Kernels have occasionally been released with flaws that have caused one or more of my machines to not boot. To this end, I always make sure I have at least one perfectly running kernel on a machine. A great way to handle this is to first add plugins=1 in your /etc/yum.conf file. The next step is to take this script (written by Jeremy Katz from Red Hat) and save it as n-installonly.py in /usr/lib/yum-plugins. You can change the number of kernels to retain on the system by changing the tookeep variable (default = 2).
With a known working kernel on your system, you can upgrade safely. If the new kernel is hosed, simply boot the old kernel to solve the issue with the new kernel be it to remove it, recompile it, or update it."
After performing the periodic update on 2010-05-26 including libc, libc6 and libgtk2.0 my system fails on boot with the following error message:
Code:
run-init: /sbin/init: no such file or directory
Kernel panic - not syncing: Attempted to kill init! If I boot from the 10.04 live CD, all partitions on the hard drive are visible, mountable, and pass all file system checks.
This morning my update manager came up so I clicked to update. About halfway through the update an error message popped up & said to restart my system. I restarted my system and now have a black screen with the following message:
mountall: symbol lookup error: mountall: undefined symbol: udev_monitor_filter_a
dd_match_subsystem_devtype
init: mountall main process (344) terminated with status 127
I read around earlier & tried to use a Ubuntu disk and reboot but I have the same error.
I'm using a Dell Inspiron computer, it's just over a year old. I keep up with all the updates but unfortunately cannot say for sure which updates were taking place because I just hit the update box.
my left mouse button on my Acer laptop stopped working out of nowhere. While searching for a solution I started the upgrade process. Without thinking I restarted during the upgrade installation, which has apparently caused some big problems.I cannot boot any longer. I get the Ubuntu splash, then a slowly flashing black screen.I am able to boot to the Live Cd without any problems, but I'm not sure what to do from there.I'm been searching the forums, but can't find anything.
View 7 Replies View RelatedI was having problems performing an update yesterday that failed on dovecot dependancies and after a few tries I removed dovecote (it wasn't being used) from the installation and tried again. Everything seemed to be going OK then the update (about 160MB) hung and the screen went black a few times and I think then shutdown automatically. The PC then fails to reboot and displayes the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" I have tried to get the PC to boot with the super grub disc but without success (probably my in experience) I have also tried a suggestion from one of the forums to start the PC with a live CD and typed su -c 'grub-install /dev/sda at the terminal again without sucess. I have looked at the files with the live CD there are grub, menu and kernel files there (some are in lost + found, b ut don't know wheer these should be so have not changed anything.
Is there an easy way for the in-experienced to repair the boot process ?
The PC is a pentium 4 running Fedora 13
There is a 200MB boot partition formated as Ext3
and a 19GB partition formated as a LVM with Ext4
There is a CD drive but no DVD
Everything has worked OK for the past year through two online upgrades.
I was finally able to install Fedora 11 x64 after choosing to only install packages from the repository on the install DVD. Prior to that when I had chosen tio install from the default online repositories, the install itself failed with a Python exception ( see my other post ). Now, however, once I boot after the install I eventually receive a kernel panic message, and failure. The exact same thing happened with CentOS 5.3 x64 after a flawless install. So unless someone knows what might be going on I will assume that Fedore, Red hat, and offshoots for x64 bit systems are just not for me. I have been able to successfully install the latest Mandriva and SUSE x64 Linux distros so whatever Red Hat/Fedora has done just does not work on my system.
View 3 Replies View RelatedI 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".
View 1 Replies View RelatedToshiba notebook is set up to triple boot win7, mepis 8.5 and os 11.3.Recent update of os11.3 left system with boot failure, "file not found".I booted mepis and used utility to reinstall grub, but no joy.
Appeared to install ok but on reboot, sda5 identified as 'mepis' not os11.3 and would not boot. Win7 & mepis boot ok.
Next, booted live Parted Magic and repaired as per another thread here, but again, no joy.NONE of the systems will boot.Rebooted mepis live cd and reinstalled grub again. Sda5 still identified as mepis and will not boot. Win7 & mepis boot ok.
After some updates Jessie 8 my boot grub shows now 2 kernel versions to boot from.
3.16.0-4-amd64
3.16-3-amd64
- How do I know which one is the newest and if happy with it, how to remove the older one?
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.
I was using 2.6.28-14 kernel version, it update me to 2.6.28-15. Now I have upgraded kernels many times, not first timer, but this is a first to me. So I have this wierd system setup, don't ask. Where I use lilo instead of grub, just take it as it comes guys, I have to. At any rate, it upgraded all fine, and I restarted, play the blues I got a "No setup signature found" error and lilo won't boot. So I did some searching on web and everyone says to boot up CD and re-install lilo. Well with grub I've done this many times, no prob bob, but lilo won't work.
So I used my super auto grub CD to try to re-do things. Since grub config and grub was still installed on my Linux partition I tried it right. No go of course, grub says it can't find the partition nor can it mount it. So I tried the beta of lilo on the grub cd and it don't work either. Botched it up worse, first it wouldn't do anything on my second drive, just sat there black screen. Then I did it a second time, let's screw it up some more right. Now it doesn't even find a boot loader in the MBR ha ha.
So at any rate, how in the sam heck do I fix this thing? Short of downloading 10.04 and re-installing everything?? Don't want to do this, too much work when I can just upgrade and keep my stuff installed and setup. So I tried running jaunty from CD and re-loading lilo. So everything is working fine right, I mounted drive and apt-get install lilo and ran lilo. So lilo even telling it what config file to use and where won't find things and won't re-install. So just for grins, even though I thought it wouldn't work I mounted my second drive linux partition, the one with the boot info on it, you ready, to root "/". Then I couldn't unmount
The 486 kernel works just fine, and while I have only 1GB of RAM at the moment I hope to have 2GB someday and would like to take advantage of the dual core CPU, so I would like to configure grub to run the 686 kernel by default. For whatever reason, it runs the 486 right now and the 686 fails in a major way: there is no network connectivity at all. It could be plugged into my cable modem router and it shows no wired connections. The fact that one works and the other doesn't puzzles me since I haven't touched either since the install and a few rounds of upgrades.
I should mention I'm newbie but getting better; I managed to install debian on this x60, yet while preserving the factory install rescue & recovery partition and preserving the factory install MBR so that ibm-specific hardware functions (thinkvantage button, etc.) still work. This required me to use dd to copy the first 512 bytes of my debian partition to a file in the windows partition, etc., and modifying the windows bootloader. (I wish I had learned dd long ago--it rocks). I did this because if I ever resell the X60, the fact is most people use MS Windows and having that partition adds a perception of value to some potential buyers; not to mention I paid $ for it (I was young & stupid) so why should I delete it. I also backed up the recovery partition on another drive using dd over NFS in case the hd ever heads south.
Anyway, I've never been comfy with messing with the kernel. I did once recompile a module for ALSA because it had a bug in it for an old Yamaha integrated sound card on an old PIII and the newer version worked [alsa fails on this x60 too but I think I found a post on here that has a solution I will try later]. But I'm clueless as to networking modules, not to mention the correct module is installed already from Intel for this chipset. So what is there to do?
Here's a clue: the ifconfig output is radically different from the 686 and 486 kernels. Looks like hardware is not being detected since eth0 fails to show:
I would show the diff output below if it weren't so long--and not allowed--upon 2 text files, the first holding the output of modprobe -l under the 486 kernel and the second under the 686 kernel.
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.
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?
