Shulou(Shulou.com)06/02 Report--

Notes for each file under the virtual machine:

Turn on the virtual machine after a shutdown and report an error:

Unable to enumerate all disks cannot find the disk

For losing the .vmdk descriptor file when there is no snapshot:

The disk file listed in the data storage browser is the basic disk file of the virtual machine is-flat.vmdk

Recreate the vmdk descriptor file:

1. Determine the size of the flat.vmdk underlying disk file (in bytes)

two。 Create a new empty pseudo disk of the same size as flat.vmdk.

3. Rename the descriptor file of the newly created .vmdk disk to match the name of the original virtual disk

4. Modify the contents of the renamed descriptor file to reference the flat file.

5. Remove temporary flat files left over from the newly created disk.

SSH log in to ESXI to enter the data storage directory:

Cd / vmfs/volumes/5dd90fdc-2ceecbae-b595-801844eed08a/cl-win7

Create a new virtual disk of the same size as the missing descriptor file:-c: specify the file size

Vmkfstools-c 214748364800-a lsilogic-d thin temp.vmdk

Delete the newly created underlying disk and keep the new descriptor file:

Rm-I temp-flat.vmdk

Rename the new descriptor file to the missing virtual disk:

Edit the new descriptor file to point to the underlying virtual disk file: vi cl-win7_4.vmdk

Note: if the original .vmdk is not a thin disk, find the line ddb.thinProvisioned = "1" and remove it.

Check disk chain status: return to normal

Vmkfstools-e cl-win7_4.vmdk

Power on normally:

For missing .vmdk descriptor files when there is a snapshot:

Unable to power on, unable to restore snapshot:

I took two snapshots here, so there are two incremental disk files:

02-sesparse.vmdk is based on incremental snapshots made by 01-sesparse.vmdk, and 01-sesparse.vmdk is based on increments made by basic disks of-flat.vmdk, forming a complete disk chain.

First detect the disk chain from the most recent snapshot file: (the largest sequence number is the snapshot incremental disk file in use)

Vmkfstools-e cl-win7_4-000002.vmdk

You can see that the 02.vmdk return message shows that the 02.vmdk check is normal and the 01.vmdk disk chain is inconsistent.

Continue to check 01.vmdk and find that only the incremental disk file cl-win7_4-000001-sesparse.vmdk is found, and the disk descriptor file is missing. Let's rebuild a disk descriptor file for the incremental disk:

Copy a template from the underlying disk descriptor:

Cp cl-win7_4.vmdk cl-win7_4-000001.vmdk

Modify the CID and parentCID,createType of cl-win7_4-000001.vmdk, delete the blank line, and add a parent vmdk file:

CID can be read from the lower layer of the missing file with multi-level snapshots

For example, what I have lost here is 1.vmdk. I read the parent layer CID from 2.vmdk, that is, the parent CID of 1.VMDK 's CID,1.VMDK is the CID of the underlying descriptor.

Finally save the changes and finally test the integrity of the disk chain:

Vmkfstools-e cl-win7_4-000002.vmdk

If the test is normal, you can turn it on normally.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.