Thanks you Oliver!
Posts made by okynnor
Can't access NFS in XO
I am getting this error when trying to add a storage repository from XO in order to allow me to run backup-ng for the first time.
"Command failed: mount -t nfs 192.168.1.5:/VM_ISOs /run/xo-server/mounts/8ea70d00-9303-4044-a471-e2b87947de3a -o vers=3 mount.nfs: mounting 192.168.1.5:/VM_ISOs failed, reason given by server: No such file or directory"
I am using NFS as that's what XO suggested because I am using FreeNAS SMB. but is' version 1 smb enabled. not sure if that's the reason or not.
The directory Im using a directory that's open and thus no authentication is needed.
RE: Unable to start VMs
The server was just upgraded to 8.0.0!!
I tried to start them from xsconsole and XO to no avail.
The VMs are set to auto-start. This was no problem until now where only 3 VMs start but the remaining 5 do not.
when I run
xe vm-cd-eject --multiple
this is what I get:
[17:17 xenserver-idpiupet ~]# xe vm-cd-eject --multiple operation failed on 7991ecab-0275-8e3c-a044-352c949773e6: Operation could not be performed because the drive is empty vbd: e243e381-fe10-8c22-b7c5-27aad7a48f22 operation failed on 8912fdcb-d756-457d-d45f-27d9a894a1ed: Operation could not be performed because the drive is empty vbd: 768b001a-1b47-dd45-2012-e91161d65855
Unable to start VMs
some VMs do start but a bulk don't.
By sampling one of them, in the error logs, I get this message. Would appreciate assistance in what I am supposed to do. Nothing has changed and if someone shares why this happens with some and not with other VMs, I'd be very appreciative.
Why would a VDI go missing to begin?