Originally Posted by Asagath
Any idea how to solve it?
Yes. Do not make backups with direct copies. They are subject to all sorts of fluky errors which you do not discover until you try to restore. Instead make backups with rsynch, cp, tar, or similar programs which copy by file.
Possible problems with this particular restore could be:
Your partition table for the original disk may make no sense on the disk you are restoring to. Check this by booting a rescue CD and running:
Your file system structure may be corrupt on the the disk you are restoring to. If it was corrupt on the original then the direct copy faithfully reproduced the problem. If the file system was correct on the original then the difference in disk geometry between the 2 drives may mean that hard links now point to the wrong place. Check this by booting a rescue CD and running fsck against every partition on the restored drive.
The initrd may be someplace other than where the MBR thinks it is. You can check this by booting a rescue CD and reinstalling the boot loader on the restored drive. LILO tends to be more susceptible to this problem than GRUB.
Another possibility which has nothing to do with direct copy is that your initrd may not contain the correct modules in order to load your kernel. You may need an ide module in your initrd instead of a scsi module. Section 2 of this web page explains how to do that for Red Hat: