Problem: Some or all replication jobs are failing due to the following error:
Vixd mount failed for device
Cause: The cause for this error can be one of the following:
- Amount of memory assigned to the AVM was modified which in turn causes SCSI controllers to disappear due to no disks assigned to them.
- VMDK being protected is an independent-persistent disk.
- The AVM and protected device(s) are on datastores that have different block sizes and/or VMFS versions.
Solution for Cause 1
The user should following the instructions described in the Adding a SCSI controller to the virtual machine article.
The steps are as follows:
- Right-click the AVM virtual machine in VMware vSphere and click the Edit Settings option.
- In the Virtual Machines Properties screen, click the Add… button and create the required SCSI controllers.
- Once the SCSI controllers have been created, click the Add… button again and create the same number of new hard disks. Assign a disk to each of the new SCSI controllers created in Step 2.
- The SCSI controllers should now be successfully added back to the AVM virtual machine. At this point, it is safe to remove the disks that were added in Step 3.
Solution for Cause 2
Axcient Fusion does not currently support protection of a VMDK that is an indepdenant-persistent disk. The user will need to reconfigure the disk to a persistent disk in order for Axcient Fusion to be able to protect it.
Solution for Cause 3
If the AVM and the protected device(s) are on different datastores, these datastores must have the same block size and VMFS version. If replication jobs are failing due to incompatible datastores, the user will need to either make these two datastores compatible or migrate the AVM or protected device(s) to the same datastore.