Kernel Panic Mount Error 6 Mounting Ext3
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware Converter Standalone > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 7 Replies Latest reply: Sep 2, 2014 7:18 AM by kellyer RHEL 4 machine converted fine, but get kernel panic when I start the VM hawkeye11 Sep 18, 2012 6:31 PM So I have a bunch of old Red Hat 4 servers that I need to convert to VMs. I am using the standalone converter 5.0 and the VMs range from Red Hat version 2.6.9.-11 to 2.6.9-42. Some of the machines I can P2V with out any issues but a majority of them fail withmount: error 6 mounting ext3mount: error 2 mounting noneswitchroot: mount failed: 22umount /initrd/dev failed: 2 (see pic for more details)So I get a 100% complete when I use the Converter but when I boot up the VM I get that error. I have followed the directions from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002402 but I still not having any luck. I made changes to /etc/fstab, /boot/grub/grub.conf, /boot/grub/device.map etc... I am also having issues with rebuilding the ramdisk. I ran the command with the existing version on the drive but I get an error about about no modules found. I have also found another article saying the version of TAR might be an issue so i've upgrade the version to 1.14-15 and re-ran converter and it still failing. Anyone have any ideas what is wrong? I am windows admin with some linux background so please go detailed on the linux commands. 8152Views Tags: none (add) This content has been marked as final. Show 7 replies 1. Re: RHEL 4 machine converted fine, but get kernel panic when I start the VM sparrowangelstechnology Sep 18, 2012 8:34 PM (in response to hawkeye11) change the scsi controller type of the vm Like Show 0 Likes (0) Actions 2. Re: RHEL 4 machine converted fine, but get kernel panic when I start the VM hawkeye11 Sep 18, 2012 10:42 PM (in response to sparrowangelstechnology) I have tried switch between all 4 options and went back to LSI Logic Parallel. I have also tried to convert the VMs to vmware hardware 7 and it did not make a difference. I went as far as doing a straight copy of the HDD with ghost and I still have the same problems. Is there somet
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 https://communities.vmware.com/thread/418662?start=0&tstart=0 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 https://access.redhat.com/solutions/28605 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
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Thanks for posting this. I wanted to do this once or twice in the past, but never bothered to figure it out. I will be trying it soon... https://lists.centos.org/pipermail/centos/2007-April/036154.html I have a Mondo Backup of a server that I want to move to less powerful hardware, and hopefully this will do the trick. Dennis -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of dan1 Sent: Monday, April 09, 2007 11:22 AM To: CentOS mailing list Subject: Re: [CentOS] SOLVED: hard disk move to another server >You can at least try to prepare a new initrd (name it differently and >create a different entry in kernel panic grub.conf) with mkinitrd. >mkinitrd has a nice feature called --with=module so you can try to >mkinitrd --with=sata_via to include this module even if not 'already' >specified in /etc/modprobe.conf (don't forget also to change this after >the machine has correctly booted : 'alias scsi_hostadapter=') I've >never tested such hdd migration but it should work ... Hello, Fabian. Sorry for the very late answer. You are right, this did the trick. However, there was a thing to add to make it kernel panic mount work, we need to mount the /proc filesystem on the destination root directory for the mkinitrd to work properly. Else, thank you very much for the help you provided! The quick fix is to simply copy the /boot/initrd-xx.img file from a working installated drive on the destination server to the old drive partition, and it will work (you must update the grub entry of course). However, if you don't have such a working hard drive, you will need to recompile this initrd file. Therefore I post the complete procedure below to move a hard disk drive with a working CentOS 4 system from one server to another one, not having the same SATA chips, or from a PATA to an SATA or vice/versa. If you don't do this, then you might receive this kind of error: Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.8 starting mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! Here is my procedure for those who would need it: 1. To recreate the initrd file, we will do it by booting from a successful boot partition on the destination server, like the CentOS live CD for example, or any other hard drive a hard drive which has been installed with the CentOS installer on the destination server. We will mount the