I've been trying to track this kernel panic down for the last few days on this system... I believe it might be autofs/nfs related, but I'm not 100% sure.
Here is the dump in /var/log/messages:
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:
Code:
A yum update got interrupted - I cleaned it up, reran yum update - everything appeared okay but now system won't boot
kenel panic - not syncing VFS :unable to mount root fs on unknown-block(0,0)
any hope to repair this or must I reinstall linux ?
Previously we ran a 2.6.23 Linux kernel on our systems. We have now upgraded to a 2.6.32 kernel and are in the process of testing to make sure everything works. We have a driver for a Magtek Intellistripe 65 that was previously working in the 2.6.23 kernel. Originally it didn't want to be loaded into the 2.6.32 kernel at all. I had to make some changes to the code (ie replace kill_proc and other functions that have since been removed/replaced) and now when the card is removed the system freezes. I have a feeling that it could be to do with changes to usb-core, but i'm not sure.
I looked through and diffed the kernel for changes to usb-core, but i cant see any earth shattering changes to it, so i believe it still should be working fine. I've tried my modified version on the 2.6.23 kernel, and its all working fine, so it wasn't my changes that broke it.
I have a Centos 4.8 linuxbox running in VMWare ESXi 4 and the kernel is 2.6.9-89.0.11.ELsmp. Recently, this linuxbox is quite unstable, it has kernel panic once a week... But we didn't have any configuration changes on it. And I have attached the kernel panic console screen and lsmod for the server.[URL]...
View 2 Replies View RelatedWe have a server running CentOS 5 Linux 2.6.18-128.1.16.el5xen #1 SMP Tue Jun 30 06:39:23 EDT 2009 x86_64 x86_64 x86_64 GNU Linux. We've seen at random times that the server will just reboot and nothing is logged in messages. I tried to enable kdump but was only able to get a 5.4 gig dump since our /var directory is set to 10GB. Here is the messages I see before and after the server restart. I had thought that when a kernel panics, it is supposed to halt the system and not reboot it. My /proc/sys/kernel/panic is set to 0. I can run an update but want to have some sort of idea what is causing the issue and if the update will fix anything.
May 13 20:05:22 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1071 duration=1(sec)
May 13 20:05:22 hlotmt01 xinetd[3609]: START: bpcd pid=1072 from=10.203.1.1
May 13 20:05:23 hlotmt01 xinetd[3609]: EXIT: bpcd status=0 pid=1072 duration=1(sec)
[code]....
I'm having a strange problem on some of our Debian servers. It all started about three weeks ago when we moved our virtual environment (VMWare ESX3) from a SAN to a NAS (NetApp). At first I thought it had to do with that move but since the other 9 servers are working perfectly I eliminated that idea. For over a year all 12 Debian 5 servers have been working great without mentionable failures. All servers are (where) up to date with the latest patches. About three weeks ago I started having kernel panics with the following message on three of our servers:
Code:
Code: Bad EIP value
EIP [00000000] 0x0 SS:ESP 0068:f6d7da18
Kernel panic - not syncing: Fatal exception in interrupt and other times it looks like just a dump of hexadecimal data. The only difference between those 3 servers is that they have several mounted shares connecting to the NAS using CIFS. So I was thinking that it might have to do with an update of some kind in regards to smb. I recovered an image from a month ago, before the troubles began, copied over the data and MySQL databases and configured the 'old environment with recent data' exactly the same with MySQL master-master replication, document synchronization and load balancing. This task I performed last night (no other way since it's a production environment). Up to this time neither of the two 'restored' servers had a kernel panic. The one that has not been restored is having one at random about every hour and a half. Following are the different versions between the 'at this time' working server(s) and the failing one:
Code:
FAILINGWORKING
samba-common 2:3.2.5-4lenny122:3.2.5-4lenny9
smbclient2:3.2.5-4lenny122:3.2.5-4lenny9
smbfs 2:3.2.5-4lenny122:3.2.5-4lenny9
[Code]...
I am trying to restore a golden image to a server using system imager and getting the below error after the PXE boot.The image is for Red Hat 4 AS."UDF-fs: No partition found (1)No filesystem could mount root, tried: cramfs msdos vfat iso9660 udfKernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)"Please let me know if anybody had faced this issue before and tried trouble shooting.
View 1 Replies View RelatedI 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 one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code:
# Linux bootable partition config begins
image = /other/spare4/boot/vmlinuz
[code]....
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
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
View 9 Replies View RelatedI am working on RHEL4 AS. I have created a user and tried to access, but the system is showing the error messsage as "system administrator has disabled access to the system temporarily". I could login through root. Before this I have changed the root/.gnome2/panel2.d folder permissions for group and others as read only to prevent other users to delete or add icons on the panel bar.
View 3 Replies View RelatedIm am building a Linux distro. It will be very tiny and fast.
I only have a minimal linuxkernel (bzImage) who is 1,2 mb big. And then I have Busybox who is 174,6 kb big.
The commands in busybox is: cd, ls, mkdir, rmdir, wget, httpd, clear, rm, poweroff, halt, reboot, fdisk, mount, umount, free, and cp.
When I compiled the kernel i use initramfs/initrd function and point it to a folder where initrd/initramfs source is.
The kernel works OK with others initramfs/initrd files. But not with my own.
Quote:
Here is how the end of the kernelcomplie look like.
Quote:
Here is my init file who is the initrd/initramfs source.
Quote:
The initramfs folder contains "bin" (folder) and "init" a file. No more.
The problem is that the kernel cannot find/read init file.
I was installed xming application on windows XP & Windows 7to access Linux server's GUI session and i was able to access it using root account but when ever iam trying to access GUI using normal account it is giving some error.I am testing this since it is a freeware.
View 7 Replies View RelatedWe have done an installation on a blade server (HP) for RHEL4.5.
The server have an HP smart array 2200 controller and during installation it can see the controller and disks just fine.
The installation completes up to the point where the system needs to reboot , however after the reboot it does not start up again and get stuck at the message: "Trying to boot from drive c:"
We used the rescue option to mount the installation and cant find nythign wrong, even with the grub setup (except that it points to hd96 as its primary disk). we tried changing this to hd0 as well but still no luck.
After about 3 installations we are still not having any luck.
Recently i've been playing with few variations of linux distros since my Windows XP got infected with something that makes anything flash-player related crash or restart computer even(im saying this because it might be related), reinstall didn't help fix it so i decided to better switch back to Linux world and tried some newest distros. Everything was nice untill..recently some distros after installation gave me kernel-panic or caps lock+scroll lock lights blinking..trouble is Fedora 14 just gave me same stuff after i went maybe 5mins away from keyboard with web browser open then came back to notice..if at first i thought it was wrongly made distribution now i'm bit scared that my PC is dying..i did basic search in google and people say it may be related to hardware beeing too old or drivers but when i use it then i don't encounter this - just when afk. I have almost none experience in Fedora so was just wondering if someone could point me to right direction
View 6 Replies View RelatedI have a CR-48 running Ubuntu 11.04. I've had some continual issues with it, along with other Linux distros I tried. There are times my laptop freezes completely during mid use. If I power off and back on, 70% of the time it doesn't detect the hard drive upon next boot. If I go into BIOS, no SSD detected. If I pull the battery, hit the power button, put battery back in, it'll run fine for a while.
I'm up in the air if it's a hard drive issue or motherboard issue. Once I got this kernel panic I sat here for a half hour on another system typing it up. I hope somebody can look at it and make sense of it and tell me what essentially is happening.
running Kernel 2.6.9.89 just updated from RHN using up2date...
This server runs for a random 5-30 mins then throws the kernel panic.
I am developing a some application which running on rhel4 os. And its functions will handle via the web application. So we have provided an option to login (via vnc)to the server on web application when we need. so how we can enable vnc for a session (like 30 minit)? I'm using default vnc installation while installing rhel 4 nothing more installed by downloading. When I click session button on web page, I execute this command from my code
"service vncserver start"
then I can access server via vnc but when I click on disable button on web page, I execute this command from my code
"service vncserver stop"
but still I can login to server via vnc
The 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?
After installing the latest updates (dont know which ones) yesterday, I get a kernel panic (LED lights flashing at the keyboard and black screen) when starting X (the login manager). I am running on 64 bit with the proprietary ATI catalyst driver. How can I start in text only mode?
View 5 Replies View RelatedEdit: 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 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 am getting Kernel panic. I was getting is very frequently before, then I re-installed and it starts off fine then after a while it starts happening again.The problem is I have no idea what is causing it. The screen is completely frozen and won't respond to anything. The Alt sysreq combinations don't work, and I have to power off with the button.
View 2 Replies View RelatedI have a Toshiba Satellite laptop, dual-boot with Win7 and Ubuntu 10.10. Everything works as it should in Ubuntu, except when I resume from standby the computer goes into a "kernel panic," the screen freezes and caps lock light blinks.
I travel with my laptop and use standby all the time being a student, so I've been forced to use Windows 7 because it's far more reliable (isn't that funny >_<) when I resume from standby..
After literally searching for DAYS, no solutions have worked for me, and apparently this is a pretty big issue. I would love to get Ubuntu running full-time on my laptop. Also, my display drivers aren't officially supported by Ubuntu, but I'm not sure if that has anything to do with it.
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.
View 1 Replies View RelatedI 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?
View 6 Replies View Related
