I saw the Bugzzila Strobe Light Icon was active and it said that it has found a kernel problem. After clicking the icon, the unexpected happend, my system crash completley.
After rebooting, here is what im getting.
Can't mount root fulesystem
Boot has failed, Sleeping forere.
First time trying anything like this. I'm running a Abit NF7 with a silicon image 3112 that's support was broken in 2.6.35. I get a kernel panic when VFS can't find the root partition, I can't remember the exact line (can't log it, root isn't mounted yet) but it says something like sata1: link down (sstatus 0 scontrol 0). I think there might be a more telling error message before, but it flies by too fast to see or capture with my camera video recorder.
There's a patch that reverts back to when there was a delay in /drivers/ata/libata-sff.c in the function ata_sff_tf_load, by calling ata_wait_idle(ap) which fixes the issue for some people but not my system. I don't know anything about what I'm doing, but I thought I'd go through and add printk's in each function in sata_sil and see how far the device was initialized. I did this but they all happen early in the boot that flies by. Is there any way to add a pause like the "more" command? [URL]
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)
View 2 Replies View RelatedI 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.
[root@noname boot]# uname -r
2.6.18-164.11.1.el5
My /boot/grub/menu.lst looks like:
default=1
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
[code]....
I can't see anything wrong and I did not change/try anything.
I needed to use CIFS for accessing a NTFS network share. I decided to include CIFS in the kernel and tried compiling and installing it. Now when I (try to) boot in my new kernel with CIFS support, I get the message: gave up looking for root device.
View 5 Replies View RelatedI 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:
Code:
Kernel Panic - not syncing: VFS unable to mount root fs on unknown-block (0,0)
EDIT: Here's the content of grub.conf
Code:
# 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]....
What is peculiar on this grub.conf, is that the 2.6.33.6-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 2.6.33.3-147 kernel is also missing (i.e initramfs-2.6.33.3-147.fc13.i686.PAE.img).
I updated the kernel to 2.6.35.10-74.fc14.x86_64 and had to reinstall and rebuild the kernel module for my ATi driver as usual, so I edited the kernel arguments at the grub splash screen so that I could boot into single user mode and install the driver (i.e appending the relevant line with '1'). The interesting thing is, the system booted directly into single user mode as root when the system started up. No password was required.
View 6 Replies View RelatedMy 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 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 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 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 just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).
Installation went fine, but upon the initial boot, I get:
Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)
I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13Here's the tutorial:Quote:Originally Posted by leigh123linuxF13 Howto for the rpmfusion nvidia drivers This is a Three-Step Process. If you don't follow all three steps, your install will fail!1. Install the nvidia driver. ( if you have 4Gb of RAM or more you will probably have a PAE kernel [32bit only] so follow the PAE part )For GeForce 6, 7, 8, 9, 200 & 300 series cards
Code:
su
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-
[code]...
I am running FC13 on a fairly old PC (PIII 500MHz, 384MB RAM, 10GB SCSI disk). It works fine using kernel 2.6.33.5-112.fc13.i686.PAE. After a series of recent updates the system now also has a new kernel 2.6.34.7-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
initrd /initramfs-2.6.34.7-56.fc13.i686.PAE.img
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-2.6.33.5-112.fc13.i686.PAE
-rw-r--r--. 1 root root 112291 Sep 15 04:32 config-2.6.34.7-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
which gave:
[root@localhost 2.6.33.5-112.fc13.i686.PAE]# ls -l
total 3300
lrwxrwxrwx. 1 root root 51 Jun 3 00:52 build -> ../../../usr/src/kernels/2.6.33.5-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!)
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
[Code]....
I'd like to run a script as root at boot. So far, I've tried that : [URL]...ript-boot.html , but it did not worked. By the way, I'm not even sure that it is the good way to do.
View 2 Replies View RelatedI am trying to install Ubuntu 10.10 from a USB flash memory stick. It works fine until around 95%, where I get the following warning/error:
[Code]....
I click OK and the installer seems to finish nicely, except the terminal throws several errors along these lines (see photo):
[Code]....
I tried also with 10.04 LTS, the difference being that the install warning appears two or three times instead of once. Some results from googling (Ubuntu Forums, Ubiquity bug) suggest unchecking the initial update options. I am going to try this but I'm not sure if I'll be able to get the boot loader right (there seemed to be problems with this).
After a kernel update, the system always updates the GRUB menu, and the newer kernel is the default boot option.However, after an update on my F13 X64 system, the GRUB menu was updated, the config file still sets the default to "1" but if i left the automatic boot it will boot the previous kernel... am I crazy or missing something here?Here is my /boot/grub/grub.conf file:
Code:
#boot=/dev/sda
default=1
[code].....
I installed a fresh copy of Fedora 13 in Windows Virtual PC (I am aware Virtualbox would probably be more suitable), and everything started fine. After updating to the new 2.6.34 kernel it will no longer start, however, 2.6.33 still works.
View 7 Replies View RelatedI am new to Fedora. I know my top probably already been posted somewhere but I just could not find it. I just installed Fedora 11. But my root password does not work (I guess was my fault to type wrong in the first place or some type of short term memory lost). I looked at the root password recovery procedure which involves select single user at GRUB page when booting. But for some reasons, Fedora 11 does not boot into GRUB. I tried Alt+CTRL+F1, F1 or Shift, none of those gives me Grub screen.
View 5 Replies View RelatedUPDATE: This is a bug: [URL] Evidently the problem is with plymouth because a workaround is to add "rd_NO_PLYMOUTH" to the kernel boot options. I don't get a prompt for my disk encyrption pass phrase---just a flashing cursor---but that's a small price to pay for being able to run fsck when the root filesystem wasn't umounted properly.
I have fully updated f13 (as of today) on a laptop with all ext2 file systems (It has nothing but flash memory.) If it's shut down without unmounting all file systems, it drops to a shell and asks for the root password to run fsck when it's rebooted. Every key press is treated as though it were <enter>, with a response to the effect that the password is incorrect.
I installed kernel 2.6.32.9-67 via a yum update this morning. When I rebooted, the machine appeared to freeze with a single blinking underscore cursor. I used a live CD to edit grub.conf and reboot into the old kernel, which started normally. Later, I tried booting into the new kernel via grub again. After about two minutes, the blinking cursor is replaced by the normal boot screens and the machine works fine. This is on a seven year old PC with AMD Althon XP 2000+, 768MB RAM, VIA KT400 chipset and the NVIDIA 173xx driver from RPM Fusion.
View 6 Replies View RelatedHere's the deal: I've done a fresh F12 install on my T61. Told the installer to Encrypt the Hard Disk. The installation went fine. The kernel was 2.6.31.5. I ran a yum update, which added another kernel - 2.6.32.11, but I can't boot from that one. The newer kernel throws a an "Uncompression error -system halted" immediately.
View 3 Replies View RelatedI upgraded, using package manager, to the latest kernel (2.6.35.10-72); I upgraded also kmod-nvidia and kmod-wl to the latest version, and the upgrade worked.After restarting the PC, though, it wouldn't boot Fedora: it stops at:"setting hostname for <my laptop's name>:[OK]"then it simply hangs there. It doesn't move, it doesn't boot, it doesn't ask for a login and it doesn't let me use command line.I can, however, boot and run Fedora fine if I select the previous kernel from the GRUB menu.Anybody can give me a hint to find the cause of the problem?
View 2 Replies View RelatedYesterday the updater installed a new kernel, Fedora (2.6.35.11-83.fc14.i686). This kernel will not boot into a GUI. This is almost certainly an nvidia problem. This kernel, Fedora (2.6.35.10-74.fc14.i686) works fine using the rpm-fusion supplied nvidia drivers. How do I get the new kernel to boot?
View 6 Replies View RelatedI have installed Fedora 12 on my HP laptop which has got a NVIDIA graphics card. I have got latest F12 kernel 2.6.32 as well as default kernel 2.6.31.I have installed Nvidia Proprietary Drivers and modified grub.conf file for 2.6.32 kernel saying blacklist nouvaue so that it can load NVIDIA drivers ...After that I am able to successfully boot into 2.6.32 kernel with Nvidia Proprietary Drivers.Everything seems to be fine .. But suddenly today when I tried to boot into F12 2.6.32 kernel I got the following error
Code:
No Root Device Found
Boot Failed, Sleeping Forever
[code]...
My Fedora 12 System was failed when booting.The message like that : mount: wrong fs type, bad option, bad superblock on /dev/mapper/my_vol missing codepage or helper program, or other error. In some case, useful info is found in syslog - try dmesg | tail or so Can't mount at root filesystem. [drm: drm_mode_rmfb ] *ERROR* tried to remove a fb that we didn't own. Boot has failed, sleep forever. I guess something wrong with my hard disk, so the bootloader can't recognize the filesystem type.
View 2 Replies View RelatedHow do I get modules in the Kernel to load automatically at boottime? I''m specifically trying to get i810fb to load during the boot process. In Ubuntu, I just had to edit a file and update my initramfs. How do I do this in Fedora?
View 5 Replies View RelatedI 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?