Error 6 Mounting Ext3 Centos
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... 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 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 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 destination (failing) boot filesystem to /mnt/boot, and also its associated destination root filesystem, with these commands: mkdir /mnt/boot mkdir
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 https://lists.centos.org/pipermail/centos/2007-April/036154.html 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 https://communities.vmware.com/thread/418662?start=0&tstart=0 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. 8108Views 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
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 https://www.redhat.com/archives/linux-lvm/2010-June/msg00007.html 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 http://www.webhostingtalk.com/showthread.php?t=547369 and whatever SCSI drivers or modules are needed. Assuming that 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 error 6 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 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 error 6 mounting 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 failed to boot. Specifically: ------------------------------------------------------------- Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.8 starting Reading all physical volumes. This may take a while... No volume groups found Volume group "VolGroup00" not found ERROR: /bin/lvm exited abnormally! (pid 321) mount: error 6 mounting ext3 mount: error 2
Forums Hosting Security and Technology 2.6.17.8 Kernel panic - not syncing: Attempted to kill init If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 32 of 32 Thread: 2.6.17.8 Kernel panic - not syncing: Attempted to kill init Tweet Thread Tools Show Printable Version Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 09-14-2006,08:02 PM #1 rOCk-MaStEr View Profile View Forum Posts View Forum Threads WHT Addict Join Date Feb 2006 Posts 109 2.6.17.8 Kernel panic - not syncing: Attempted to kill init hello this is like the 4th time 2day for me trying to compile the kernel and this is the msg that the support got from console : Creating root device mkrootdev: label /1 not found Mounting root filesystem mount: error 2 mounting ext3 mount: errot 2 mounting none Switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing: Attempted to kill init! OS : CentOs 4 Reply With Quote 0 09-14-2006,08:07 PM #2 cywkevin View Profile View Forum Posts View Forum Threads Visit Homepage Predatory Poster Join Date Jul 2003 Location Goleta, CA Posts 5,550 Maybe you configured your file system options incorrectly. I would pay someone to compile the kernel so it gets done properly. Patron: I'd like my free lunch please. Cafe Manager: Free lunch? Did you read the fine print stating it was an April Fool's joke. Patron: I read the same way I listen, I ignore the parts I don't agree with. I'm suing you for false advertising. Cafe Owner: Is our lawyer still working pro bono? Reply With Quote 0 09-14-2006,08:11 PM #3 rOCk-MaStEr View Profile View Forum Posts View Forum Threads WHT Addict Join Date Feb 2006 Posts 109 no i think facing problems and having them fixed would make me learn too.. Reply With Quote 0 09-14-2006,08:18 PM #4 cywkevin View Profile View Forum Posts View Forum Threads Visit Homepage Predatory Poster Join Date Jul 2003 Location Goleta, CA Posts 5,550 Well if you want to learn take the output of lspci and make sure you have enabled support for the various devices in the kernel config. also search your startup log files for Kernel panic - not syncing: Attempted to kill init! and the lines before it will give you more information. Last edited by cywkevi