Error /bin/lvm Exited Abnormally
Red Hat Certificate System Red Hat Satellite Subscription Asset Manager Red Hat Update Infrastructure Red Hat Insights Ansible Tower by Red Hat Cloud Computing Back Red Hat CloudForms Red Hat OpenStack Platform Red Hat Cloud Infrastructure Red Hat Cloud Suite Red Hat OpenShift Container Platform Red Hat OpenShift Online Red Hat OpenShift Dedicated Storage Back Red Hat Gluster Storage Red Hat Ceph Storage JBoss Development and Management Back Red Hat JBoss Enterprise Application Platform Red Hat JBoss Data Grid Red Hat JBoss Web Server Red Hat JBoss Portal Red Hat JBoss Operations Network Red Hat JBoss Developer Studio JBoss Integration and Automation Back Red Hat JBoss Data Virtualization Red Hat JBoss Fuse Red Hat JBoss A-MQ Red Hat JBoss BPM Suite Red Hat JBoss BRMS Mobile Back Red Hat Mobile Application Platform Services Back Consulting Technical Account Management Training & Certifications Red Hat Enterprise Linux Developer Program Support Get Support Production Support Development Support Product Life Cycle & Update Policies Knowledge Search Documentation Knowledgebase Videos Discussions Ecosystem Browse Certified Solutions Overview Partner Resources Tools Back Red Hat Insights Learn More Red Hat Access Labs Explore Labs Configuration Deployment Troubleshooting Security Additional Tools Red Hat Access plug-ins Red Hat Satellite Certificate Tool Security Back Product Security Center Security Updates Security Advisories Red Hat CVE Database Security Labs Resources Overview Security Blog Security Measurement Severity Ratings Backporting Policies Product Signing (GPG) Keys Community Back Discussions Red Hat Enterprise Linux Red Hat Virtualization Red Hat Satellite Customer Portal Private Groups All Discussions Start a Discussion Blogs Customer Portal Red Hat Product Security Red Hat Access Labs Red Hat Insights All Blogs Events Customer Events Red Hat Summit Stories Red Hat Subscription Benefits You Asked. We Acted. Open Source Communities Subscriptions Downloads Support Cases Account Back Log In Register Red Hat Account Number: Account Details Newsletter and Contact Preferences User Management Account Maintenance My Profile Notifications Help Log Out Language Back English español Deutsch italiano 한국어 français 日本語 português 中文 (中国) русский Customer Portal
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 rescue kernel matches the kernel on the failed drive, mkinitrd _should_ take https://access.redhat.com/solutions/32016 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. We want to be able to see /dev/sda it order to set up to boot from it. Along https://www.redhat.com/archives/linux-lvm/2010-June/msg00007.html 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 stumping me. I have an old server's drive (IDE) that has CentOS 4 on it. The mainboard fried, so I imaged the drive using 'dd' onto a new drive and tried booting from it. Not surprisingly, it
start Centos General support questions including new installations Post Reply Print view Search Advanced search 13 posts 1 2 Next thanh_hien73 Posts: http://www.centos.org/forums/viewtopic.php?t=13175 6 Joined: 2009/04/08 09:43:27 error 'noapic' when start Centos Quote Postby https://forum.acronis.com/forum/19741 thanh_hien73 » 2009/04/08 11:06:40 i restore Centos from backup file,after i have finished,i start centos, it can't start and repost error: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. Who can help me? Top gerald_clark error /bin/lvm Posts: 10594 Joined: 2005/08/05 15:19:54 Location: Northern Illinois, USA Re: error 'noapic' when start Centos Quote Postby gerald_clark » 2009/04/08 13:31:40 Did you do as suggested?Is this a restore onto a new machine? Top szymon_g Posts: 6 Joined: 2008/05/22 15:12:42 Re: error 'noapic' when start Centos Quote Postby szymon_g » 2009/04/08 22:03:11 http://bugs.centos.org/view.php?id=3503NOAPIC and NOSMP in grub.conf (you error /bin/lvm exited can add them directly from grub, just press 'e' and write them in the kernel line) helped me. Unfortunatelly, I dont have smp - i.e. i cannot use both cores of my processor (core 2 duo). I tried Centos Extra kernel, i tried Redhats kernels (I even compiled one by myself) didn't helped. I doubt, however, that its a hardware problem: debian, ubuntu, opensuse and arch works fine on it.Now i'm trying to compile Fedora 10 kernel wish me luck ;pbest regardsszymon Top thanh_hien73 Posts: 6 Joined: 2009/04/08 09:43:27 Re: error 'noapic' when start Centos Quote Postby thanh_hien73 » 2009/04/09 02:48:01 yes,i restore it onto new machine, and error: 'noapic' or ''kernel panic- not syncing: attempted to kill init". help me. i also add noapic on kernel line when i typed 'e' key at green desktop but it don't work !!!! Top thanh_hien73 Posts: 6 Joined: 2009/04/08 09:43:27 Re: error 'noapic' when start Centos Quote Postby thanh_hien73 » 2009/04/09 07:03:18 i repaired in BIOS and fix error 'noapic'. Now i amn't work
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 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 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 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