Aller au contenu principal

Failed to open raw hard disk data file '[datastore1] <Task_name>/<VM_name>.vmdk'.

Thread needs solution

vmProtect 8 virtual appliance deployed into a ESXI host with 2 VMs.

Occasionally 2 VMs failed to backup with the errors in attached file. Usually backup can be completed successfully again by rebooting the vmProtect 8 Appliance.However, this is a passive problem solving as in rebooting vmProtect appliance whenever error encountered.

Appreciate any permanent solution for these errors. Will Vmprotect 9 resolve this problem?
Any explanation for the errors?

Failed to open raw hard disk data file '[datastore1] QSSSGUAIWD001.qss-safety.com/QSSSGUAIWD001.qss-safety.com.vmdk'.
Additional info:
--------------------
Error code: 94
Module: 83
LineInfo: 1b5da992938b2ae1
Fields:
Message: Failed to open raw hard disk data file '[datastore1] QSSSGUAIWD001.qss-safety.com/QSSSGUAIWD001.qss-safety.com.vmdk'.
--------------------
Error code: 64
Module: 83
LineInfo: 7feed46a356d56b9
Fields:
Message: Failed to add SCSI disk to the system. Host: 3; Target: 1.
--------------------
Error code: 64
Module: 83
LineInfo: 7feed46a356d56b0
Fields:
Message: Cannot find attached hard disks in the system.
--------------------

==================================================================
The operation 'Backing up' has failed.
Additional info:
--------------------
Error code: 26
Module: 100
LineInfo: 48afbd3608a410ca
Fields:
Message: The operation 'Backing up' has failed.
--------------------
Error code: 1080
Module: 1
LineInfo: 145a191bfe9050d1
Fields:
Message: Failed to execute the operation.
--------------------
Error code: 1005
Module: 1
LineInfo: bb03ce40e9a37f1a
Fields:
Message: Cannot find any disk or volumes to back up. The operation has been terminated.
--------------------
=====================================================================
Task 'QSSSGUAIWD001' failed: 'Failed to create a backup.
Additional info:
--------------------
Error code: 3
Module: 435
LineInfo: 555b5abba09501ce
Fields:
Message: Failed to create a backup.
--------------------
Error code: 32786
Module: 114
LineInfo: 28314c961de7d32e
Fields:
Message: Failed to prepare for backing up.
--------------------
Error code: 353
Module: 149
LineInfo: a71592046cb2c5f6
Fields:
Message: Failed to back up the group.
--------------------
Error code: 2
Module: 218
LineInfo: 338a407ad20e0987
Fields:
Message: Error occurred while running the backup and recovery engine.
--------------------
Error code: 1080
Module: 1
LineInfo: 145a191bfe9050d1
Fields:
Message: Failed to execute the operation.
--------------------
Error code: 1005
Module: 1
LineInfo: bb03ce40e9a37f1a
Fields:
Message: Cannot find any disk or volumes to back up. The operation has been terminated.
--------------------'.

Fichier attaché Taille
vmprotect_error_20130828.docx 197.98 Ko
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Ivan,

The root cause here is that there are some traces left on post-backup stage which prevent new disk-attach to the appliance and this results in the following errors:

"Failed to add SCSI disk to the system. Host: 3; Target: 1."
"Local system has no more disks of type '3'."

The problem here is that the mounting (virtual disk attach event) traces are left in the Linux environment (vmProtect appliance) and therefore new mount attempts fail. We have fixed most of such symptoms in the 9th version by migrating to a newer Linux kernel version so it definitely makes sense to upgrade.

If the problem still persists then it would be really helpful to track down the history of the backups, i.e. capture the log which contains both previous successful backup attempt and the last failed one (since there should be some events in between which explain why the system came to this state). View->Show Logs->Save All To File will capture all these.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager