Ubuntu :: Kernel Panic Not Syncing Attempted To Kill The Idle Task Wubi Ubuntu Install
Dec 13, 2010
-Linux / Ubuntu.
-I am running Windows Vista
I just downloaded Wubi - To install Ubuntu on my computer. (Whether it's called Dual boot or running Ubuntu inside of Windows Vista I do not know.) Everything went fine, got a very easy little screen to ask what partition I wanted to install it on and how much size, etcetera, the download went fine, blablabla.
Problem: It asks me to reboot (This is the first reboot I got.), I say yes, it reboots, I get the booting screen where I get to pick between Windows and Ubuntu, I pick Ubuntu, and it gives me this 'error'.
Among other things it reads:
After this nothing happens - I waited about 25 minutes.
I manually turned off my computer - started it up again - once again chose Ubuntu and the same problem occured.
1. I looked around the Ubuntu folder inside my C a little, it shows the iso file as Ubuntu-10.04.1-desktop-amd64
2. Some other forum advised people with this problem to check their RAM, so I unplugged both, cleaned and switched them. (I have 2 GB ram total.) This didn't work. Same problem still occurs.
I used ubuntu in my ARM board. but now i rebooted it says that "kernel panic - not syncing: Attempted to kill init!" i have to reinstall my OS or any other way to get retify?
Our email server and fax server configured in a Linux server.2day mornin onwards i am getting the error.kernal panic -not syncing : attempted to kill init.
Bootin "powerserver"(Centos-4 i386)-up( 2.6.9-11 EL) root (hd0,0) Filesystem type is ext2fs,partition type 0*fd
How to resolve "kernel panic not syncing attempted to kill init" problem in Linux?? And why this error occurs? In my case, this error occurs when i boot my computer and after this error my computer goes on rebooting..
am trying to interface ade7758(adc) to at91sam9261...i have written a sample code which registers an spi driver and sends an address to ade7758 and receives a data...every thing is fine.My device is registered but kernel is giving a crash message....below is the message....
exec of init (/sbin/init) failed!!! : 2 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! My server is at remote end which I access through Public IP.
Today I was upgrading my netbook with Ubuntu 10.10 on it to 11.04 via the Update Manager. I got a few errors and the Update Manager seemed like it wasn't continuing, so decided to exit it. It didn't respond so after a while I decided to restart the netbook. However the on/off/standby/restart, etc. button in the top right wasn't responding either, so I decided to force a shutdown with the power button on my netbook. Now Ubuntu doesn't start up, and gives me an error along the lines of:
Kernel panic - not syncing: Attempted to kill init! Pid: 1, comm: init Not tainted 2.6.35-28-generic #50-Ubuntu Now could I in some way repair my Ubuntu installation while still keeping the files I already have on my computer? Maybe via booting from a flash drive or something...?
I got the following error after compiling kernel version 2.6.38.2 from sources with this Howto:[URL].. Creating root device.
Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults
I boot from CD (Tried both debian-506-i386 and the Netinstall) I also tried the flags acpi=off noapic nolapic And when it starts booting the install, it appears: "Kernel panic- not syncing: attempted to kill init"
I was unable to access the server and had to reboot it. When the server was booting after the Grub, it errored out withKernal Panic -not syncing Attempted to Kill init!!exec of init (/sbin/init/) failed No such directoryI reboot into the recuse mode from the CD and when looking for the installed OS.I got an error like thisFound OS but with errors.Mounting part or all of your system at /mnt/sysimage.. something of the sort. I've run fsk -y on the /boot and root drives and rebooted but still the same issues.Here is my grub.conf:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file
I recently installed new hard drive and cloned old hard drive software onto it. The bootloader installs either linux or other operating system. Ever since the cloning, boot hangs. Words in the thread title are the last to appear before everything grinds to a halt. Just before the kernal panic message appears, "Initrd finished" is last line. Will have to try booting again to find more info before this.
I just imaged my RHEL 4 system that was running on a Dell Poweredge 2950 server using Acronis software and I restored the image to a VmWare virtual machine.
Dell Poweredge 2950 - RAID 5 VmWare - using ESX 4.0 OS - Red Hat Enterprise Linux 4 ES Update 5 x64 kernel - 2.6.9-55.0.9.ELsmp
I'm getting the following when I try to boot on the new virtual machine. I'm thinking it has to do with the fact that it's new hardware and it's having trouble either finding the right drivers or pointing to the correct place.
"No Volume Groups found Volume Group "Volgroup00" not found ERROR: /bin/lvm exited abnormally! (pid505) mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!" I was able to boot into Linux rescue mode using the boot CD. Then I typed: #chroot /mnt/sysimage
Here's all the info from the commands I typed: #ldd /bin/bash libtermcap.so.2 => /lib64/libtermcap.so.2 libdl.so.2 => /lib64/libdl.so.2 libc.so.6 => /lib64/tls/libc.so.6 /lib64/ld-linux-x86-64.so.2 #uname -a Linux localhost.localdomain 2.6.9-89.EL x86_64 #df -h ....
I've tried the following: 1. mkinitrd -v -f /boot/initrd-2.6.9-55.0.9.EL.img 2.6.9-55.0.9.EL 2. modified the device.map to point to /dev/sda3 3. changed the SCSI controller in Vmware to use BusLogic instead of LSI Logic. (didn't work because I'm running 64 bit.. gave me an error message) 4. grub-install --recheck /dev/sda 5. tried booting to differerent OS versions (i.e. 2.6.9-55.0.6, etc.). I tried all of the versions listed in the boot menu. None of these worked.
I Downloaded the 6 CD's of CentOS installation , and I start install them on my machine : Processor : Intel Pentium 4 -2.08 Ghz Ram: 256 MB cash :512kb HDD: 80GB (it is for home server purposes)
After the fourth disc the system ask to reboot the system ; so I restart it ok? What I get ? No OS. Just a long text : I think the bootup run ok, then this line came out I think it reveal some thing that Pros will know it: nash received SIGSEGV Backtrace : [0x804fb35] [0x488420] [0x......... [0x........ [0x......] then Kernel panic - not syncing: Attempted to kill init!
I had FC10 working nicely but decided to move to FC12 to be able to use the latest and greatest... Turning out to be nightmare!
My HDD is partitioned into three:
(hd0, 0) 100MB : used to be original /boot for FC 10 (hd0, 1) 120GB : /home (hd0, 2) 30GB : / > First thing tried: preupgrade
Using this preupgrade setup happend and asked to reboot. However, upton reboot got locked in stage2. So this option was abondoned.
> Second thing tried: installation CDs
Using this method formatted (hd0,2) and installed FC12 on (hd0,2). However, did not change anything on (hd0,0). This still held all the upgrade information from the previous trial. Now, when I rebooted after the install there was a kernel panic with error "kernel panic not syncing vfs". Thinking it might due to the (hd0,0) partition and errors in my install, I abandoned this.
> Third thing tried: installation CDs
Using this method I formatted both (hd0,0) and (hd0,2). The install was similar to above but now (hd0,0) was also formatted and after install was empty. But upton reboot I still got the "kernel panic not syncing vfs" message. I dug through google and saw references to problems in grub.conf and lo behold there were problems with my grub.conf. I don't see the initrd line at all nor do I see the initrd*.img file in my disk. The grub.conf is:
My computer AMD phemom II 955 X4 Black Edition 3,2 Ghz Asus M4A785TD-M EVO micro atx Kingston 4Gb Ram DDR3 1333 mhz (KVR1333D3N9K2/4G) Disco Duro Western Digital 1 terabyte LG GH24 Super Multi DvD rewriter
menu.lst
fstab
fdisk /dev/sda
Orden (m para obtener ayuda):
Bios
I have Sata=AHCI
Sometimes it starts and sometimes not. the RAM is memtest OK. The test detects a firmware in the micro hole 15 to 16 mb of memory. The rest is OK.
I am getting an error when I try to boot my ubuntu 10.4 system (64 bit). Error:Kernel Panic- Not syncing: VFS: Unable to mount root fs on unknown-block(0,0).I installed Sbackup and tried to create a backup of the home, var, usr/local folders. I started the backup and it ran for about 30 minutes then I got a message from the system that indicated that I was out of hard drive space, then the system froze. I restarted the system and then I got the above mentioned error.
I get this Kernel Panic when I start my PC once in a while. After a restart or two it boots normally. I have included a screenshot taken with my camera. Anybody have any idea what this is and how I can get rid of it?
I tried using gparted on a live cd to shrink a windows partition to make room for ubuntu. Then windows failed to boot. I deleted the entire disk and tried to install ubuntu 10.10. It seemed to install fine, but now when I start up I get
[ 0.869364] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
and a bunch of other stuff that doesn't look good. I saw some other posts about this error, and people are talking about lilo. I'm not sure what to do
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.
The first server I installed installed fine. The second server, installed with the same config, went to "kernel panic not syncing no init found try passing init= option in kernel" error. I tried reinstalling but it keeps going to that error after install reboot. The storage is ISCSI connected via Intel Server Adapter, which allows it to boot from ISCSI. Not sure if that's the cause for the problem, but the first server is connected to the same ISCSI and installed just fine.
Is there a way that I can make sure ISCSI module installs during installation? Although I think it is installed since it's able to copy the files and setup /dev/sda. I just wana make sure that it installs during setup.
I 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?
this is a dual boot XP/UBUNTU 10.04. while using XP, the computer rebooted itself. the GRUB's screen appears, but neither the ubuntu nor the XP option works.
Ubuntu gives this error message:
Code: 0.797795 kernel panic-not syncing: vfs: enable to mount root fs on unknown-block (0,0)
XP hangs on a black screen... and that is it (thanks for support windows!) UBUNTU 10.04 live CD hangs when the 5 processing dots appears bellow the ubuntu logo. hangs the same way with the processing bar in UBUNTU 9.04 live CD. memory check (memtest86) is showing thousands of errors right from the start.
I've just started using Linux Ubuntu. I had a frightening error message, I don't know why. But after browsing some replies to something similar on this site, I simply opened a previous session and found that all worked fine and I hadn't even lost any of my downloads and adaptations. ś Yes I've still got my third level key and everything.
I recently decided to try out OpenSuSE after a few years of using kubuntu. However, upon lanuching the install disk I get the following kernel panic: "kernel panic-not syncing VFS:unable to mount root fs on unknown-block(3,1)". I am using the 64-bit DVD install and I have verified the md5 of both the download and the disk itself. The specs for my computer are:
I'm using openSUSE 11. I'hv tried to upgrade it to 11.1 with a x86_64 installation DVD (as I did earlier), but it failed. It showed the following message:
[Code]...
eventually same type of problem happend when I was trying with fedora 10... fedora 9 and openSUSE 11 install smoothly in my 64 bit machine (compaq SR1730IL, Intel pentium 4, 524 and 1GB DDR2 RAM)
I'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'?
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)"
