ESXi

Our host esxi4 runs two virtual machines. As I tried to make a second snapshot - with the help of the vsphere-client - of the debian-4-server the process stopped after a few seconds with the guest-os being switched off.

Meldung von esxi.bk4.local: Cannot open the disk

'/vmfs/volumes/4a770d15-f3c30b40-9704-0022154f-

f9eff/LML403/LML403_3-000001.vmdk' or one of the

snapshot disks it depends on. Reason: The file

specified is not a virtual disk.

Info

12.07.2010 16:02:48

root

As I tried to restart the guest-os I got the following message:

LML4 auf esxi.bk4.local kann nicht eingeschaltet werden: Ein allgemeiner

Systemfehler ist aufgetreten:

Fehler

12.07.2010 16:02:50

root

In english: The server can not be switched on. There has been an system-error.

It is also impossible to make a backup with the vmware-converter.

Thanks for any ideas

tux-online

How much free space do you have in on the VMFS datastore?

Please post the latest vmware.log, the LML403.vmsd, the LML403.vmx and a list of files in the VM's folder. A screeshot of the datastore window, showing names, sizes and time stamps will do.

André

Hallo Andre!

There should be enough space: There is over 900 GB of space while the debian server just needs 400 GB. I will post the log-files in about 10 days since the school is closed at the moment. I couldn´t find the log-files via vsphere-client, so I guess that I have to log in on the console of the esxi-server and copy the logs to an usb-drive?

Thanks

tuxonline

All the files can easily been downloaded from the datastore browser, you don't need to do anything on the CLI (yet).

The files are located in the VM's folder (from which I asked you to create the screenshot)

André

@DSTAVERT: Thanks for your post! I appreciate it.

@André

Broken disks require fewer cooks. You are a good cook.

Thanks for the moment, but as I mentioned before I don`t have access to the server due to holidays. I`ll post the log-files as soon as possible.

tuxonline

Hallo Andre!

I finally got the logs. Thanks so far.

tux-online

Attachment(s)

LML403.vmx   3 KB 1 version

vmware.log   33 KB 1 version

Hallo Andre!

Last but not least the screenshot of the datastore.

Greetings

tuxonline

I think the posted vmware.log is to new, here are some older ones.

Attachment(s)

vmware-32.log   33 KB 1 version

vmware-33.log   33 KB 1 version

vmware-31.log   33 KB 1 version

From what I can see, it appears the header/descriptor file "LML403_3-000001.vmdk" is broken (kaputt in German). The "LML403_3-000001-delta.vmdk" should not appear as a separate file in the datastore browser.

What I need are the header/descriptor files (just a few bytes in size) of the disk and its snapshot ("LML403_3.vmdk" and "LML403_3-000001.vmdk") to see what's wrong and help you repair it.

To get these, you need to access the ESXi host via "ssh" (winscp), because these files cannot be downloaded separately via datastore browser.

For how to enable SSH access on ESXi 4.0 see the upper part of http://www.vm-help.com/esx40i/ESXi_enable_SSH.php.

André

Hallo Andre!

You`re very fast! I created a package of log-files with the vsphere-client. I`m lucky, this package contains the required files.

Greetings

tuxonline

As you can see the contents of "LML403_3-000001.vmdk" are completely screwed up. Somehow they were overwritten. I've never seen something like that before!

At the moment I'm sitting at home and don't have access to a live system. Therefore I'd like you to attach the two files for another disk (e.g. "LML403_2.vmdk" and "LML403_2-000001.vmdk") , so I can derive the correct entries from them.

André

Hallo Andre!

I compared the content of LML403_3-000001.vmdk with that of similiar files, but they have nothing in common. As you wished I add some more files.

Some more files:

Thanks for the additional files. This made it easier for me to repair the broken file.

Now you have to upload it to the VM's folder. You should do this via CLI/winscp as I don't know what will happen when you try to upload it using the datastore browser.

After uploading the file, open the datastore browser. There you shouldn't see the delta file anymore.

Then right click the VM in the inventory, select "Remove from Inventory", right click the vmx file in the datastore browser and select "Add to inventory".

In "Edit settings" you should now see the correct disk size for the 3rd disk with the size grayed out (since it is a snapshot).

If everything is ok, you can either start the VM now or take another snapshot before starting it.

André

I`ll probably try the upload next week - I`m still on holiday. Is it also possible to use a linux live cd to import the new file? Where is the correct folder?

Thanks

tuxonline

Is it also possible to use a linux live cd to import the new file? Where is the correct folder?

I don't think a live CD will work, because the file has to be copied into the VM's folder on the VMFS datastore and the live CD will most likely not recognize VMFS partitions.

On the CLI you will find the folder at "/vmfs/volumes/<datastore-name>/LML403"

Waiting for your feedback next week.

André

... I just reproduced the issue on my ESX 4.0 test host.

Uploading the header vmdk file using the datastore browser works.

André

Thank you!

Hallo Andre!

I just uploaded your file and the vm starts, great! As I tried to make a backup with the vCenter-Converter I got the following error message:

Unable to obtain hardware information for the selected machine.

Do you have any idea? Thanks for the fantastic help so far!

tuxonline

You are welcome and thanks for the feedback.

For the converter issue you could try 2 things:

- Temporarily (for the conversion) change the selected Operating System in the VM's settings to e.g. Suse Linux

- Try Converter v3.0.3

André

Hallo Andre!

The vmware vCenter Converter Standalone Client has got the build number: 4.0.1 build-161434

Changing the operating system from "debian 32 bit" to "other linux 2.6 32 bit" helped.

Thanks again

tuxonline

ESXi 4.1 ?

Try to fix it

vmkfstools --fix check

Hallo Klou!

It´s esxi 4.0. I´ll try it next week - after the holidays.

Thanks

tuxonline

Hello, tuxonline1

Looks like in 4.0 there is no option --fix[/b]

In vSphere Client you can find logs clicking "Home">"System Logs"

You could try as suggested in this link?

http://www.ardamis.com/2009/11/20/vmware-cannot-open-the-disk-xxxxxx-vmdk-or-one-of-the-snapshot-disks-it-depends-on/

Don't try to fix anything. You risk loosing data if you go in a direction without understanding what the problem is. Follow through André's post. Provide the information he has asked for.