Did you read the fine print stating it was an April Fool's joke. Here is my procedure for those who would need it: 1. Re: RHEL 4 machine converted fine, but get kernel panic when I start the VM KlausK Sep 23, 2012 11:19 AM (in response to hawkeye11) I ran into a kernel panic Like Show 1 Like (1) Actions 6.

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). If it doesn't note what the return value is, eg (hd1,4). Did you edit /etc/fstab to change hda to sda, hdb to sdb, etc., before running mkinitrd? However, there was a thing to add to makeit work, we need to mount the /proc filesystem on the destination rootdirectory for the mkinitrd to work properly.

its a CentOs on AMD Opteron # cat /etc/modprobe.conf~ alias scsi_hostadapter sata_sil alias eth0 e100 Reply With Quote 0 09-21-2006,06:47 AM #28 cywkevin View Profile View Forum Posts View We then rebuild an initrd file by typing the following:mkinitrd --with=sata_via /initrd-new.img 2.6.9-42.0.10.ELTo know the proper kernel version to use (last number of the command line),you need to use an existing Is the 250GB drive listed first in the boot order for the hard drives in your bios setup? Make sure that the /etc/modprobe.conf file contains the driver you have added to this line: alias scsi_hostadapter sata_via 6.

Did you read the fine print stating it was an April Fool's joke. foodown View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by foodown Thread Tools Show Printable Version Email this Page Search this Thread Advanced I haven't had to do it in such a long time that Iprobably missed a step. https://communities.vmware.com/thread/418662?start=0&tstart=0 This didn't work.It did compile the new kernel, but has taken the other module, not thecorrect one for the new system.Maybe it did take the module from the old config file

The config you posted looks fine to me, so long as your new kernel image is actually located at /vmlinuz-2.6.18 and everything else is correct. Last edited by cywkevin; 09-14-2006 at 08:23 PM. i couldn't find my way for it i think udev should be enabled from the Distro.. Like Show 0 Likes (0) Actions 5.

Somewhat easier than remembering the proper initrdcommands.Hello, Scott.Thanks for the suggestion. However, we mustfirst create the /proc filesystem on the chrooted partition, else thecompilation won't work properly:mount -t proc none /mnt/root/proc3. 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 On my mdv2008 the ide hard drive is still dealt wiht as /dev/hde which is the normal designation for that drive.

Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. I have installed mandriva 2008 on an external (USB) harddrive. 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, this contact form Else, thank you very much forthe help you provided!The quick fix is to simply copy the /boot/initrd-xx.img file from a workinginstallated drive on the destination server to the old drive partition,

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. This also implies that the module you need is in a stock kernel. -- MailScanner is like deodorant... You"re Not Alone, Dell Study Finds GoDaddy Hits One Million .UK Registration Milestone Webmail User Onboarding: A Goldmine of Marginal Gains HostingCon Europe 2016 Countdown: Plan Your Educational Experience Today Report:

We do not create the initrd file in the boot directory, because we can sometimes not access it at this time (especially with md partitions), but we will simply copy the I am also having issues with rebuilding the ramdisk. Ok, booting the kernel.Red Hat nash version 4.2.1.8 startingmount: error 6 mounting ext3mount: error 2 mounting noneswitchroot: mount failed: 22Kernel panic - not syncing: Attempted to kill init!Does anyone know how I can 'chroot /mnt/sysimage' just fine.

Make sure that the /etc/modprobe.conf file contains the driver you haveadded to this line:alias scsi_hostadapter sata_via6. alias hostadapter2 sata_nv Rebuilt a new initrd with, for example... I ran the command with the existing version on the drive but I get an error about about no modules found. navigate here Now, let's come out of the chroot:exit7.

To check on how grub sees the hard drives at boot time do the following: 1. Take a look at this output for fdisk -l /dev/hde: Disk /dev/hde: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 Introduction to Linux - A Hands on Guide This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started Thatshould redo the initrd.

Normally you should take the last one. You hope everybody uses it, and you notice quickly if they don't!!!! the Live CD won't boot too !! Might it might look at mtab?

Therefore I post the complete procedure below tomove a hard disk drive with a working CentOS 4 system from one server toanother one, not having the same SATA chips, or from It will be in the form of (hdx,4). Else, thank you very much forthe help you provided!The quick fix is to simply copy the /boot/initrd-xx.img file from a workinginstallated drive on the destination server to the old drive partition, However, if you don't have such a working hard drive, you will need to recompile this initrd file.