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.
Finally updates are broken - I've been able to use my upgraded F12 system for some time, faithfully keeping up with f10, then f11. Just yesterday it finally broke:
Test Transaction Errors: installing package kernel-2.6.31.12-174.2.22.fc12.i686 needs 10MB on the /boot filesystem
It would appear that the most recent kernel update has broken the 10MB barrier initially set by the version I first installed (for the boot partition). Needless to say, I have quite an investment in this machine, and of course no time to back it all up and do a fresh F12 install. I am hoping someone out there can give me a bulletproof way to steal some space and expand the boot partition...
I just tried to update to kernel 2.6.27.15-170.2.24.fc10 (x86_64) at the suggestion of the gnome update widget, and the process hung. A bunch of other things were updating at the same time, many of which were related to audacity or wine.
I'm not sure just what was being updated, because the option to review which updates are available does not work - when I click on it, nothing happens, but when I take the other choice (install all updates), I take pot luck. It would be nice to be able to choose which programs to update, and to be able to upgrade the kernel independently, but I don't seem to be able to do that at the moment.
Googled this and found the same problem mentioned in the yum site:
[root@plouton ~]# yum update kernel
Loaded plugins: refresh-packagekit
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package kernel.x86_64 0:2.6.33.6-147.fc13 set to be installed
--> Finished Dependency Resolution
--> Running transaction check
---> Package kernel.x86_64 0:2.6.33.4-95.fc13 set to be erased
--> Finished Dependency Resolution
Dependencies Resolved
As the post title says I have attempted to move my FC11 from a 120 gig ide drive to a 250 gig sata drive. I have tried all of the following with the same result listed below: Basic setup is as folows:
old hdd /dev/sda1 (boot) /dev/sda2(swap) /dev/sda3 (/)
attempt 1- boot fc11 live cd with old drive detected as sda and nwe drive detected as sdb.
dd if=/dev/sda of=/dev/sdb bs=512
attempt 2 - boot into fc11 live cd fdisk remove old partitionon /dev/sdb and create exact copy of partition table on /dev/sda on /dev/sdb - mark /sdb1 as bootable and copy /dev/sda1 + /dev/sda3 to /dev/sdb1 and /dev/sdb3
dd if=/dev/sda* of=/dev/sdb* bs=512 (* denotes 1 or 3 respectively)
attempt 3 boot linux rescue cd based on debian
run gparted to remove old partitions on /dev/sdb
use gparted to copy partitions from /dev/sda to /dev/sdb
All of the above result in the following (as best as I can describe it)
system self checks OK
system loads GRUB menu -OK
system appears to load kernel and then hangs after outputting device information regarding my USB keyboard and mouse.
Is there some magic that I am missing? system.map perhaps? Additonal info: grub.conf looks like:
# 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
[code]....
The boot process fails using; 2.6.30.9-96.fc11.x86_64. I am able to successfully boot by selecting 2.6.30.5-43.fc11.x86_64 from GRUB. The last few messages I receive when booting using 2.6.30.9-96.fc11.x86_64;
ADDRCONF (NETDEV_UP): eth0: link is not ready
Sky2 eth0 link is up at 100 mps, full duplex flow control rx
ADDRCONF (NETDEV_CHANGE):eth0: link becomes ready
audit (1257757711.701:20095): auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 op=remove role key=null list=2 res=0
audit (1257757711.701:20096): audit_enabled=0 old=1 auid=4294967295 ses=4294967295 subj=system_u:system_r:readahead_t:s0 res=1
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.
What can I do?
The girlfriend did an update a few nights ago. Besides removing her NVidia drivers, it also installed kernel version 2.6.27.29-170.2.78.fc10.i686.
That kernel was causing problems. Now it won't boot at all. How do we remove that kernel altogether?
If we remove it, would simply doing another update from the previous (still working) kernel just try to reinstall that bad kernel?
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 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.
View 12 Replies View RelatedI 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.
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.
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?
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.
I have just updated my kernel to version 2.6.38.8-35 in Fedora 15, it now refuses to boot that kernel. I just get a lot of text on the screen and nothing happens. I can ctrl-alt-fn to get to a prompt, but I do not know how to fix the nvidia problem.
When I edit Xorg.conf and replace 'nvidia' with 'nv' the new kernel boots but only to fallback mode, trying to then re-install the nvidia drivers shows them to be already installed and I can get no further.
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.
Update to 5.3 went OK a few days ago.Today there is updated kernel packages available but it fails dependencies on ecryptfs-utils.
View 3 Replies View RelatedIt appears that I have really messed up my machine. I was trying to get matlab working on FC 11 and I ran into libc.so.6 issues, so I put an older file libc.2.3.1.so in /lib/tls/ directory and created a symbolic link libc.so.6 to see if the application would work. Unfortunately at the same time the system did some updates and the system hung, so I ended up rebooting, but now it gets stuck at boot screen (after grub) with a kernel panic - not syncing: attempted to kill init.I just need a way to get to the directror /lib/tls and delete the link and the older .so file I threw in there. How do I get this accomplished. I cannot get even to a shell from the boot screen.
View 3 Replies View RelatedSince doing the update which included kernel "2.6.32.16-141 fc12-i686 PAE" I can no longer boot into my usual 1280x960 desktop. I can set it using NVidia settings but even though this offers to modify xorg.conf it fails to do so. I have tried running as root and it doesn't then give an error message but when I look at xorg. conf there is no section.showing any specific screen size. It worked ok before the update. In case it is relevant the video card is a Quadro FX1400 with KDE. Also the whole program seems rather unstable since the update.
View 10 Replies View RelatedI have a problem with the kernel update to 2.6.34.6. Up until 2.6.33.x my system boots fine, but with this update the boot stops at the moment that the mouse cursor should become visible. To resolve the problem, I've gone back to 2.6.33.x and removed the 2.6.34 kernel but I wonder what happens with the next kernel update.
Anyone else having this problem?
I'm not sure what caused it, but it happened right after running 'yum update'. It may be because it installed a new kernel, and there are now two kernels listed in my grub.conf and at boot; 2.6.31 and 2.6.32. System boots through a list of things it's starting up and stalls out at ATL or ADL or ADM maybe. It hangs there for a minute or so then flickers. This happens every time at boot. It's a bit difficult to post more information since I can't get past that part of the boot process, and I can't seem to be able to skip it either. It may be worth mentioning that this is a mini-itx motherboard. Intel Atom 330 1.6, 2GB DDR2, onboard GeForce 9400m. It's a zotac ionitx-a-u. I've installed a fresh copy of Fedora 12 lxde.
View 3 Replies View RelatedI recently got the Message, that i should do a partial System Upgrade. It included an update to Kernel 2.6.34. Since this update, i cannot boot with this kernel:
Code:
Mounting none on /dev/ failed...
i can still boot with older kernels, but many drivers including wifi and graphics drivers dont work there anymore.
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".
View 1 Replies View RelatedI 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:
New kernel Fails to boot. video driver is current and I tried reinstall . The .19 Kernel works fine
View 2 Replies View RelatedSo I just finished doing a Hardy based LiveCD. I made an installation in VirtualBox, installed some packages, and then compiled a totally new kernel, 2.6.35, actually this one: [URL] I compiled squashfs support in the kernel naturally Everything seems to be fine, the system boots up normally etc. But here comes the trouble: I make the iso file with remasterys (2.0.12-latest for Hardy) but this iso isn't able to boot.
It drops to busybox shell, casper.log says: /init: 1 /dev/sr0: no such file or directory Unable to find medium with the livesystem. My /dev folder is totally empty, it contains only the shells (8 pieces of tty). I don't know what's wrong...my rootfs is surely mounted, mount shows rootfs rw /
Because I am using one of the new WD disks I am trying to aling my root partition with the real sectors, as described here: [url]
So I copied all files to a temp location, deleted my partition (/dev/sda3), recreated it a few cylinders later (same name) and copied the files to the newly created partition. I updated UUIDs in grub's configuration as suggested in this thread:[url]
But now it fails to boot with the following error:
Code:
I checked the filesystem on this partition and its fine. I tried to recreate the initramfs from Knoppix:
Code:
But it didn't change anything.
How can I either fix it or install a different kernel on this drive so I could boot into it and re-install my default kernels?
I had to install grub manually after the install. GRUB loads fine and I can select the Ubuntu option, but it simply stays on a purple screen with no HDD activity. When I go into recovery, it falls to a busybox command-line and says "ALERT! /dev/disk/by-uuid/(string of letters and numbers) does not exist". I use a RAID array which causes me loads of problems, but I'm fairly sure, from what I've read of similar problems, that this is due to the update it did during installation. I suppose I could try installing it without internet connection, but then presumably the same thing would happen as soon as I ran update-manager? I have actually tried the reinstall several times as well as reinstalling GRUB.
View 1 Replies View Related
