VectorMaritime
asked on
Fail to boot a cold converted Fedora Core 3 VM on ESX3.02
On a VMware ESX 3.02 we are trying to migrate a Linux Ferdora Core 3 that is running today in an old machine. We used cold convert an a VM was created on the ESX server, without any warnings. When we try loading the boot process failes:
,,,,
root (hd0,0)
Fileseystem type is ext2fs, partition type 0x83
kernel /bbot/vmlinuz-2.6.9-1.667 ro root-LABEL=/ rhgb quiet
[Linux-bzImage, setup=0x1400, size-0x155da5]
initrd /boot/initrd-2.6.9-1.667.o mg
[Linux-initrd@0x1fe7f000,0 x60d2c bytes]
uncomperssin linux ...ok booting the kernel.
PCI: Cannot allocate resource region 4 of device 0000:00:07.1
audit (1192753282.970:00:initial ized
Red Hat nash version 4.1.18 starting
mkrootdev:label / not found
mount:error 2 mounting ext3
mount eror 2 mounting none
switchroot : mount failed :22
unmount /initrd/dev failed:2
kernel panic - not syncing : Attempted to kill init!
,,,,
root (hd0,0)
Fileseystem type is ext2fs, partition type 0x83
kernel /bbot/vmlinuz-2.6.9-1.667 ro root-LABEL=/ rhgb quiet
[Linux-bzImage, setup=0x1400, size-0x155da5]
initrd /boot/initrd-2.6.9-1.667.o
[Linux-initrd@0x1fe7f000,0
uncomperssin linux ...ok booting the kernel.
PCI: Cannot allocate resource region 4 of device 0000:00:07.1
audit (1192753282.970:00:initial
Red Hat nash version 4.1.18 starting
mkrootdev:label / not found
mount:error 2 mounting ext3
mount eror 2 mounting none
switchroot : mount failed :22
unmount /initrd/dev failed:2
kernel panic - not syncing : Attempted to kill init!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I wonder if that information was lost when you cloned it to a vmware image?
This should be a very easy fix. Just boot the virtual machine from a rescue disk, take a note of what partitions are really the root, boot, etc.. (/dev/sda1, /dev/sda2, etc...) and edit /etc/fstab and put the actual locations in there. You also need to edit your grub.conf on your boot drive, it probably has something like root=LABEL=/, change it to root=/dev/sda1 or whatever your root is.
That or re-create the labels, but I'd try pointing at them directly first.