Unable to boot ScopTel on Hyper-V after installation


After the installation is complete, the virtual machine reboot and crashes with a Kernel Panic during the loading process.



 Scanning logical volumes

Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
Creating root device.
Mounting root filessystem.
mount: could not find filesystem '/dev/root'
Setting up other filessystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!



Add the original ScopTel ISO, as a DVD drive in Hyper-V.

Boot the Hyper-V system, and at the boot prompt, type “linux rescue”.

Follow the prompts to mount the existing ScopTel installation, and get to the shell.

Run the following command to make the installed system the root (/) environment:

chroot /mnt/sysimage



View the contents of the /etc/grub.conf file to note the exact version of the installed kernel, which will be used in the next command:

cat /etc/grub.conf



Run the following command, replacing “VERSION” with the version you noted from the output of the grub.conf file:

mkinitrd /boot/initrd-VERSION.el5.img VERSION.el5 --preload hv_storvsc 
--preload hv_vmbus --preload hv_utils -f


For example, if the grub.conf file noted that the kernel was “/vmlinux-2.6.18-348.12.1.el5,” the version number is 2.6.18-348.12.1. The mkinitrd command would then be the following:

mkinitrd /boot/initrd-2.6.18-348.12.1.el5.img 2.6.18-348.12.1.el5 --preload hv_storvsc 
--preload hv_vmbus --preload hv_utils -f

Type “exit” twice to reboot, and your system should boot normally