Hi.
I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine from a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every attempt to convert this machine I get a "Kernel panic"
mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc failed: No such file or directory setuproot: error mounting /sys failed: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!-220000
I have follows the VMware provided solution for this situation but the results are the same http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd... http://blog.edgoad.com/2010/03/vmware-no-volume-groups-found.html
I have re-installed the CentOS kernel but that didn't make any difference. I have tried installing disk labels but that didn't make any difference. I have installed a clean install of 5.3 into a new vm , I even did a custom disk configuration to match that created by VMware Converter and that worked fine with most of the configuration being the same with the exception that it used disk labels.
I'm at a loss at this point , I'm open to suggestions.
Here are my configs as shown when using a rescue disk and chroot into /mnt/sysimage
[root@localhost /]# cat /boot/grub/grub.conf # grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 console=ttyS0,9600n8 console=tty0 # initrd /initrd-version.img #boot=/dev/sda default=0 timeout=5 #splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu # (removed by Converter) title Memtest86+ (1.65) # (removed by Converter) root (hd0,0) # (removed by Converter) kernel /memtest86+-1.65 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
title CentOS (2.6.18-128.7.1.el5) root (hd0,0) kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet # kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=LABEL=/ initrd /initrd-2.6.18-128.7.1.el5.img
#title CustomKernel (2.6.18-128.7.1.el5) # root (hd0,0) # kernel /vmlinuz-2.6.18-128.7.1.el5 ro root=/dev/sdb1 rhgb quiet # initrd /initrd-2.6.18-128.7.1.el5.img [root@localhost /]#
[root@localhost /]# cat /boot/grub/device.map (hd0) /dev/sda (hd1) /dev/sdb [root@localhost /]#
[root@localhost /]# cat /etc/fstab /dev/sdb1 / ext3 defaults,noatime 1 2 #LABEL=/ / ext3 defaults,noatime 1 2 LABEL=/boot /boot ext3 defaults 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 [root@localhost /]#
[root@localhost /]# fdisk -l /dev/sda
Disk /dev/sda: 108 MB, 108134400 bytes 4 heads, 32 sectors/track, 1650 cylinders Units = cylinders of 128 * 512 = 65536 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 2 1633 104448 83 Linux [root@localhost /]# fdisk -l /dev/sdb
Disk /dev/sdb: 159.9 GB, 159921602560 bytes 143 heads, 28 sectors/track, 78008 cylinders Units = cylinders of 4004 * 512 = 2050048 bytes
Device Boot Start End Blocks Id System /dev/sdb1 1 78009 156172288 83 Linux [root@localhost /]#
[root@localhost /]# mount /dev/sdb1 on / type ext3 (rw,noatime) /dev/sda1 on /boot type ext3 (rw) devpts on /dev/pts type devpts (rw) tmpfs on /dev/shm type tmpfs (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) [root@localhost /]#
Thank you. G
On Tue, 17 Dec 2013, Gregory Machin wrote:
Hi.
I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine from a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every attempt to convert this machine I get a "Kernel panic"
mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc failed: No such file or directory setuproot: error mounting /sys failed: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!-220000
I'm not following all of what is on the machine here, but here are some general things to try:
1. From what I can tell, your grub.conf expects /boot to be on its own partition, which appears to be sda1 .. is that the case?
2. Verify your /etc/fstab looks right for the new virtual HW you set up.
3. If that is correct, try using "grub-install /dev/sda" to reinstall your bootloader.
4. You might trying using the older/compatible versions of hardware, specifically the SCSI controller in case that is an issue.
5. In the event that it really can't find /proc or /sys mount in a chrooted rescue environment run "mkdir /proc /sys ; chmod 555 /proc ; chmod 755 /sys"
Good luck! Barry
On Tue, Dec 17, 2013 at 6:06 PM, Barry Brimer lists@brimer.org wrote:
On Tue, 17 Dec 2013, Gregory Machin wrote:
Hi.
I used VMware Standalone converter 5.5 to convert a CentOS 5.3 machine
from
a Physical server to a Virtaul Machine on ESXi 5.1 . Thus far with every attempt to convert this machine I get a "Kernel panic"
mount: could not find filesystem '/dev/root' setuproot: moving /dev failed: No such file or directory setuproot: error mounting /proc failed: No such file or directory setuproot: error mounting /sys failed: No such file or directory switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!-220000
I'm not following all of what is on the machine here, but here are some general things to try:
- From what I can tell, your grub.conf expects /boot to be on its own
partition, which appears to be sda1 .. is that the case?
Yes, originally /boot and / where on the same disk as seperate partitions,
VMware converter recreates them as separate disks each with its own partition /boot on /dev/sda1 and / on /dev/sdb1 .
- Verify your /etc/fstab looks right for the new virtual HW you set up.
As far as I can tell it should be correct.
- If that is correct, try using "grub-install /dev/sda" to reinstall
your bootloader.
As far as I can tell this is correct.
- You might trying using the older/compatible versions of hardware,
specifically the SCSI controller in case that is an issue.
I have tried all the available hardware options. I have gone as far back
as vmx-4 and tried all the scsi controler options.
5. In the event that it really can't find /proc or /sys mount in a
chrooted rescue environment run "mkdir /proc /sys ; chmod 555 /proc ; chmod 755 /sys"
I deleted the directories and recreated as above but no luck.
Good luck! Barry
On 12/17/2013 2:06 PM, Gregory Machin wrote:
I deleted the directories and recreated as above but no luck.
In similar conversions I've done in the past, I've found that the server I've converted from is using a different SCSI driver that isn't compatible with the VMware virtual SCSI devices.
I assume you're booting from ISO into the rescue environment to check the things that have already been suggested. When you do, does the installer find the existing Linux installation and mount it correctly? If so, try:
1. Boot from an ISO into the rescue environment and have the installer mount your system on /mnt/sysimage
2. Bind mount the /dev and /proc filesystems into the recovered image:
mount -o bind /dev /mnt/sysimage/dev mount -o bind /proc /mnt/sysimage/proc
3. chroot to your installed system:
chroot /mnt/sysimage
4. Save your existing initrd, just in case:
mv /boot/initrd-KERNELVERSION.img /boot/initrd-KERNELVERSION.img.save
5. Create a new initrd:
mkinitrd /boot/initrd-KERNELVERSION.img KERNELVERSION
6. Exit out of the rescue environment, reboot, and hope for the best..
On Tue, Dec 17, 2013 at 6:55 PM, Eric Michaelis combinare@gmail.com wrote:
- Create a new initrd:
mkinitrd /boot/initrd-KERNELVERSION.img KERNELVERSION
- Exit out of the rescue environment, reboot, and hope for the best..
I'd do a "grub-install /dev/sda" while your are there...
In similar scenarios, I've sometimes done a fresh install of another VM, updated to the same rev as the copied system, then copying the contents of /boot over to the one that isn't working. Roundabout, but anaconda knows a lot more than I do about matching drivers to devices - and there may be something interesting in /etc/modprobe.conf too. If you are willing to start from scratch and have a host with some NFS space to hold a temporary backup, you could try copying the system with the 'rear' package from EPEL. It will make a bootable iso image (that you can map into the VM to boot) that includes the tools from your running system to partition and set up the filesystems before restoring the backup into it. I've used it to convert some systems with raid, etc. that the VMware converter did not recognize. Also, it gives you a chance to edit the filesystem layout if you want (not exactly straightforward, but at least possible).
-
Barry Brimer -
Eric Michaelis -
Gregory Machin -
Les Mikesell