I have a SLES 11 SP4 machine that is a VM on a Hyper-V server. I shutdown the VM and exported a copy to a different host for testing purposes of some software.

On the new host, I have successfully imported the SLES VM, but when I turn it on I get disk errors such as:

fsck.ext3: No such file or directory while trying to open /dev/disk/by-id/scsi-14253465420202020b55afof5d356d04b9e0aa3747286fdfe-part7
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>

/etc/init.d/kbd: line 42: locale: command not found
/etc/init.d/kbd: line 234: find: command not found
Can not find a keymap for us.map.gz, trying fallback.
Loading keymap Loading /etc/defkeymap.map
no /usr/sbin -> Numlock off.
Stop Unicode mode.

fsck failed for at least one filesystem (not /)
Please repair manually and reboot.
The root file system is already mounted read-write.

Attention: Only CONTROL-D will reboot the system in this maintenance mode. shutdown or reboot will not work.
The original VM that I exported from runs and boots fine. Thoughts?