I have two systems, each one has its own Areca controller and associated array. One was running 4.1 and the other I upgraded to 5. I noticed that sometimes if I cloned a VM locally on the 5 system, the new clone would not boot. Then ZFS reported corruption of its root disk, which is a VMDK on this datastore. That's when I tried cloning a Windows 2K8 VM from the 4.1 system to the 5.0 system. When I clone to a SATA drive on the motherboard of the 5 system, it works fine. But when I clone to the Areca datastore, it won't boot. When I run the Windows repair, it tells me some dll has been corrupted and it can't be fixed. This happens every time I try it. Areca told me that they tested cloning on 5.0 and didn't have any trouble. They are claiming the driver in 4.1 and 5.0 is the same. The only difference is that compile it against 5.0. When I can take down my other server, I will put 5.0 on it via USB flash and then test clone in the reverse direction. (I downgraded the 5 system to 4.1.)
↧