Salta al contenuto principale

[RESOLVED] Error when backing up VM: Message: Local system has no more disks of type '3'.

Thread needs solution

We get the below on some VMs, we have rebooted the Acronis appliance and we confirm we have enough LUN space to create\delete a snapshot in VMWare ESX 4.0 Update 1. We have 300 GB free space on the LUN where the Acronis appliance resides. Why are we getting the below on only some VMs? Can an Acronis engineer tell me what the below means?

Failed to perform the requested operation.
Additional info:
--------------------
Error code: 13
Module: 149
LineInfo: d1ab7fa1e56ec76e
Fields:
Message: Failed to perform the requested operation.
--------------------
Error code: 236
Module: 16
LineInfo: 7bb42efe3c73323f
Fields:
Message: Internal error: Attempt to access emulated disk for non-initialized object.
--------------------
Error code: 94
Module: 83
LineInfo: 1b5da992938b2ab9
Fields:
Message: Failed to open raw hard disk data file '[LUN38] TST/TST.vmdk'.
--------------------
Error code: 179
Module: 83
LineInfo: 999b08030ac9fb1b
Fields:
Message: Local system has no more disks of type '3'.
--------------------

0 Users found this helpful

Hello Bruce,

Thank you for your post and welcome to the forum.

I am terribly sorry for the inconvenience, currently we are investigating this issue. Your case is being worked by a member of our Expert team.

Feel free to contact me directly if you require additional assistance.

Thank you.

hi, Anton
i have also faced this problem. Pls see below message

Backgroud
1 VMware is 5.0
2 We have three ESX hosts.
3. The licenes for ABR is upgraded from ABR10 to ABR 11
4. The AppNetwork IP series(172..**) is different to storage to SAN( this IP series is 192.***..........)
5. Added host in Vsphere Client by ESX host name, not IP.
6. ABR version used now is Build11.0. 17318
7. We have 3 sever license for virtual

i have checked the KB, it told me to update Builder.

or, if i do not want to update builder, check those following, but it still does not work.

Hope you give me some suggestion.
Or email to me :shiyao.sun@Honeywell.com

------------------------------------------------------------------------------------------
Failed to perform the requested operation.
Additional info:
--------------------
Error code: 13
Module: 149
LineInfo: d1ab7fa1e56ec76e
Fields:
Message: Failed to perform the requested operation.
--------------------
Error code: 236
Module: 16
LineInfo: 7bb42efe3c73323f
Fields:
Message: Internal error: Attempt to access emulated disk for non-initialized object.
--------------------
Error code: 23
Module: 83
LineInfo: c61573f663f5d8b1
Fields:
Message: Failed to get access to hard disk '[CDB-OTS-ESX02-share] ODP1-FOD01/ODP1-FOD01.vmdk'.
--------------------
Error code: 94
Module: 83
LineInfo: c61573f663f5d86b
Fields:
Message: Failed to open raw hard disk data file '[CDB-OTS-ESX02-share] ODP1-FOD01/ODP1-FOD01.vmdk'.
--------------------
Error code: 14009
Module: 0
LineInfo: c61573f663f5d74e
Fields:
Message: The server refused connection
--------------------

Hello sun shiyao,

Thank you for posting your question in our forum.

For your message I found this article in our knowledge base. Please review the offered solutions to solve your problem.

If there is anything else, we can do for you, please let me know.

Thank you.

hi, i have already checked following the guide from the link http://kb.acronis.com/content/24687

follwoing the below guide, but it does not work still.
To resolve the issue without installing the latest build, do the following:

1.Upgrade the virtual appliance hardware to the latest (7th) version using the Upgrade Virtual Hardware command in the vSphere Client;
2.If the virtual appliance has more than two disks, leave the first two disks and remove the rest from the Virtual Machine Properties dialog. Acronis Backup & Recovery 11 supports up to two disks in a virtual appliance;
3.Change the second SCSI controller type to lsi logic parallel. There should be one controller with the bus logic parallel type and one with the lsi logic parallel type;
4.Reboot the virtual appliance.

So i will follow solution 1 to upgrade ABR 11 to builder 17737 or higher. But at my accoount, the version is Chinese, and I need English Version. Pls help me to do so

Hello sun shiyao,

Thank you for your reply.

If you want to change the language, you need to contact support in this case. Please see instructions in this article from our knowledge base.

If there is anything else, we can do for you, please let me know.

Thank you.

All, we have already solved this problem. The reason is DNS wrong configuration.
In my system:
There is 1 Domain Controller, and 3 ESX host.
There is 1 Vcenter.(Application networ is 172.***)
There is 1 SAN (IP 192. ***)
Honestly to say, as beginnging, i added ESX host by its IP not name, that time, ABR 11 can work.
As requiredy by customer, all machines added should by its name, and I added hosts by its name. It begin not to work.

I continuous on un-install and re-insall, and even upgrade the builder from 17318 to 17440. It still does not work.

The main reason is Network configuration.

What i have done are following:
1. At VC, network/properties/(TCP/IPV4)/Properties/Advanced/ interfacte metric. Set VC' IP at application network to Rank top1.
Dependen on IP' imporatance, rank it.
Reason: if you configure Vcenter at AMS using VC' IP, there will be no problem. If used VC' name, the agent will fail to be deployed.
2. Add Host with its name at Vsphere client.( if you add host by its application IP, skip this)
configuration/DNS/Routing, configure host name, domain name, DNS server, and domains where host search for.
Most important
Add ESX host name and its application IP to Domain Controller policies.

Retry, it works.

Suggetion:
Acronis must update install guide carefully. Do not just let user name or IP. No one will know the reason.

Hope this will be helpful to those later faced this problem.

More, the acronis KB suggestion solutions
Solution1 to upgrade builder is not reasonable.

Solution2 does not have any little help to me

Hello sun shiyao,

Thank you for your reply.

As you have solved your issue, I will close this thread.

You can leave your comment at the end of each kb article. We read those feedbacks and if necessary, update the article with corrected information.

As your issue is now resolved, I lock this thread.

If there is anything else, we can do for you, please let me know.

Thank you.