[dnanian]

We're not aware of any problems in this area. It's possible that your kernel extension cache -- once built -- was retained on your second copy, and this allowed the system to boot due to some weird peculiarity of your particular configuration, but you didn't indicate how you moved it, so it's hard for me to say.

If you moved it and retained the kextcache, try creating a copy script that doesn't ignore this file. This is something that shouldn't be retained, especially when a backup might move to new hardware, but in your case retaining it might not do any damage, and could explain what you're seeing.