General :: Getting Info On Kernel On Another Disk - Kernel Panic Error 6 Ext3
Feb 13, 2011
Dell laptop booting from a USB stick with a CentOS 5.5 minimum installation.
Uncompressing Linux...OK, booting the kernel.
Red Hat nash version 184.108.40.206 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?
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 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.
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 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.
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 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?
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-220.127.116.11. 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 18.104.22.168 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! "
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 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.
I downloaded the ubuntu-9.10-desktop-i386.iso file from the website, extracted it, and ran the Wbiu.exe file - it prompted to get my info and then restart. Upon restarting, I then had the choice to run Windows or Ubuntu, and I've been running Ubuntu ever since.
I ran into some speed-bumps. Upon entering the Ubuntu option at my start-up prompt, I go to another prompt asking me to choose from: Ubuntu, linux 2.6.31-20 Generic Ubuntu, linux 22.214.171.124 Recovery mode Ubuntu, linux 2.6.31-14 Generic Ubuntu, linux 2.6.31-14 Recovery mode Windows 7 installer Windows Vista installer I've been choosing the very first one, the 31-20 generic, but just this morning after downloading some programs from the Synaptic and transferring a few Gbs of music, I received this error prompt: Code: [2.879604] Kernel panic -- not syncing: VFS : Unable to mount roof fs on unknown--block (8,2) After that, I've been running the 2.6.31-14 generic installer. I have no idea what any of this means and I've spent time crawling through threads trying to figure it out. I mean, it still WORKS but I just help but think I've done something very wrong. ALERT: SUDO PASSWORD QUESTION
I hope the cautionary sign above has dispelled any annoyed gurus who have answered this question dozens of times before. I've crawled through my fair share of threads concerning this, the best corollary being the following: forum/linux-newbie/157773-solved-sudo-password-errors-usb-internet-issues.html; which, strangely enough, was never really solved. Like the user in that thread, when I access the terminal and type in a command, the next line invariably states "[sudo] password for jacob' -- when I hit enter and type in the long list of possibilities I've read (read: sudo, su, su root, su passwd, sudo passwd, sudo root, et al.), alas, nothing happens but the same statement.
i am just learning about computers and know nothing at all except how to turn it on. i just booted up linux and recieved message:  Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown - block (8,1)
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)
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:
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.
last part of init extracted from initrd-2.6.9-78.0.8.ELsmp.img:
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 126.96.36.199 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
I 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).
It is my first try getting Linux on my pc which is an Acer Aspire Z5610. This is not the first time for me when I am getting an Kernel Panic error on this computer.
I looked up google hoping to find an answer and I found out that it may be my BIOS's fault. I currently have Windows 7 on this PC. I have a Phoenix BIOS and there is an update for it called "Bios Linux" on the official Acer support website.
OK, after this short introduction, that's the error:
I really hope to get support for this problem as I can not literally install any other OS to this PC than Windows 7 because they fail with Kernel Panic.
Tried other Linux Editions and even Mac OS Intel Edition and IAtkos V1 and V7 and they all give kernel panic.
I untared a few libs on the wrong server (that's the when you're supposed to start laughing!) and I corrupted my server. Everytime it boots up, I get the following error:
/sbin/init: relocation error: /lib/tls/libc.so.6: symbol _dl_out_of_memory, version GLIBC_PRIVATE not defined in file ld-linux.so.2 with link time reference. Kernel panic - not syncing. Attempted to kill init!
I can I restore the original libs? I'm running RHEL 2.6.9-42 on a Proliant DL585.
After a reboot, my PC just hang. It says "insmod : error inserting '/lib/raid456.ko : -1 File exists ..." then followed by a kernel panic. I have tried to boot using rescue mode but it couldn't find any Linux partition, thus no /mnt/sysimage was mounted. It left me at a shell and I'm stuck there.
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory,HDPVR,nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps (I suspect also boot but I can't be sure; it just occasionally stalls part way through the boot display).
Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports:
Thread 1 (<main task>): Cannot access memory at address 0xffff880028025b70
I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory.
Does anyone know of a linux (or bootable) tester for video memory? All I am able to find are some things for windoze like this.
Also is there any way to track that address from the core dump back to a physical location?
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?
I am having a problem with lockups on a new FC12 box (dual core 3 ghz, 4 gb memory, HDPVR, nvidia 8400gs). This happens reliably when replaying MythTV videos, but also randomly at other times using other apps. Usually but not always this is accompanied by a kernel panic (caps lock + scroll lock lights flash on keyboard).
I did a core dump with kdump and it reports: Thread 1 (<main task>):
Cannot access memory at address 0xffff880028025b70I am in the process of running memtest86+ right now, and it's been through several passes without errors. I know it needs to run more, but given the reliability of this problem with MythTV video playback I am wondering if the problem could be in the video card memory. Any linux (or bootable) tester for video memory? All I am able to find are some things for windoze such as this. Also is there any way to track that address from the core dump back to a physical location?
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 study computational systems engineering.. and in my school (itlp) we've got fedora 12 installed in some of the computers.. and we use it to learn network administration and security. the reason of this message.. is that i want to install fedora 12 in my notebook (dv4-1525la vu068la).. but an error keeps poping up.. the error is the next one..
DMAR: No ATSR found DRDH: handling fault status reg f0003d63 Kernel panic - not syncing: DMAR hardware is malfunctioning
and though i have looked in bugzilla.. there is no help for me there.. they say.. "press tab in the welcome bootscreen when you are about to select whether to install or restore an existing system and write intel_iommu=off and press enter" but that does not really helps.. it just does the same.. in some blogs they say "upgrade your bios".. but i say.. then why i can not install the olders distributions with my "old" bios.
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!
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 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