Error /bin/lvm Exited Abnormally Kernel Panic

Tue, 6 Feb 2007 15:08:59 -0800 (PST) I'm running into a kernel panic when I change the VolGroup that the system is in. I'll go more into how I do this in a minute. But the reason I do it is that I must take a hard drive out of another system put it in another system so the data can be copied. I have 9 systems that have the default lvm install config. The 9th system is used to put the harddrives from the 8 systems one at a time to read the data from the drives. I'm trying to change the VG VolGroup00 of system 9 to VolGroup99 so that I can mount the other system with VolGroup00 when I need too. Hopefully, with a usb adaptor or something of that sort. What I do is boot system 9 with the Rescue CD and do a # lvm vgchange -a n and then # lvm vgrename VolGroup00 VolGroup99 and I get a success message that the VG has been changed. I test mount the lv and I can read and write data fine. I then reboot the system edit the line in grub on bootup to VolGroup99 and get the kernel panic message below the line. I'm using RedHat Enterprise Linux WS 4 Update 4 with kernel 2.6.9-46.ELsmp which I found from the message forums. Is their some sort of config I'm not changing that I'm supposed too? I thought the kernel update I applied was supposed to fix this. Thanks, Thomas ---------------------- root(hd0,0) Filesystem type is extfs, partition type 0x83 Kernel /vmlinuz-2.6.9-46.ELsmp ro root=/dev/VolGroup99/LogVol00 rhgb quiet [Linux-bzImage, setup=0x1400, size=0x1604fe] initrd /initrd-2.6.9-49.ELsmp.img [Linux-initrd 0x37ef3000,0xfcaf9 bytes/ Uncompressing Linux... Ok, booting the Kernel Red Hat nash version 4.2.1.8 starting Reading all physical volumes. This may take awhile... Found volume group "VolGroup99" using metadata type lvm2 Volume group "Vol"Group00" not found Error: /bin/lvm exited abnormally! (pid 484) mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not synching: Attempted to kill init! Follow-Ups: Re: Kernel panic when LVM VG is changed From: Tom Sightler [Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]

com> Subject: Re: [linux-lvm] Imaged a drive, now kernel panics Date: Sat, 05 Jun 2010 22:33:22 -0500 You mentioned that the old drive is IDE. If so, You may be running into a couple problems I've had. I take it the new drive is SATA, SAS, or SCSI? Did you edit /etc/fstab to change hda to sda, hdb to sdb, etc., before running mkinitrd? The existing kernel may not have the needed drivers compiled in, the drivers for the particular chipset and whatever SCSI drivers or modules are needed. Assuming that https://www.redhat.com/archives/nahant-list/2007-February/msg00054.html rescue kernel matches the kernel on the failed drive, mkinitrd _should_ take care of that if /etc/fstab is correct. Might it might look at mtab? I also tried moving the current kernel out of the way and using 'mkinitrd' to rebuild the image (after chrooting and making sure everything looked fine) Be sure to bind /proc, /sys, /dev, and /selinux into the chroot. https://www.redhat.com/archives/linux-lvm/2010-June/msg00007.html We want to be able to see /dev/sda it order to set up to boot from it. Along the same lines, double check that any other partitions, primarily /boot, are mounted in the chroot. That should pretty much you, but before I figured out some of the possible failure modes I build modified several initrd by hand. You can debug the init script with simple echo statements much like you would debug any simple script. One last thing - on some motherboards the BIOS can be set to present a SATA drive as if it were IDE, I understand. qemu-kvm can also present a hard drive image as either SCSI or IDE, regardless of the actual underlying hardware. So you could present your SATA or SCSI drive as an IDE drive in order to make the old initrd and kernel happy. -- Ray Morris support bettercgi com Strongbox - The next generation in site security: http://www.bettercgi.com/strongbox/ Throttlebox - Intelligent Bandwidth Control http://www.bettercgi.com/throttlebox/ Strongbox / Throttlebox affiliate program: http://www.bettercgi.com/affiliates/user/register.php On 06/05/2010 07:59:49 PM, Digimer wrote: Hi all, I am sure this is a fairly common issue, but it's s

Registration E-mail: * Password: * Useful Links How to get Support? All Product Documentation Frequently asked questions by product Acronis Backup 12 FAQ Acronis Backup 11.7 FAQ Acronis Backup & Recovery FAQ Acronis True https://forum.acronis.com/forum/19741 Image 2017 FAQ Acronis True Image 2017 Mac: FAQ Upgrading to Acronis True Image 2017 Grover's True Image Guides Acronis Disk Director 12 FAQ Acronis Disk Director 11 FAQ Product pages Acronis Home Products Acronis Business Products Acronis Forum Archive Home › Forums › Acronis Business Products Discussions › Acronis Backup & Recovery 10 & 11 Forum 19741: RedHat Linux 4 Kernel panic not syncing kill init no volume groups found Login error /bin/lvm to post comments 2 replies [Last post] Mon, 2011-03-21 05:09 Gilbert Florescu Offline Beginner Joined: 2010-11-06 Posts: 2 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 error /bin/lvm exited 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 Filesystem Size Used Avail Use% Mounted on /dev/volgroup00/logvol00 4.0G 3.2G 558M 86% / /dev/sda3 190M 41M 140M 23% /boot /dev/volgroup00/logvol05 6.9G 117M 6.5G 2% /home /dev/volgroup00/logvol03 4.0G 78M 3.7G 3% /tmp /dev/volgroup00/logvol06 109G 14G 89G 14% /u01 /dev/volgroup00/logvol02 7.9G 3.5G 4.1G 46% /usr /dev/volgroup00/logvol04 4.0G 1.4G 2.4G 37% /var #fdisk -l Disk /dev/sda: 740.8GB 255 heads, 63 sectors per track, 90073 cylinders Device Boot Start End Blocks ID System /dev/sda1 1 8 64228 de Dell Utility /dev/sda2 9 531 4200997 8e Linux LVM /dev/sda3 *