I ran an upgrade to 11.04. It boots fine into KDE, then panics (flashing Caps lock) about a minute later. The Live CD runs fine. Here's the part of my syslog that looks related:
[Code]...
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.
View 9 Replies View RelatedI learned yesterday that doing a massive upgrade on my system while moving was a BAAAD idea.The upgrade process was going along just fine, it was all downloaded and was actually installing that last time I saw it. I unplugged my laptop to move a bookcase out, and completely forgot to plug it back in. After I got back from moving a load, I found my computer was off. I tried to boot up, and I got an error that kind of freaked me out. It reads as follows:
Code:kernel panic not syncing vfs unable to mount root fs on unknown-block(0,0)I'm able to get to grub just fine, and my windows partition loads up just fine, but any of the linux kernels fail similarly when I attempt to load them.I'm sure that I can fix this, I just have no idea how. Probably has something to do with a live cd.
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.
Remember try to "sudo dpkg --config -a"
I got a notification that there was an upgrade available today in ubuntu 9.10 64, after the update i restarted my system and while booting i encountered this error message:
Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block (8,17)
does this have something to do with the OS looking at the wrong hd?
theres no command prompt to actually do anything and i tried booting in safe mode and had the same problem. Let me know what i can do!
I recently upgraded from FC7 to FC10 (Also, the Kernel from 2.6.22.9 to 2.6.27.19).I did the upgrade through Yum (First installed the fc10 rpms, then did yum upgrade).Now the new Kernel won't boot.These are the options in GRUB for the new Kernel
Code:
root(hd0,1)
kernel /boot/vmlinuz-2.6.27.19-170.2.35.fc10.x86_64 ro root=LABEL=/ rhgb debug
[code]....
Today I upgraded one of my computers with the following command
% yum upgrade
Before the upgrade the computer was running CentOS 5.3 with the versionlock plugin and kernel 2.6.18-128. The update went smoothly (no dependency problems).
If I try to reboot with the new kernel (2.6.18-194), I get the following:
Found volume group VolGroup00 using metadata type lvm2
2 logical groups in VolGroup00 now active
mount: error mounting /dev/root on /sysroot as ex3t: No such device
setuproot: moving /dev failed: No such file or directory
[Code].....
If I reboot with the previous kernel (2.6.18-128), everything is fine.
Yesterday i was prompted by my update manager to update some packages. I really don't remember which but i updated.
After reboot the box now kernel panics. I don't believe i get a ubuntu splash screen, and at this point i can't figure out how to get to my grub, in case a kernel was upgraded and it's possible to boot to different kernel.
i noticed some words like 'mantis', 'oops' and 'dvb_core' was a part of the text i get on the screen.
Can this be because of a dvb* upgrade that breaks something important ?
If needed, i should be able to boot via liveCD, or i could take a picture of the errors.
I have a system that was upgraded from Debian 7 to 8. Unfortunately it is not able to boot from the new kernel 3.16. Only the old 3.2 kernel is able to boot. I could transfer a backup, install it in Virtualbox, redo the upgrade and I can reproduce the error..The last error before "panic" is this line
Code: Select all 59.073579] Freeing unused kernel memory: 216K (ffff8800017ca000 - ffff880001800000)
Loading, please wait...
[ 59.226154] systemd-udevd[53]: starting version 215
[ 59.326564] random: systemd-udevd urandom read with 4 bits of entropy available
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... /init: .: line 210: can't open '/scripts/init-premount/ORDER'
[ 59.552148] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000200
The directory is indeed empty. I have reinstalled
Code: Select allapt-get install -reinstall initramfs-tools
and rerun initramfs
Code: Select allupdate-initramfs -c -u
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.
I decided to try Kubuntu (10.4 64bit) again today, it's been a few years since I last tried it. The installation went well, but now I don't seem to be getting past Grub. I get a message that says: Kernel panic - not syncing:VFS:Unable to mount root fs on unknown block(0,0) I tried to use the recovery mode option in grub but that gave me the same message.
View 9 Replies View RelatedI installed mythbuntu from a live CD on an old machine with an IDE hard disk just to play with it. It worked a treat, so I bought an Acer Aspire Revo R3610 and used dd to copy the old HD contents to the new one, and then gparted to resize the ext4 partition.
On boot I got - Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
I checked every grub2 command and it all looked fine. I then tried booting the original kernel that the live CD installed (2.6.31-14) and it booted! I tried 2/6/31-17 again, and got the panic.
After much googling, I found a suggestion to do - sudo update-initramfs -k all -c -v and this worked.
Is this expected behaviour? One of the delights of Linux is that installs move smoothly between machines, but this one didn't. Was this due to the old machine using IDE and the new one AHCI SATA? How do I get an initramfs that's flexible and will boot smoothly on any given hardware?
When I load the live CD into my computer, the DVD drive spins very fast and then drops down to command lines with a kernel Panic. I have tried with the Final Release and with the Release Candidate. Because of this I cant even load up to the live CD enviroment.
It also mentions the name of my mother board in the code, the motherboard is a gigabyte G41M-ES2L and is brand new.
Could someone give some advice or help? Currently I dont have ubuntu installed on this computer as I went for a fresh install with vista.
In my internal disk i had installed 10.04 and 10.10. 2 days ago after a restart my system did not boot and i got the message: kernel panic:not syncing VFS unable to mount root fs on unknown block(0,0).
For 2 days i tried to solve the problem without success and today i installed 10.04 in the entire internal disk but the problem(message above mentioned) remains.
the result of the sudo fdisk -l command is this
Quote:
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
[Code]....
sdb is my external hard drive in whick i also had 10.04 installed but never used it.
It's my first time i switched to linux (fedora13) and i wanted to check out ubuntu10. Started installation but somehow (stupid!) selected not the right harddrive to install new system from an iso dvd. Well installation was not successfull, because not the right drive was selected.I came back to fedora but my "storage" harddrive that i had all my collected data and projects is lost. Basically it's like new formated and some files from the ubuntu 10 are on it. None of my files. Is there any way to recover it back? I don't even have a clue how do you install software to fedora13?(I'm a newbee that was sick and tired using and upgrading windows - so now mac OZ and linux)
View 7 Replies View RelatedThe Fedora 11 Live CD was tested on a Dell and it is good. On the HP Pavilion a705w, with an Intel Celeron 2.93HHz w 760MB RAM, the install fails with kernel panic. The cd was burned on the HP.
A colleague suggested that the HP may not be compatible with the kernel. Are there startup settings that I might try to diagnose the panic issue? Perhaps there is a verbose boot up process that pauses so one can take notes?
i m trying to install Centos 5.5 on a x86_64 machine i use kickstat and cobbler but during the %pre script the installation failed with the following message
kernel panic ; not syncing nmi watchdog does someone what can be the cause of that?
Here is the beginning of my kickstart file with the pre part
url --url=http://cobbler.int-evry.fr/cblr/links/Centos-5.5-x86_64
# If any cobbler repo definitions were referenced in the kickstart profile, include them here.
repo --name=el5-x86_64-rpmfusionnonfree --baseurl=http://cobbler.int-evry.fr
[Code]....
tried preupgrade to F12 got uncompression error kernel panic-not syncing VFS unable to mount root fs on unknown block(0,0). H.
View 1 Replies View RelatedI've been using Linux for a few years, but this is my first time using Fedora. I installed it on an old computer last night and rebooted, and everything seemed good. I let it start to install updates, but after they were about half done I stopped it, turned the computer off, and went to bed. I know that was stupid of me, and I'm afraid it screwed something up because now when I boot I get the error "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(0,0)".
When I looked up the error on Google it seems a lot of people get this after installing a kernel incorrectly, so could stopping the update in the middle perhaps screwed with my kernel? Could I simply chroot into the installation from the live CD and run 'yum install kernel26'?
I tried installing hardy heron on my hp pavilion entertainment laptop It starts booting when I get this message, "kernel panic--not syncing--attempted to kill init!" My computer freezes. I have to pull the pull the plug and drop out the battery.
View 1 Replies View RelatedI tried to upgrade Empathy from 2.28 to 2.30 via Synaptic but the upgrade always failed as there were some errors to do with the dependencies (libglib2.0* and others). The dependency issues were odd as it told me that Empathy wanted to install files that were older than the existing ones. So I decided to uninstall Empathy and all its dependencies, and re-install the whole (updated) package and it's dependencies from scratch via Synaptic. After the install, Ubuntu told me that there were broken packages and Update Manager kept on popping up asking me to run a partial upgrade to fix these broken packages. Well, the partial upgrade also failed (due to the same dependency issues , I suspect) so I decided that I'll run a full system update (as Update Manager had being bugging me prior to my failed Empathy upgrade). 486 Mb later, Ubuntu no longer wants to boot - it freezes on the splash screen.
When I start it in recovery mode, it spews out the various processes being loaded. Trying to run earlier kernels (2.6.31-19 / 17 / 14) from GRUB, in both normal mode and recovery mode does not seem to help.I am running Ubuntu 9.10, kernel 2.6.31-20-generic.
a) Is the problem to do with the kernel - did the update try to update the kernel as I note that there is a new stable release (2.6.33-2)? However, GRUB still indicates that the kernel is 2.6.31-20.
b) Would updating the kernel to 2.6.33-2 help? If so, how do I do this?
c) Is the problem, as I suspect, to do with the libglib* files? If so, how do I fix it?
I am trying to install Fedora 11 from the full DVD iso on a system using an Intel D945GNT motherboard with a dual-core 3.2GHz Pentium D installed. The installation hangs quite quickly and produces the error "Kernel panic - not syncing"... The previous line is something along the lines of "EIP: [something] intel_i915_configure() [something else]". I have tried many different kernel boot options, such as acpi=off, nolapic, nommconf, and the like, but to no avail. It seems as though this has something to do with a memory mapping conflict due to the allocation of video memory for the on-board graphics chip, but I'm not at all certain about that.
View 3 Replies View RelatedI have a system here that tends to have kernel panics during an linux installation, though I was able to perform a vista installation on the same hardware. Now I would like to ask what your suggestion for the cause of that problem is. Here a screenshot: [URL]
I suspect the hd to cause it:
-it is now over 7 years old
-smartctl displays over 16k read error and 0.5mio seek errors
(or are such high numbers normalfor that old disks?)
-the panic contains the string bad_area in the trace
But it might also be a RAM error, since the trace contains sth about page_fault and vista installs on the very same hdd and does not report any error messages (concerning the hardware, and I heard win doesn't complain about a bad RAM).
Kernel Panic.
I am using
"HP Pavilion dvb 111x"
"AMD Turion X2"
"ATI RADEON Graphic Card"
And "RHEL5"
I am not register user of Redhat. I am trying to switch kernel form linux-2.6.18.X To linux-2.6.27.53. I had download source of kernel and install it as per README file. During installation everything was fair but as I am trying to boot from my new kernel it shows me "Kernel Panic" error. It Displays
" ide_generic :I/O resorce 0x1F0-0x1F7 not free.
ide_generic :I/O resorce 0x170-0x177 not free.
Redhat nash version 5.1.19.6 starting.
mount : Could not find filesystem. '/dev/root'
setuproot : mounting /dev failed : no such file or directory
setuproot : mounting /proc failed : no such file or directory
setuproot : mounting /sys failed : no such file or directory
switchroot : mount failed : no such file or directory
Kernel Panic not Synching:
attempt to kill init! "
Problems arose when I updated today, after not booting(updating) for a couple of days. Message originally said "Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(8, 1)"
I get the options to boot too:
2.6.31-21-generic
2.6.31-21-generic(recovery mode)
2.6.31-20-generic
2.6.31-20-generic(recovery mode)
[Code].....
PS - I really don't want to sound like a jerk
I have a new acer machine which runs fine on 10.10 mythbuntu desktop livecd. Install seemed fine.
Then I ran an update and on reboot I get a kernel panic error. Research on this reveals it as a very deep subject which can consume many hours, so I opted to reinstall.
This time with ubuntu 10.10. I've tried different CDs, liveusb. Same errors.
So, the question is this - where do I concentrate my efforts - somewhere ubuntu doesn't like this machine, or grub. Does a reinstall overwrite the grub install too? Or do I have a bogus grub install I need to purge before I will get anywhere.
I ran into a strange issue after doing a preupgrade from Fedora 10 to Fedora 12: Preupgrade worked as described, I upgraded successfully to Fedora 12 and also worked 2 days without any (major) issue. Then I had some issues with firefox (malloc errors, couldn't start) so I thought I'll do it the "Windows Way" namely reboot, and then no chance to boot fedora. I was hit by a kernel panic saying "init not tainted 2.6.31.6-166.fc12.i686". I was able to boot in rescue mode using the preupgrade installer (still in the grub menu) but even chroot /mnt/sysimage gave me a "Segmentation fault".
I am not able to re-upgrade the system since the installer tells me (on vty3) "product Fedora version 12 found on VolGroup00-LogVol00 is not upgradeable". I also tried to reinstall the installed kernel as well as upstart (hint from [URL]) from the preupgrade repositories (using rpm --root /mnt/sysimage --force ...) but the kernel install failed with %post and %posttrans errors (signal 11). I also did fsck.ext3 for the lvm partition with no success. Does anyone have some additional hints how to recover? It's a 32 bit install on an Intel p4 with 2GB RAM.
i'm currently using puppy linux 431. and i want to replace it with fedora LXDE but i encounter this error upon booting using livecd.
Quote:
RAMDISK: incomplete write (XXXXX!= XXXXXX)
write error
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I am trying to install Fedora on my computer but I am getting a kernel panic at liveCD boot after boot menu. It occurs to me for F13 and F14 (all x64, F14 x86 seems to boot fine but I'm trying to host a x64 guest OS on it so I need to get the x64 version to work)
My system specs:
Dual Opteron 265
4GB RAM
Asus K8N-DL (nVidia nForce Pro 2000, BIOS 1010)
I also tried to install F14 in some other computer (which worked flawlessly) and put the HDD into the computer in question, which gave me the same kernel panic.
I have PC with motherbord P5KPL-AM (latest ver. BIOS), and i want installation CentOS 5.2.But can't screen attaching....
View 5 Replies View Related