Hi there,
Initial setup was consists of Dell server, storage and switches.
System was working fine. Due to system maintenance, Dell switches were replaced by Cisco switch.
During the maintenance work, server & storage were not touched, but switches are removed & replaced then system was working normally.
Due to maintenance work rebooted servers. Then virtual machine cant recognize datastore.
Now, we are experiencing below error message and log.
Attachments: error screenshots, log
Many thanks to anyone who can assist.
I've attached the "FileServer-000001.vmdk", in which I changed the parentCID to mach the parent virtual disk's CID.
After uploading the file to the datastore, I'd recommend that you reload the VM by running the commands in step 2 and 3 of Reloading a vmx file without removing the virtual machine from inventory (1026043) | VMware KB to ensure that the modified file is being re-read.
Please note that a broken snapshot chain often causes some file system corruption within the guest OS, so ensure that you have a backup, or at least create another temporary snapshot prior to powering on the VM so that the current .vmdk files are not being modified.
André
Welcome to the Commuity,
according to the .log file you posted, "FileServer-000001.vmdk" is attached to "DC-Summit.mn-Slave"!?
To me it seems that the same virtual disk is attached to two VM's. On "DC-Summit.mn-Slave" it's the snapshot disk, which is the active one, and on the "FileServer" VM it's likely the base disk. If this is the case, powering on the "FileServer" VM caused the issue with the broken snapshot chain.
Although it is easy - from a technical point of view - to fix the snapshot chain (you may however see file system errors in the guest OS), it is necessary to understand how the VMs are supposed to be configured regarding their attached virtual disks.
André
Hi Dear,
Thank you for your response.
Yes, your right., Fileserver is a virtual machine that has two virtual disks. One is system disk, another one is main file disk (i think my main disk is FileServer-000001.vmdk). I have add existing virtual disk and selected "FileServer-000001.vmdk" file but content ID mismatch. .
About the "DC-Summit.mn-Slave" it's just i have attached "FileServer-000001.vmdk" for testing purpose. But problem was same.
Please kindly see the attachments.
Please download the following files from the datastore, compress/zip them, and attach the resulting .zip archive to a reply post.
Note that each virtual disk consists of two .vmdk files (although only one shows up in the datastore browser). What I need is only the small descriptor .vmdk file, i.e. not the flat or delta .vmdk files. To download the two mentioned .vmdk files, enable SSH on the host, and then use e.g. WinSCP to connect to it, and download the files from the /vmfs/volumes/Office_FileShared/FileServer folder.
André
I've attached the "FileServer-000001.vmdk", in which I changed the parentCID to mach the parent virtual disk's CID.
After uploading the file to the datastore, I'd recommend that you reload the VM by running the commands in step 2 and 3 of Reloading a vmx file without removing the virtual machine from inventory (1026043) | VMware KB to ensure that the modified file is being re-read.
Please note that a broken snapshot chain often causes some file system corruption within the guest OS, so ensure that you have a backup, or at least create another temporary snapshot prior to powering on the VM so that the current .vmdk files are not being modified.
André
André ur really awesome
Thanks a lot for your help.
Problem solved.