CentOS 5 :: Kernel Panic Creating LVM Snapshot Of Root Fs Volume
Oct 29, 2009
I can cause the kernel to panic immediately with the following command. lvcreate --snapshot --name Snap --extents 100%FREE VolGroup00/LogVol00 The last line of the panic message is "<0>Kernel panic - not syncing: Fatal exception" If I create a snapshot of any other volume it works just fine. It only panics on LogVol00 which is my root fs.
I'm running 5.4 after update from 5.3. It didn't work with 5.3 either. This is a 32-bit guest running in VMWare Server 2.0.1 which is running on FC10 x86_64. I've tried the guest in both UP and SMP (2 cores) modes and observed no difference.
View 2 Replies
ADVERTISEMENT
Aug 14, 2010
Recently, I've tried to create a snapshot of my /root folder in 10.04 (I remember to have done so a couple of times without trouble).I used the commandHTML Code: Code: lvcreate -L10G -s -n rootsnapshot /dev/server/root Without a hint of HDD activity, Gnome (?) hangs up - I can move the mouse, and the clock is moving on, but I can't click on anything. No HDD activity, and this goes on forever (after a while, the whole system locks up). This happens each time when I try to create a snapshot.
View 3 Replies
View Related
Jun 11, 2010
I have a CentOS 5.4 storage server with LVM/RAID1 setup, I need to change the motherboard from Gigabyte GA-G31M-ES2C to Asus P5K-E. After the switch, I got kernel panic during boot (the following is copied manually from the screen, is these stuff recorded somewhere in the log? I checked /var/log/messeges but didn't find anything):
Code:
Scanning and configuring dmraid support
md: Autodetecting RAID arrays
md: autorun....
md: ... autorun DONE
[code]....
I used CentOS CDROM and entered rescue mode to take a look, some findings:
1. Initially the drive label is different from my old system, for example the old sdb became sdc. I switched the SATA cable around to get this sorted out except one IDE drive (originally hda, now hde), but this drive is not used in RAID
2. After the label is fixed, I used mdadm to check RAID1 devices (md0/1/2/3), it seems each device is missing a drive (originally md0 is created by sda1+sdb1, now it's just sdb1, and thus degraded). I used mdadm to re-add the missing drive, mdadm --detail shows everything is fine now.
3. Step 2 didn't fix the error, so I "chroot /mnt/sysimage/" and took a look around, all the directories seem fine, include the ones on "main" volume group. vgscan/vgdisplay/lvdisplay shows all the vg and lv as they should be.
View 4 Replies
View Related
Mar 20, 2011
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.
View 2 Replies
View Related
Feb 2, 2010
I recently (a couple weeks ago) installed Ubuntu on my desktop computer dual booting with Win XP (which I am using right now). I used Wubi to install it, and everything went fine. I used Ubuntu without a problem up until a few days ago. I am using an install of Ubuntu (I am not running it off a disc, USB drive or through the Wubi software).
I restarted my computer after using Ubuntu constantly for the time I've had it installed. It booted into Win XP (because it was first on the list where you select which OS to load) so I restarted again and tried to boot into Ubuntu. Instead of working, it gave me the error "Kernel panic - not syncing: unable to mount root" or something like that. So, I restarted again, and it was the same thing. I restarted in recovery mode, and it was the same thing.
View 9 Replies
View Related
May 3, 2010
Fresh install on an acer.CRC=3691807100boots livecd fine selected to replace entire disk now presented with vfs error after install and reboot. This is a full replace install taking all the disk not a wubi install. Please help I don't want to have to reinstall windows 7 (PC has worked sweet as for 4 weeks with windows 7 just need to get back to ubuntu again
View 1 Replies
View Related
May 5, 2011
I 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 .....
View 3 Replies
View Related
Apr 19, 2011
I have been dual booting "Windoz" (hda1) and slackware 11 (RTAI - hda 5) old system. The problem happen after I installed slackware 13(sda8) on the same hard drive. I was able to mount my old slack11 (now (sda5)) to slack13 to read. So I wanted to boot to slack11.
MY Lilo on slack 13:
Now when I boot to Slackware11 I get:
VFS:
How can I boot a old "hda" image on "sda" system. With a floppy I can go back to Slackware11.
View 7 Replies
View Related
Jun 7, 2010
I am using a kernel with no initrd. I have had this kind of panic before. Usually it means that the kernel can access the hard drive because the driver for the controller or filesystem isn't built into the kernel.
The kernel is 2.6.34 vanilla.
My IDE controller is a Silicon Integrated Systems SiS 5513, and I built the driver for it into the kernel BLK_DEV_SIS5513=y
My /boot (hda1) is ext2, and everything else is ext3
EXT2_FS=y
EXT3_FS=y
My grub entry (hda2 is my root partition) kernel (hd0,0)/vmlinuz root=/dev/hda2
View 5 Replies
View Related
Jul 26, 2010
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.
View 3 Replies
View Related
Apr 29, 2010
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)"
I get the options to boot too:
2.6.31-21-generic
2.6.31-21-generic(recovery mode)
2.6.31-20-generic
2.6.31-20-generic(recovery mode)
[Code].....
PS - I really don't want to sound like a jerk
View 6 Replies
View Related
May 13, 2010
I had 9.10 installed on my IBM Lenovo Thinkpad, x301. I was performing updates as normal, and chose the Upgrade button to upgrade me to 10.04. Everything started fine, but upon reboot, no bueno, Kernel Panic!
The exact message was "Kernel Panic ubuntu - not synching VFS Unable to mount root fs".
I thought this was a grub issue. Since grub2 now is installed... But it was not. I think it ended up being a problem with some of my configuration files.
I have three kernels I tried:
1. 2.6.32-22
2. 2.6.31-21
3. 2.6.31-20
The first threw me into the kernel panic.
The second would hang on "init crypto disks"
The third would hang on "checking battery state"
I noticed (from reading another thread) that while these are loading up that you can click on alt-ctl-F1 thru F6 and get prompt. (I also had my home directory encrypted, thought that was part of the problem, but it wasnt).
Once I get passed the loging, I am able to poke around. I tried manually start Gnome via "sudo service gdm start", but it failed. Said it was missing a configuration file. Then I tried on "sudo dpkg-reconfigure gdm" and it would not work. Saying some configuration files are missing or broken. It also said something about dpkg --configure -a, I am assuming this configures everything...
So I tried "sudo dpkg --configure -a" And selected 'y' to every option. Which basically installs the package creators default settings, and viola! Works.
Just wanted to share that knowledge for the other stuck in the upgrade hell.
Normally I would just copy my files off and reinstall, but it was encrypted... Another headache. I guess good in case someone stole my laptop.
Remember try to "sudo dpkg --config -a"
View 7 Replies
View Related
Jul 9, 2009
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.
View 1 Replies
View Related
Jul 23, 2010
I just installed the DVD iso of Fedora 13...and did a "sudo yum update" after the installation got finished. After 3 hours of waiting, I restarted. I was greeted by Fedora with a kernel panic, right after it boots up.
Here's the message:
Code:
Kernel Panic - not syncing: VFS unable to mount root fs on unknown-block (0,0)
EDIT: Here's the content of grub.conf
Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
[code]....
What is peculiar on this grub.conf, is that the 2.6.33.6-147 boot conf is missing an initrd line...I looked in the /boot directory...and I found out that the initramfs file that matches the 2.6.33.3-147 kernel is also missing (i.e initramfs-2.6.33.3-147.fc13.i686.PAE.img).
View 1 Replies
View Related
May 10, 2011
My Fedora 14 box is no longer starting. I am getting a message at startup - "Kernel panic - not syncing:
VFS: Unable to mount root fs on unknown-block(0,0)".
Unfortunately, I don't know what I did before I got the message. I mean, I have made various installations, including some kernel drivers (such as a wifi card and a sound card). Also I did need to update the kernel-devel package as a requirement for some install or other. I know that is not very helpful, but let's get to the important bit...
What does the message "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" mean? What has broken?
And how does on recover from it? I have been reading around, and of course I am able to boot the machine from a live CD, but I am not sure what I should do with grub.conf, what I should rebuild, how to do it and so on.
View 3 Replies
View Related
Feb 2, 2010
I'm using Ubuntu 9.10 through Windows 7 and got this message today...
kernel panic- not syncing VFS: unable to mount root fs on unknown block (8,1)
Is there a way to fix this? (and I'm going to need really simple instructions here)
Also I tried to uninstall ubuntu in windows 7 and then reinstall but it will not let me. it says that an error has occurred: The system cannot find the file specified stdout=
View 4 Replies
View Related
Feb 6, 2010
I was updating my Ubuntu 9.10 Karmic Koala when i decided that i should reboot my computer. All the downloads were done. When i rebooted it booted in normally but when it got into the kernel loading part, Linux-Bzimage and initrd loaded fine, But then Kernel Panic - not syncing : VFS: Unable to mount root as fs on unknown-block (8,1) came up. This is a wubi install also, and i have never had any troubles before.
View 9 Replies
View Related
Mar 27, 2010
So, we had a power cut, and when I turned it back on, I got:
Quote:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)
Hence, the computer won't boot.
Ubuntu is installed within windows.
I had so much data on there, How to without a re-install?
View 6 Replies
View Related
May 19, 2010
[ 0.719079] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I was installing updates on my Ubuntu 9.10 and one of them was the upgrade to the new 10.04 LTS. So I said, okay, great! Installed the updates, upgraded my Ubuntu (even though it informed me that some packages had errors). I restarted my PC and then I get this error. I don't know what happened, but that's the error I get when I turn my PC on. Nothing else happened.
PC Specs Compaq, 32-bit processor, 2GB ram, ATI Xpress 200 graphics, Realtek soundcard. PS/2 keyboard, USB mouse. SyncMaster 920Nx flat-panel monitor.
What I did to try to fix this, regardless of it not worked:I tried resetting the BIOS. Didn't do anything. I still get the error.Tried running from CD. It didn't detect the CD or anything, I guess, because I still get the error and it didn't let me run the CD.
View 2 Replies
View Related
Dec 8, 2010
I screwed up trying to install a new kernel Now, when I try to boot up, it says: kernel panic not syncing VFS unable to mount root fs on unknown block My system:
-encrypted LVM with encrypted home
-10.04 ubuntu system
What's the easiest/fastest way recover the documents on my encrypted home folder? I have the home folder encryption passphrase. I just want to recover and backup those documents, even if after that I have to reinstall the whole system. I have a live CD and also another 10.04 system on a second computer. I've managed to mount the hard drive in this second system and see everything on it, except the contents of the user home folder (Private). Everything I see on the internet is about encrypted home, but not top of a LVM encrypted.
View 3 Replies
View Related
Apr 20, 2011
I am currently running the latest version of Ubuntu (10.10 I believe) and recently installed a new, vanilla 2.6.37.1 kernel on my machine. Then, all I did was run update-grub (I'm not sure if this is correct as I am new to GRUB2 :/), rebooted and tried to boot into the new kernel, but I got the above error on boot. Does anyone know why this is happening?
View 9 Replies
View Related
Dec 13, 2010
I have trawled through an extensive number of post on quite a few forums without even a step forward with this.
I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively), swap is not raided.
I was doing an yum update through the software updater in gnome and the system froze.
I had to press reset to get any response from the machine.
Since then I have been getting the kernel panic above just after grub starts fedora.
I tried the previous kernel from the previous update and it has the same error.
At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead.
Is there any way to access these partitions through a live CD or rescue environment?
Is there a method to bring this install back to life? or am I looking at a reinstall?
View 1 Replies
View Related
Dec 13, 2010
I have trawled through an extensive number of post on quite a few forums without even a step forward with this.
I have a fedora 13_x64 system with software raid1 for /boot and / (md0 and md1 respectively) , swap is not raided.
I was doing an yum update through the software updater in gnome and the system froze.
I had to press reset to get any response from the machine.
Since then I have been getting the kernel panic above just after grub starts fedora.
I tried the previous kernel from the previous update and it has the same error.
At the worst I am prepared to load OS again but there is still some info and configs that I would like to access from the raid partitions before I go ahead. Is there any way to access these partitions through a live CD or rescue environment?
Is there a method to bring this install back to life? or am I looking at a reinstall?
View 1 Replies
View Related
Jan 12, 2010
I have an ongoing issue that I've not been able to troubleshoot. Upon bootup I get the following text and error, and it stops. ACPI: Aborted because bad gzip magic numbers MP-BIOS bug: 8254 timer not connected to IO-APIC Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)
View 2 Replies
View Related
May 5, 2010
I recently started to use Ubuntu in VWware player on my windows-XP. I installed ubuntu 10.04 few days ago, It was working fine.
Yesterday, I compile a new kernel, kernel 2.6.33 in my vmware ubuntu 10.04. Everything went well till I did reboot. before reboot I use the command "update-grub" to make it compatible to the new kernel. BUT... after rebooting, I have a problem in loading a grub correctly. it gives me following message " [2.149136 ]kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)" and I can not proceed further. I have my all data on it. I also tried to boot it from live CD but unfortunately, I can't mount the hard disk on it in order to get those data from my old Ubuntu set up.
View 4 Replies
View Related
Aug 5, 2011
I need to recover some data of the 'home' directory after kernel panic.I was upgrading ubuntu 11.04, [COLOR=blue !important][COLOR=blue !important]installed[/COLOR][/COLOR] on usb.Failed to upgrade because the main partition had no more space. I moved one directory of about 100Mb to other partition, but it seemed that in the main partition didn't appear those 100Mb free. i restarted the computer expecting those 100Mb free. And kernel panic.
[ 0.789567] Kernel panic - not syncing: VFS: Unable to mount root fs on unknow-block(8,1)
[ 0.789646] Pid: 1, comm: swapper Not tainted 2.6.35-22-generic #33-Ubuntu
[ 0.789716] [<c05c6468>] ? printk+0x2d/0x35
View 2 Replies
View Related
Feb 1, 2010
I just installed a fresh copy of Fedora Core 12 on a system. I have a 1 GB swap partition, a 20 GB root partition and a 50 GB /video partition (for a mythtv system I am building).
Installation went fine, but upon the initial boot, I get:
Kernel panic - not syncing: vfs: unable to mount root fs on unknown block (0,0)
I can boot off the FC12 cd and go to the rescue option and get to a shell, but not sure where to go from
View 9 Replies
View Related
Jul 31, 2010
I was following this tutorial on How install the rpmfusion nvidia drivers in Fedora 13Here's the tutorial:Quote:Originally Posted by leigh123linuxF13 Howto for the rpmfusion nvidia drivers This is a Three-Step Process. If you don't follow all three steps, your install will fail!1. Install the nvidia driver. ( if you have 4Gb of RAM or more you will probably have a PAE kernel [32bit only] so follow the PAE part )For GeForce 6, 7, 8, 9, 200 & 300 series cards
Code:
su
rpm -Uvh http://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-
[code]...
View 2 Replies
View Related
Feb 10, 2010
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: [0800654] Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown - block (8,1)
View 5 Replies
View Related
Jun 5, 2010
im a rookie at configuring linux and i have problem booting slackware 13.1 just installed. i get a message similar to this Kernel panic - not syncing: VFS: Unable to mount root fs on unknown- block(8,4) i got this one from another user who has a similar problem, they say i should fix lilo.conf and it actually was pointing to a wrong partition so i fixed it. i also fixed /etc/fstab to make it point to the right partition /dev/sda3. but after fixing the files, it still wants to load something in /dev/sda4, i dont know why so what should i do next, please explain with commands and not just words. edit this is my lilo.conf
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sda3
[Code]...
View 12 Replies
View Related
