XSIBackup-Classic / Discussion / General Discussion: ERROR: No origin disk found...

premax - 2016-02-16

Hello

I've been trying to make a backup of one of my VMs running on esxi 6.0 host. I've been getting the following error each time after several hours of backup operation:

Complete backup elapsed time: 182 min ERRORS&WARNINGS: Sun Feb 14 23:12:11 UTC 2016 - Exit code: 33 ERROR: No origin disk found at: /vmfs/volumes/53b5649f-18a451fc-629c-10604bae8dc8/bialyvm1/bialyvm1.vmdk

I did some research and find out that this volume id belongs to a virtual drive that no longer exists and had been removed months ago. I also found out that the drive is still listed in vmx file:

scsi0:0.deviceType = "scsi-hardDisk" scsi0:0.fileName = "bialyvm1.vmdk" scsi0:0.present = "FALSE"

Please note that "present" is set to "FALSE".

Is this is a bug that XSIBackup tries to backup a disk, that is no longer present?

Last edit: premax 2016-02-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

premax - 2016-02-16

PS running esxi 6.0 and xsibackup 4.7.1

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

33HOPS - 2016-02-17

XSIBackup is not able to skip the disk based on the .present = "FALSE" flag, so you can:

1 - Remove those lines for the -not present- disk.
2 - Comment those lines using the # character.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Hi,
I get the same error message. It also seems to be related to a drive, which doesn't exist, but I cannot find anything in the vmx file.

Available room in device /vmfs/volumes/Backup/vmware before backup: 953 Gb.
Needed room in device /vmfs/volumes/Backup/vmware for backup: 128 Gb.

VM Name State   Size    Stop    Copy    Start   Time (min)  Speed (mb/s)
SBS 2011    ON  128G    NO (hot backup) KO! -   2   1024
Last error for the above VM:

No origin disk found at: /vmfs/volumes/53c7da76-77199518-3ac0-d050991b6417/SBS 2011/SBS 2011-000002.vmdk for VM: Windows XP

What I don't understand is "for VM: Windows XP".

I do have another VM called "Windows XP" but the backup runs on the VM "SBS 2011". I wonder where the ..002.vmdk drive could come from. I cannot find it in any vmx files.

DEBUG INFORMATION:

• backuppoint: /vmfs/volumes/Backup/vmware
• backuptype: custom
• backupvms: SBS 2011
• mailfrom: administrator@XXX.XX
• mailto: XX@XXX.XX
• smtpsrv: sbs.XXX.XX
• smtpport: 25
• smtpusr: administrator
• debuginfo: yes
• DATE DIR: 
• XSIDIR: /vmfs/volumes/datastore1/xsi-dir
• LAUNCHED BY: user
• KEY: -o StrictHostKeyChecking=no -i /vmfs/volumes/datastore1/xsi-dir/xsibackup_id_rsa
• PID: 7592395
• ESXi VERSION: 5.5.0
• Wed Jun 29 15:37:24 UTC 2016 - Exit code: 33
ERROR: No origin disk found at: /vmfs/volumes/53c7da76-77199518-3ac0-d050991b6417/SBS 2011/SBS 2011-000002.vmdk

Any thoughts?

33HOPS - 2016-06-30

Your .vmx file could be messed up for many reasons, just make sure that the disks at which it points are the right ones. Read this:

http://33hops.com/xsibackup-restore-vmware-virtual-machines.html

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom - 2016-07-04

I think I might have found the issue, but I don't know how to solve it :-( (yet)
It appears to be related to the edit/backup file of vmx, the "vmx~" file.

According to different sources, the "vmx~" file is created, if you edit the original vmx file during runtime, or generally, if any change to the vmx is required, but the machine is running. After shutdown, the content supposed to be merged.

Well, I don't edit or cause any changes to the "vmx" file. It is actually created as soon as the machine is powered on. If it's tunred off, the file is gone.
If xsibackup is running, wihtin the "vmx~" file, there is a new vmdk storage appearing, which replaces the original one, e.g. SBS.vmdk is replace with SBS001.vmdk. Then, xsibackup fails, because SBS001.vmdk doesn't acually exist.

I now wonder ...
why is the "vmx~" is created, as soon as the vm is powered on?
why is xsibackup using the backup file ("vmx~") - can I limit xsibackup to the 'original' vmx file?

Thanks!

Last edit: Tom 2016-07-04

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

33HOPS - 2016-07-04

Don't worry about that file, XSIBackup does not edit the original .vmx file. You just should make sure your VM layout is correct:

Turn off your VM.

List all disks in the .vmx file "cat /path/to/yourfile.vmx | grep .vmdk"

Make sure they are the desired .vmdk files and that they do exist in the configured paths. If not edit the .vmx file and correct whatever is wrong.

That's all, your VM should run and nothing is going to change your .vmx file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom - 2016-07-04

Hm, I struggle as it still doesn't work. Do my observations make any sense to you:

1) power-off and xsibackup running
"SBS 2011.vmx" [the listed file 'SBS 2011.vmdk' is correct]

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

"SBS 2011.vmx~"

doesn't exist
xsibackup

success (=cold backup)

2) power-on
"SBS 2011.vmx"

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

"SBS 2011.vmx~"

cat "SBS 2011.vmx~" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

3) power-on and xsibackup running [while trying to create snapshot]
"SBS 2011.vmx"

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

"SBS 2011.vmx~"

cat "SBS 2011.vmx~" | grep .vmdk scsi0:0.fileName = "SBS 2011-000001.vmdk"

xsibackup

error: No origin disk found at: /vmfs/volumes/53c7da76-77199518-3ac0-d050991b6417/SBS 2011/SBS 2011-000002.vmdk for VM: Windows XP

4) power-on and xsibackup just finished/ not running anymore
"SBS 2011.vmx"

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

"SBS 2011.vmx~"

cat "SBS 2011.vmx~" | grep .vmdk scsi0:0.fileName = "SBS 2011-000002.vmdk"

5) power-on and [vim-cmd vmsvc/snapshot.create 39 xsibackup "XSIBackup snapshot" 1 1]
"SBS 2011.vmx"

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011-000001.vmdk"

"SBS 2011.vmx~"

cat "SBS 2011.vmx~" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

snapshot create (from command-line)

create VM snapshot: success

It appears that creating a snapshop from the command-line works fine, but it doesn't work through xsibackup.

Any ideas what I should try/verify?
Thanks again!

Last edit: Tom 2016-07-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Tom - 2016-07-08

There is only one disk in the vm:

cat "SBS 2011.vmx" | grep .vmdk scsi0:0.fileName = "SBS 2011.vmdk"

but still, I get this error:

xsibackup * error: No origin disk found at: /vmfs/volumes/53c7da76-77199518-3ac0-d050991b6417/SBS 2011/SBS 2011-000002.vmdk for VM: Windows XP

any help / thoughts / hints appreciated :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

33HOPS - 2016-07-08

I don't know what to tell you. In such a simple scenario XSIBackup cannot fail, if the VM layout is correct.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

I think I have found the issue:

in line 1743 (et. seq.):

sm=" 0"                                                   
else                                                             
sm=" 1"

changed it to

sm="0"                                                   
else                                                             
sm="1"

and it works.

I would't have thought, that the space-character makes a difference (here), but it seems it does. At least in my installation (VM 5.5).

Strange enought: if I run the affected command from the command line, the space-character doesn't make a difference:

[xsibackup:1751] vim-cmd vmsvc/snapshot.create $1 xsibackup "XSIBackup snapshot" $sm 1

[OK] vim-cmd vmsvc/snapshot.create 39 xsibackup "XSIBackup snapshot"  1 1
[OK] vim-cmd vmsvc/snapshot.create 39 xsibackup "XSIBackup snapshot" 1 1

Well, xsibackup works now on my installation (again) ... :-)

[xsibackup-free: 5.1.6]
[VMware ESXi: 5.5.0]

Last edit: Tom 2016-07-09

33HOPS - 2016-07-10

I'm glad to know that you found the cause. That variable is a string and the space is there to make sure the value is parsed as such. In any case we'll review this part to improve it if possible. We have tested XSIBackup in ESXi 5.5 without issues regarding this part, so check the block of code right below where

vim-cmd vmsvc/snapshot.

create is called, as the origin of the problem could be there for you. Also, always make sure that you have VMWare Tools installed.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

ERROR: No origin disk found...

Local and over IP backups for ©VMWare ©ESXi 5.1 to 6.7

Forums

Help

ERROR: No origin disk found...

ERROR: No origin disk found...

Local and over IP backups for ©VMWare ©ESXi 5.1 to 6.7

Forums

Help

ERROR: No origin disk found... document.SUBSCRIPTION_OPTIONS = { "thing": "topic", "subscribed": false, "url": "subscribe", "icon": { "css": "fa fa-envelope-o" } };

ERROR: No origin disk found...