Chia Sẽ Kinh Nghiệm Về IT

Tìm Kiếm Với Google

Gởi Ðề Tài Mới  Gửi trả lời
Công Cụ Xếp Bài
Tuổi 12-07-2017, 11:23 AM   #1
Trả Lời: n/a
Fix lỗi : The content ID of the parent virtual disk does not match the corresponding
The content ID of the parent virtual disk does not match the corresponding parent content ID in the child.

Nếu bạn gập lỗi tương tự thế này thì tham khảo bài hướng dẫn sau để fix nhe

Recently I have worked again and again on the following issue:

Cannot open the disk '/vmfs/volumes/4a496b4g-eceda1-19-542b-000cfc0097g5/virtualmachine/virtualmachine-000002.vmdk' or one of the snapshot disks it depends on.
Reason: The parent virtual disk has been modified since the child was created.

My customer was not able to power on a virtual machine. As mentioned in the following KB: Content ID mismatch conditions are triggered by interruptions to major virtual machine migrations such as Storage vMotion or Migration, VMware software error, or user action.
The Content ID (CID) value of a virtual machine disk descriptor file aids in the goal of ensuring content in a parent virtual disk file, such as a flat or base disk, is retained in a consistent state. The child delta disks that derive from that base disk's snapshot contain all further writes and changes. These changes depend on the source disk to remain intact.
Depends on snapshot size, there are 2 ways to solve (power on VM) problem.

Cách Fix:

Giải pháp 1:

  1. Vào thư mục chứa VM xem và search trong file vmware.log tìm
  2. Log in to ESXi via SSH and change directory to the /vmfs/volumes/datastore_name/VM
  1. Log in to ESXi via SSH and change directory to the /vmfs/volumes/datastore_name/VM.
  2. Open vmdk file via vi editor. Please press "i" and move to the parentCID line.
  3. Correct the CID by changing the parentCID line value (after "=").
  4. Save changes and close the file via pressing "ESC" and ":wq!". Enter...
Important: If the VM consists of multiple virtual disks, probably you have to repeat the steps for the other .vmdk files. Please try power on VM. If still the problem exists, follow steps 1-5 again.
Solution nr 2 (snapshots with 0 bytes) is to modify VM hard disk to point a parent virtual disk file by doing the following steps:
  1. Locate a parent virtual disk file (Browse datastore and VM folder):In my case the parent virtual disk file is AvayaApp1Cen-t.vmdk and snapshots: AvayaApp1Cen-t-000001.vmdk, AvayaApp1Cen-
  2. t-000002.vmdk.

  1. Remove a Virtual Disk from a Virtual Machine. In my case I need to remove (without deleting from disk) AvayaApp1Cen-t-000002.vmdk.
  2. Add an Existing Virtual Disk to a Virtual Machine. In my case
  3. AvayaApp1Cen-t.vmdk.
  4. After browsking and adding disk, click OK to save changes.
  5. If you receive the following warning you need to consolidate files (snapshots): To consolidate the files, right-click the virtual machine and select Snapshot > Consolidate.
  6. Power on VM.

If Solution 1 or 2 does not help or VM behavior is not normal after power on, probably you will have to restore the VM from backup.

Tham khảo:

  Trả lời ngay kèm theo trích dẫn này
Gửi trả lời

Công Cụ
Xếp Bài

Quyền Hạn Của Bạn
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is Mở
Hình Cảm xúc đang Mở
[IMG] đang Mở
Mã HTML đang Tắt

Bây giờ là 05:07 PM. Giờ GMT +7

Diễn đàn tin học QuantriNet |
Founded by Trương Văn Phương | Developed by QuantriNet's members.
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.