Workstation 15 Pro
Windows 10 Host
No Snapshots
I have been going through all the similar issues on this forum and there are similar questions but My VM has two hard disks and one of the disks is based on an NFS.
Attempts tried so far:
I cloned the vm, it boots to initramfs, not sure if 2nd hard disk is cloned.
I have created new VM and pointed to the existing vmdk, boots to initramfs
I have deleted the lck folders, no joy.
I have tried ovf export, but no joy in ESXi.
I have tried vmplayer, no joy.
Most other options will not work due to the file being locked.
I have a eve-ng vm running for a few months and no issues.
I have two hard disks (1st local SSD drive 150GB e:, 2nd 150GB NFS which was added few weeks ago)
I have been using this VM daily with no issues and after missing one day, problems.
I have attached the logs, the vmx, vmxf, vmsd and the vmdk of the 2nd hard drive.
If you need any further information, please let me know.
Appreciate any help that can be offered.
The VM's configuration (.vmx) file, and the vmware.log file show diffetent virtual disks!?
The vmware.log contains:
scsi0:0.fileName = "EVE-2019.vmdk"
scsi0:1.fileName = "\\Rdn_nas01\NFS_3_NC\EVE-2019\EVE-2019-0.vmdk"
The .vmx file however shows the same virtual disk file twice, which is likely causing the error.
scsi0:0.fileName = "EVE-2019.vmdk"
scsi0:1.fileName = "EVE-2019.vmdk"
Either fix the configuration, so that each virtual disk points to its own .vmdk file, or remove the "scsi0:1" lines from the .vmx file.
André
> and one of the disks is based on an NFS.
Workstation is very picky about the filesystems used to store the VMDKs.
Avoid anything other than plain uncompressed NTFS.
I assume that the NFS is the problem here - copy the vmdk to a local NTFS and the problem will probably go away.
The VM's configuration (.vmx) file, and the vmware.log file show diffetent virtual disks!?
The vmware.log contains:
scsi0:0.fileName = "EVE-2019.vmdk"
scsi0:1.fileName = "\\Rdn_nas01\NFS_3_NC\EVE-2019\EVE-2019-0.vmdk"
The .vmx file however shows the same virtual disk file twice, which is likely causing the error.
scsi0:0.fileName = "EVE-2019.vmdk"
scsi0:1.fileName = "EVE-2019.vmdk"
Either fix the configuration, so that each virtual disk points to its own .vmdk file, or remove the "scsi0:1" lines from the .vmx file.
André
.... oops
Thankyou, Thankyou, Thankyou,
Lesson learned, I have backed up all the configurations and diagram schemas.
Your suggestion saved me 2 days rebuilding my lab system.
I moved the second vmdk from the NFS to the local SSD drive and changed the second drive to scsi0:1.fileName = "EVE-2019-0.vmdk"
The system works.
Thankyou to everyone who provided a response.