Update manager downloaded and installed latest kernel (Ubuntu, Linux 2.6.31 -16 -generic). When I tried to restart I get the message { 1.661235}Kernel panic - not syncing: VFS: unable to mount root fs on unknown - block(8,38). Everything works fine on previous update.
View 1 RepliesI 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.
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:
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 RelatedYesterday 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 updated my slackware 13 to current with the commands as writes in man slackpkg:
slackpkg update
slackpkg install-new
slackpkg upgrade-all
but now it's print kernel panic and I can't restore it.I tryed to boot with root=/dev/sda3 parametre, but not effect. Do you have ideas?
After reading this article openSUSE News - Forum Users Benefit from openSUSE KDE Repository I added that KDE repo to yast and switched all packages.
After rebooting it says (failsafe kernel configuration says the same):
Kernel panic - not syncing: VFS:
Unable to mount root fs on unknown block (0,0)
And stops at this string: "[<c0203826>] kernel_thread_helper+0x6/0x10" and capslock light is blinking.
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.
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.
View 3 Replies View RelatedAfter update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
View 4 Replies View RelatedDell 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?
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 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 use gentoo linux and some minutes ago I thought to upgrade my kernel version. I had 2.6.36-r5 and I want to set 2.6.37-r4. After merging gentoo-sources I did this:
# cd /usr/src/linux
# make menuconfig
# make && make modules_install
# mount /boot
# cp arch/i386/boot/bzImage /boot/bzImage-2.6.37-gentoo-r4
# module-rebuild populate
# module-rebuild rebuild
At the end I changed the /boot/grub/grub.conf file. The last two commands are for reinstall modules that are not included in the kernel source. After rebooting the system this is what it printed out and stop loading.
sd 2:0:0:0: [sda] Attached SCSI disk
EXT3-fs (sda3): error: couldn't mount because of unsupported optional features (240)
List of all partitions:
0800 313474754 sda driver: sd
0801 56196 sda1
0802 2104515 sda2
0803 310407930 sda3
0810 48843636123 sdb driver: sd
0811 48843636123 sdb1
No filesystem could mount root, tried ext3 vfat msdos iso9660
Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,3)
Pid: 1, comm: swapper Not tainted 2.6.37-gentoo-r4 #1
Call trace
? printl+0xf/0x11
panic+0x50/0x146
mount_block_root+0x161/0x170
Yesterday I decided to dual-boot windows 7 and Ubuntu 11.04. I successively instaled Ubuntu the first time using a flash drive. However, I found that I had made the partition for Ubuntu way to large. Having no idea what to do, I messed around with the partition sizes. Through a series of... mistakes, I deleted the two (the main space and swap space) linux partitions. When I restarted my computer I got the "partition not found" error. So from there, I burnt another ubuntu disk, (the flash drive I used had been reformatted for use on an Xbox) I am able to boot a live version of ubuntu on my computer. However, when I go to install Ubuntu, something goes wrong. After copying all the files, it goes into kernel panic about not syncing, and freezes.
I had looked up some advice on the web, and they said that it might be a memory error. However, Ubuntu 11.04 does not have the memtest86 or whatever, (at least that I could find) So I took out the smallest RAM stick (1 gig, leaving the laptop with 2 gigs of RAM) and it still freezes.
I included the story to see if I did something wrong with any of my steps that may have permanently done something bad to it.I know it does not sound like it, but yes, I only installed Linux yesterday, therefore, still a newb.
we are facing the problem related to Kernel panic in linux . Could u send me details of kernel panic . Why the kernel panic occur and how to resolve this problen
View 2 Replies View RelatedI have a server with Debian on it that I regularly reboot after upgrades. Sometimes (on schedule) fsck will check a disk when the computer is booting. With the exception of sitting in front of the console to observe the fsck, how can I determine the difference between a problematic halt and an fsck (besides waiting out the fsck, hoping it is an fsck)?When I send the computer down to reboot, I will usually have a terminal window open pinging the computer so I know when it has come back up. My first thoughts drifted to fantasizing about hacking fsck to respond to pings with some special magic byte so you could tell via ping that a computer was fsck-ing, but I'm thinking there have got to be easier ways..
View 2 Replies View RelatedI have just tried to update my kernel from 2.6.24.5 to 2.6.39-rc3 on a Slackware 12.1 distribution. I have successfully updated the kernel before, but it was from a newer distribution and newer kernel(Slackware 13.1 and 2.6.33.4). After I updated and rebooted, I got the following error:
Code:
List of all partitions:
0300 4194302 hda driver: ide-cdrom
0800 312571224 sda driver: sd
0801 244197560 sda1 00000000-0000-0000-0000-000000000sda1
0802 68372640 sda2 00000000-0000-0000-0000-000000000sda2
No filesystem could mount root, tried: romfs
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (8,1)
Pid: 1, comm: swapper Not tainted 2.6.39-rc3-smp #1 .....
I am the new bies for redhat.i am using "Nokia 5300" on "RHEL5"as i am going to connect the phone to the sysytem.System gets hang.on the main screen it shows some alphabeats and it Gives the message "KERNEL PANIC".i had read in some thread to use "VID" and "PID" but i dont know how to use it.Is their any method so my kernel can Find my hardware.and runs smoothly. please suggest me some methods so i can use my Nokia phone as an MODEM.
View 4 Replies View RelatedKernel 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! "
I am using RHEL 5.4 in VMware. Recently i have made changes in /etc/sysconfig/selinux and made it to be in "enforcing mode". Now when I rebooted my system, It is showing the following error:
"Unable to load SELinux Policy. machine is in enforcing mode.
Kernel panic- not syncing: Attempted to kill init!"
I need to run an executable from initramfs which after executing should restart the system. How is it possible?.I tried using exec within the init of initramfs but it shows kernel panic (I guess exec after executing the binary it tries to exit and exiting with pid 1 is giving the panic).
View 2 Replies View RelatedI had an old Dell Precision 470 with 2 hard drives, a 250GB boot drive with Red Hat installed, and a 500GB hard drive with data on it. Both of these are SATA. The computer died and I have replaced it with a Dell T3500. I was hoping just to move the hard drives into this computer and let generic drivers take over until I make the necessary changes. Unfortunately, I get the following kernel panic message after POST:
VFS: Cannot open root device "Volume00/root" or 00:00 append a correct "root= " boot option Right now the arguments to boot from the hard drive are:
ro root=/dev/Volume00/root hdc=ide-scsi hdd=ide-scsi
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 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?
View 4 Replies View RelatedOur 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
[code]....
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..
View 1 Replies View RelatedI 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?
View 1 Replies View Relatedmegaraid controller and Dell2850, all that I can see on thi screenshot:
[URL]
All drives successfuly passed verifing from LSI controllers (Ctrl+A at startup), also I tried to boot from rescue llive cd and mount all the morrored drives and check it by fsck - ok.