General :: Kernel Panic On Boot - Authentication Process Failed
Feb 22, 2011
I got home today to find that my KDE login screen would not let me log in. It said the authentication process failed or something and I needed to terminate the screen lock process manually. So I go over to another virtual terminal and try to log in. As soon as I enter my user name, a bunch of errors come up and I am unable to log in. "This can't be good" I think to myself, and reboot.
I am greeted by this error upon booting:
The error says that it says it cannot find /sbin/init. I loaded up a Ubuntu live CD and verified that /sbin/init is indeed present and all my other files still seem to be there. I tried booting into arch fallback on grub but that didn't work either. Midway through the day I SSHed my desktop from my phone and started it doing an upgrade. I was able to login.
I am trying to install linux kernel manually, for this I had compiled linux-2.6.36 with minimum drivers and features. Note that ext2, ext3, jffs file system support and sd ata_piix drivers are set as inbuilt kernel modules.
I had two hard disk for my Intel x86 box sda and sdb. I have running linux on sdb from which I can access sda. sda has one partition sda1 as ext3 fs.
I had created following directories at sda1 root, bin, boot, etc, sbin
After compiling kernel, I had copied bzImage, system map files to boot folder. then using 'grub-install' I had installed grub on sda. after installation I edited grub.conf to setup kernel image.
grub.conf
Code:
After this I booted sda by changing HDD boot priorities,And wow I got grub prompt -- linux kernel booted but as soon as it tries to mount file system it dies with error,
Code:
I accept that I dont have binaries for init and no initialization stuff in /etc, but I think problem is I am not able to give correct rootfs to kernel.
this is what i did i downloaded the latest stable kernel archive from kernel.org and extracted the archive into the download directory (i don't think that matters though) then i downloaded and installed the ncurses archive (needed for menuconfig) then i opened a terminal and navigated to the directory that was extracted from the archive and issues the floowing commands
I just installed Fedora 12. When I boot, only the following three lines are printed: pnp 00:09: can't evaluate _CRS: 12298 ACPI: Expecting a [Reference] package element, found type 0 Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I first installed Fedora using a RAID 1 setup that mirrored each partition, so I thought the problem was coming from GRUB and confusion from what to boot off of. However, I reinstalled Fedora using a simple single drive setup (left the second drive without any partition), and the same error was returned. Is this an ACPI issue with this particular motherboard/BIOS? Any ideas for how I can fix this?
I'm unable to boot the LFS-6.6 which i've built on a vmware workstation 6.5. i had no trouble in installing all the packages and have managed to run all the test suites successfully w.r.t stable LFS-6.6. while booting i get 'kernel panic' and it says unknown device /dev/sda1 and unknow block (0,0). i've only one primary partition without any swap partition. i've a label assigned to /dev/sda1 and have included it in my fstab file. device.map shows 2 entries:
One for the floppy and the other for my harddisk which is- hd0 /dev/sda. this is for the 2nd time i'm stuck at a point after perfectly installing all the stuff as mentioned in the LFS-6.6 book. i've also noticed on this website the many users have similar type of issue. it would be great if somebody could help me. note: while configuring the linux, i've inbuilt everything required for my system, including support for ramfs and other required filesystems, scsi driver etc.
My host machine is on a intel core 2 duo processor. my virtual scsi hard disk is 3 GB in size and is a ext3 fs. scsi is configured with LSI Logic which is recommended by vmware while adding an hard-disk.
My Redhat 5.3 desktop running on an AMD 64 system was not receiving the updates from rhn until a few days ago when it started checking in and downloading updates. The updates crashed generating bug reports. I tried running yum-complete-transaction command, it aborted also. I found a knowledge base article with instructions on how to rebuild the rpm database which I followed. After completing the procedure I tried to reboot. The system gets to the logon screen and then I get the message Authentication Failed and the system locks up. The commands I ran are:
rm /var/lib/rpm/__db* rpm -rebuilddb yum clean all
I am also seeing a message during boot up that the module libxml2 is missing and when I try to download the package from rhn yum cannot find the server.
I have an old server based on Tyan Thunder LE-T (s2518UGN),: embeeded VGA - ATI Rage XL two Intel Pentium III (PGA370) processors at 1133 MHz 512 MB ECC RAM embeeded Dual Intel 82559 LAN controllers 10/100Mbps embeeded Adaptec 7899W NT Ultra160 SCSI Adaptec SCSI RAID 2000S (PCI card to support for bootable RAID 5) 3x Seagate HDD ST318438LW connected in RAID 5 instaled OS was RedHat 8 rack case (2U) It worked fine but one disk from array failed.
I provided backup and decided use two mirrored SATA disks Seagate ST3500320NS HDD ES.2 500GB with PCI SATA controler Kouwell KW-5125 (SiI3124 chipset) inserted through PCI riser card (2U case). (I can't replace old SCSI disk because it isn't available any more.) I disabled SCSI controler in BIOS and removed Adaptec SCSI RAID 2000S PCI card. I inserted PCI SATA controler connected both SATA disks and configured mirroring.
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 am a Windows 7 user. I have two machines a laptop & a new bench top. Both machines run & boot Windows 7 very well. I use a very good program to clone my Hard Drive to an external USB drive. called Macrium Reflect. It is free and is a dream to use & very fast. This program creates a Linux based boot disk, which will allow you to find a backup clone file on an external drive to restore your hard drive. It works a treat on my laptop & has saved my bacon many times when I have messed things up fiddling with the registry etc.
The problem I am having is that my new desktop will not boot from the start up CD & returns the error kernel panic,not syncing cpu context corrupt. & then just tries to reboot again. I don't know what this problem relates to whether it is the computer hardware or the Linux CD or both. My laptop with the same OS does not have a problem, It is an Acer Aspire 5920G with 1.6ghz Intel dual core processor & 2gig Ram. The bench top has an Intel Dual core 3.3ghz processor, Zotac mother board & 4gig of Ram. both machines are running 32 bit OS.
I have browsed through the posts on this forum with people having the same error at boot, but as I am not using Linux & only using a boot CD I didn't think it appropriate to but into their threads. So I am hoping if some one can tell me is this a hardware issue or a Linux/New dual core CPU/ or Bios/Mother board issue. If it is a Linux issue then my Laptop surely would not boot would it? My bench top is only a week old and guaranteed, should I be sending it from Adelaide back to Sydney(purchased online from MWave) for fault inspection? or just take to a local Technician for a diagnosis. I am not having any hardware problem running Windows 7.
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:
I'm trying to upgrad from kernel 2.6.32.9 to 2.6.34.3 and I'm having problems.The boot finished with that old gem "Kernel panic - not syncing: Attempting to kill init !"I suspect that it's something to do with my PATA IDE driver because there have been kernel changes in this area.My problem is all the boot messages scroll off the top of the screen before I can read them and it's no use saying look at dmesg or /var/log/messages because the root fs isn't there - another reason why I think it's to do with the drivers.So my question is, is there some way I can slow down the boot process so that I have a chance of reading the messages ?
i used dual boot system (xp + ubuntu 10.04) and decided to replace them with jolicloud os and then it started In about 86% of jolicloud install it showed me error of hdd partition. I tried different versions of partion type, used also option to install on entire hdd - none of my tries actually worked (also with many hdd formating tries) so I was able to use only usb as live user for Jolicloud, and i burned ubuntu iso on disk - on boot up showed boot up error, i checked BIOS and everything seemed to be ok with boot order. So after many tries i took my old Gutsy Gibon 7.10 live cd. I first updated it with LTS version (8.04 Hardy Heron) and after that I updated it to 10.04 but it seemed to not finish when i saw some error in terminal and installer was exiting 13 minutes before finish then it had kernel panic - fuuuuck! After that i tried to download small versions of linux like Austrumi and puppy linux , but it showed me boot error or cd didnt even open install dialog without showing boot error.
Edit: The PC is broken and I'll buy a new one. Don' bother reading this thread.
I have Kubuntu 9.10 installed on my Acer 7520g laptop. It used to work fine.
But recently my laptop has often went into kernel panic, sometimes at boot, sometimes after hours of normal usage. Today it has not been able to boot properly from HD a single time.
When I boot it up in recovery mode, it kernel panics and displays this (normal mode displays just the graphical progress bar, no text):
Code: 00010c0f [ 9.620019] TSC f0ed3f8e6 [ 9.620019] PROCESSOR 2:60f82 TIME 1270650316 SOCKET 0 APIC 0 [ 9.620019] This is not a software problem!
[Code]....
I'm sure this is a pure software problem, because Ubuntu 7.10 LiveCD boots up normally and I got X, Gnome and everything working. So CPU must be working perfectly.
I read the logs in /var/log but there were no error messages.
I prepared a ISO from ubuntu 8.04.3 server using which kernel 2.6.24-24-server.My installer file is in initrd is iecho Preparing to install cd / mount -nt tmpfs tmpfs tmp
iecho partitioning hard disk, creating filesystem mknod /tmp/sda b 8 0 parted --script /tmp/sda mklabel msdos parted --script /tmp/sda mkpartfs primary ext2 0 -- -0 parted --script /tmp/sda set 1 boot on
iecho configuring filesystem mknod /tmp/sda1 b 8 1 tune2fs -j -i 6m -T now /tmp/sda1 iecho mounting filesystem mount -nt ext3 /tmp/sda1 /mnt
iecho mounting CD-ROM mknod /tmp/hdc b 22 0 mkdir /tmp/cdrom mount -nt iso9660 -o ro /tmp/hdc /tmp/cdrom . . . . My menu.lst file is
I decided to try Linux recently. I downloaded CentOS-5.3-i386-bin-DVD.iso. Installation was successful but the OS reports Kernel Panic while booting. At first I can see messages:
Memory for crash kernel (0x0 to 0x0) notwithin permissible range PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not usin MMCONFIG
The OS continues to boot, but then shows kernel panic.
I tried to solve this problem during several days. I've installed the OS at least 10 times changing conditions. I tried x86-64 version, disabled PAE in BIOS, performed manual partitioning without LVM. The result is the same.
My PC has Intel Core 2 Duo E8400 CPU (no overclocking), 4GB RAM (DDR2-800), ATI 3470 GPU. Windows is working smoothly on it, I can encode video during several hours without problem. All fans are working, the system is not overheated. MemTest86 showed no errors.
I've installed CentOS on my laptop (Core 2 T5600 CPU, 2GB RAM, Intel G945 Video), it works nice, i like it very much.
For testing I've installed OpenSUSE 11.1 on the PC, everything is ok, I'm writing this message from it.
I 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?
We have not actually purchased support on a 2nd seat yet, so I can't go to them for this yet, and purchasing the seat may be silly if the machine can't run the OS.
I have tried several times to install RHEL 6 workstation onto a server machine. It has a dual drive RAID filesystem, whose configuration I had nothing to do with. The install procedes nicely but Displays a mdam error 127 before shutting down for the first real boot.
When booting a weird progress bar with at least 3 colors proceding at different rates displays for about 5 seconds followed by a very verbose kernel panic error which mentions tainted swap and scheduling while atomic. I suspect the error that caused the mess runs off screen too quickly to record.
Does anybody have a clue what might be happening? Even if I install minimal this happens so it appears to be a very low level hardware problem rather than a corrupt package.
I should mention that the machine runs on ubuntu 10.10 just fine, but my Lab PI wants to run it as a redhat system.
I have recompiled a few kernels, but all on 32bit systems so not sure if that has anything to do with it.
Running Arch Linux 64bit, most recent version.
Kernel Output:
Code:
My first thoughts was that it might be my grub bootloader configuration, so had a big play around with that but it didn't fix it. Also made sure support was built for filesystems. However almost all that Fstab mounts are ext3 anyway, and certainly the root and /boot are. Now thinking it may be a memory error so will run a check when I shutdown.
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel. Red Hat nash version 4.2.1.13 starting sda: assuming drive cache: write through sda: assuming drive cache: write through mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd-dev failed: 2 Kernel panic - no syncing: Attempted to kill init!
1. Does minimum installation not drop on a kernel or initrd with ext3 support? I can't imagine that's true, but have to ask.
2. The USB stick is single partition ext3. Maybe there is some limitation specifically related to USB stick booting that requires boot to be FAT16 or FAT32? Except the CentOS 5.5 installer refuses to let me install on either FAT.
3. How can I do the equivalent of lsmod on a linux installation that will not boot? i.e. I have CentOS x86_64 running in VirtualBox, I can plug the USB stick in there, so how do I get information on the USB stick's kernel and initrd if I can't boot from it?
4. Is it possible to rebuild the i386 based initrd on this USB stick, when the computer is not booted from that stick, with a system that's x86_64 based?
System Info: Dell Latitude i686 Laptop which has run CentOS 5.5 and Fedora 12,13,14 in the past, and boots from Fedora 14 Live CD transferred to a USB stick. So I know USB booting is possible on this machine, and this stick.
The process of creating the stick:
CentOS 5.5 i386 on a USB stick. Old Dell i686 laptop which has previously run CentOS 5.5 installed from DVD, and has successfully booted from this same USB stick holding transferred Fedora 12,13,14 Live CDs. CentOS 5.5 was installed onto the USB drive directly by the CentOS 5.5 DVD installer (running virtualized in VirtualBox 4.02 on Mac OS X 10.6.5.). No errors or complaints during installation.
For whatever reason, the installer did not do some things correctly. First Grub wasn't working correctly, I got that sorted out and have the Grub+CentOS splash screen, it finds vmlinuz and the initrd, and then I get a kernel panic.
Ext3 was built into the kernel and that's why I'm getting this message. I do not know how the installer would have dropped a kernel or initrd during instalation that that don't contain such a basic thing that obviously comes in linux kernel 2.6.18-89 EL.
I am running an Hp Pavillion dv6000 with the Broadcom card that never seems to work for Linux. I recently talked with my friend who said he found a way to get it work.following his instructions I opened Synaptic and checked the package bmcwl-kernel-source to be installed.I went through the process of it all and it said it had install successfully. I restarted the computer and when I tried to enter my operating system I got this error "Kernel panic - not syncing : VFS : Unable to mount root fs on unknown - block(8,1)" I have previous versions of Linux on my computer so I can still get in to those if need be but I don't know how to undo what I did or why it isn't working for that matter. Does anyone have any ideas as to why I am getting this error and how I can fix it?
I have a server running Red Hat Enterprise Linux ES (2.6.9.55.ELsmp). When it starts up I get the following error: Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.10 starting WARNING: can't access (null) exec of init ((null)) failed!!!: 14 unmount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init!
After that I got no response from the OS. I have the installation CD, so I tried to start the rescue mode, while going through the steps I received an error stating that mounting to /mnt/sysimage failed and that if I want to I can access a shell. I really don't know what to do from here
when i was in office, something funny happened. my laptop power chord seemed to be disconnected and was running on battery power. i was away from desk and by the time i came back, laptop had gone to sleep may b due to battery getting drained.i packed up and came home, plugged in and booted but ubuntu seemed to give lots of erros and didnt boot. i went to my win partition, burnt the iso i had earlier downloaded and kept on win partition for safety. i booted off the cd and issued sudo fsck command from terminal. fsck did its job and gave a clean chit for my dev/sda5 (where ubuntu is).
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.
I installed a fresh copy of Slackware 13.1 (stable) on one of my media servers and I am experiencing something strange.... When I power up the machine, I see the kernel booting, no errors, until it gets to the point where it says:
And then randomly freeze there.... Well the machine is not totally frozen because the cursor still blinks. But it will never continue... Like I said, this happens on a random basis... After a reset, it might go through or simply stall at the same spot.
I remember after installing Slack 13.1, I rebooted the machine but forgot to remove the DVD from the player, so the install routine started up, and froze at the same point when it was loading the kernel for the setup programs...
My mobo is a MSI k9N platinum.
I never had this problem before.... (well I never used 13.1 before). Since I got this machine, I used slack 12.2 and slack 13-current with success.
This problem makes the machine extremely unreliable because I intent to use it as a backup and media server, so chances I will WOL the machine and use it remotely... if that happens.
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 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.
It 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.
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 a 8.04 x64 server installation that is receiving a kernel panic on boot no matter which kernel I choose even recovery mode.
[ 27.738620] raid1: raid set md0 active with 1 out of 2 mirrors Done. Begin: Running /scripts/local-premount ... kinit: name_to_dev_t(/dev/disk/by-uuid/c224854e-37bd-491a-b895-48e8bf07fe00) = md1(9,1) kinit: trying to resume from /dev/disk/bby-uuid/c224854e-37bd-491a-b895-48e8bf07fe00 [ 31.665733] Attempting maual resume kinit: No resume image, doing normal boot... Done. [ 31.717461] kjournald starting. Commit interval 5 seconds [ 31.717471] EXT3-fs: mounted filesystem with ordered data mode. Begin: Running /scripts/local-bottom ... Done. Done. Begin: Running /scripts/init-bottom ... Done. init: Error parsing configuration: No such file or directory [ 32.064009] Kernel panic - not syncing: Attempted to kill init!
I have built a new server, now I am trying to restore my db from mysql. I have a backup that is out dated, I was hoping there was a way to copy the files over and have them work on the new installation. I can boot the server with the installation cd using recovery mode, I can get to the hdd and mount a smbfs share from the new server. I have tried to cp the files retaining the permissions and get a permission denied error, but if I copy without retaining the perms they copy just fine and do not work.
I have setup the new server with very close to the same version of all software. I have built a new instance of my service using all of the same users and passwords. I then backed up the new db and moved it over and attempted to copy the old db over. I did not copy it straight to the mysql folder as I did not share that folder out. Any other ideas to get this db recovered? What about getting my old server to run again just long enough to get a mysql dump?
