VMware Cloud Community
Karrye
Contributor
Contributor

Virtual Machine Clone: @&!*@*@(msg.fileio.generic)Error

Hi,

We have a C# script cloning all our virtual machines to a backup store using PowerCLI (for .NET). We are using the latest 5.1 release of the PowerCLI client.

Setup: vCenter 5.1, one ESXi 5.1 node and one ESXi 4.1 node.

Guest machines are running a range of Windows 2003, Windows 2008 R2, Windows 2012, FreeBSD and Ubuntu.

When the script is making a clone, the process will run to 99% and then return the following error.

The error is also visible in the vSphere client "recent tasks" window.

A general system error occurred: @&!*@*@(msg.fileio.generic)Error

Any idea what this means?

Best regards,

Christopher de Haas

Tags (3)
Reply
0 Kudos
5 Replies
irfans123
Enthusiast
Enthusiast

Cause

This error is actually thrown by the VMware Virtual Center (attempting a  manual snapshot of the VM through the VMWare client will also render  the error). It indicates the Datastore storage for the particular VM(s)  involved are inaccessible to the VMware Host(s). The most common cause  of the issue is bad (dead) SAN-pathing to back-end SAN storage that  houses the particular datastore(s).

Resolution

Check the SAN paths/hardware for defects, correct as needed. Once the  storage is operating properly, the error message should disappe

Reply
0 Kudos
Ethan44
Enthusiast
Enthusiast

Hi Karrye

Hope doing great .

could you please share that script?

"a journey of a thousand miles starts with a single step"
Reply
0 Kudos
Karrye
Contributor
Contributor

Hi, Thank you very much for your answer.

I have looked at the SAN, but I cannot find any problems.

Also, I can clone a virtual machine to the backup SAN from the vSphere client without any issues.

Christopher

Reply
0 Kudos
Karrye
Contributor
Contributor

I will gladly make the script available once the issue have been resolved.

Reply
0 Kudos
davosplatzifx
Contributor
Contributor

Hi

I actually had this problem and the issue was related to insufficient space at the the datastore where the snapshot was trying to be reverted. As soon as we increased the free space, the task completed succesfully

Reply
0 Kudos