ESXi6: storage error when starting a Windows 7 image / deltadisks filesystem full

[FrankMunich]

Hi all,

I am using a ESXi 6.0 with latest patch on a HP ProLiant Microserver. Everything works perfectly except one Windows 7 Image I migrated from Microsoft Hyper-V.

I had first consolidated the disk files into one complete Image and then converted it to a .vmdk using WinImage.

Now when I start the Image, Windows 7 does boot up (starting Windows...) but then I am getting the error:

Meldung der virtuellen Maschine

Der Vorgang für die Datei '/vmfs/devices/deltadisks/4c5...W7EN-s001.vmdk' ist fehgeschlagen (14 (Bad Address)). Das Dateisystem, in dem sich die Festplatte '/vmfs/devices/deltadisks/4c5..W7EN-s001.vmdk' befindet, ist voll. Wählen Sie 'button.retry', um den Vorgang

zu wiederholen. Wählen Sie 'button.abort', um die Sitzung zu

The mentioned file does exist and the filesystem is of course not full. The error says the filesystem /vmfs/devices/deltadisks/ was full, but there are >600 GB free.

Any ideas what's happening here? What are these deltadisks?

[FrankMunich]

Nobody?

[a_p_]

According to the file name you didn't convert the VM to a supported file format for ESXi, but to one for e.g. VMware Workstation!? Depending on what you are using to view the files in the datastore, you will only see a single .vmdk file but not all the data files which make up the virtual disk. Please connect to the host's console (e.g. using putty), run ls -lisa in the VM's folder, and attach the command's output (i.e. the file list) to a reply post.

André

[FrankMunich]

Which Format should I use when converting? The original consolidated disk on HyperV is a .vhdx which I can convert to either .vhd or .vmdk. What is correct in this case?

The file was originally added as "W7EN.vmdk" having a size of around 35 GB. The original HyperV disk is of the same size (except a few Bytes) and works fine, so it must have all required data in it.

And, in fact, it does boot, so at least it recognizes the disk. If I need to do something different when converting the original .vhdx, suggestions are welcome.

The VMWare converter does not Support an online conversion of HyperV Images with that Version (HyperV under Windows 8.1 64 Bit), I tried that as well.

[root@ESXi6:/vmfs/volumes/5504c36b-d8a7a9d5-ecc4-38eaa7a49f0a/W7] ls -lisa

total 37458968

4225156      8 drwxr-xr-x    1 root     root          2100 Jun 17 21:13 .

      4   1024 drwxr-xr-t    1 root     root          1400 Jun 16 20:07 ..

88111236 1048576 -rw-------    1 root     root     1073741824 Jun 17 21:13 W7-06bdb0ad.vswp

46168196   1024 -rw-------    1 root     root          8684 Jun 17 21:14 W7.nvram

16808068      0 -rw-------    1 root     root           490 Jun 16 20:06 W7.vmdk

21002372      0 -rw-r--r--    1 root     root             0 Jun 16 20:06 W7.vmsd

8419460      8 -rwxr-xr-x    1 root     root          2150 Jun 17 21:13 W7.vmx

75528324      0 -rw-------    1 root     root             0 Jun 17 21:13 W7.vmx.lck

79722628      8 -rwxr-xr-x    1 root     root          2150 Jun 17 21:13 W7.vmx~

50362500 36210688 -rw-r--r--    1 root     root     37078761472 Jun 17 21:14 W7EN-s001.vmdk

92305540      0 -rw-------    1 root     root           425 Jun 17 21:13 W7EN.vmdk

37779588   1024 -rw-r--r--    1 root     root        252691 Jun 17 21:09 vmware-1.log

67139716   1024 -rw-r--r--    1 root     root        180356 Jun 17 21:11 vmware-2.log

83916932   1024 -rw-r--r--    1 root     root        187001 Jun 17 21:13 vmware.log

71334020 194560 -rw-------    1 root     root     199229440 Jun 17 21:13 vmx-W7-113094829-1.vswp

[root@ESXi6:/vmfs/volumes/5504c36b-d8a7a9d5-ecc4-38eaa7a49f0a/W7]

[FrankMunich]

The full error in the log is:

2015-06-17T21:22:12.393Z| vmx| I120: Timing out dialog 4288723

2015-06-17T21:22:12.393Z| vmx| I120: Vigor_MessageRevoke: message 'msg.vmxaiomgr.retryabort.diskfull' (seq 4288723) is revoked

2015-06-17T21:22:12.393Z| vmx| I120: MsgQuestion: msg.vmxaiomgr.retryabort.diskfull reply=0

2015-06-17T21:22:12.394Z| Worker#0| I120: FileIOErrno2Result: Unexpected errno=14, Bad address

2015-06-17T21:22:12.394Z| vmx| I120: VMXAIOMGR: Retry on write "/vmfs/devices/deltadisks/baa7f13-W7EN-s001.vmdk" : Bad address.

2015-06-17T21:22:12.394Z| vmx| I120: VMXAIOMGR: system : err=e0002 errCode=14 freeSpace=0

2015-06-17T21:22:12.394Z| vmx| I120: VMXAIOMGR: "/vmfs/devices/deltadisks/baa7f13-W7EN-s001.vmdk" : write s=1774452736 n=131072 ne=1, fai=0

2015-06-17T21:22:12.394Z| vmx| I120: VMXAIOMGR:             v[0]=5803F516000:131072

2015-06-17T21:22:12.394Z| vmx| I120: Msg_Question:

2015-06-17T21:22:12.394Z| vmx| I120: [msg.vmxaiomgr.retryabort.diskfull] The operation on the file "/vmfs/devices/deltadisks/baa7f13-W7EN-s001.vmdk" failed (Bad address).

2015-06-17T21:22:12.394Z| vmx| I120+ The file system where disk "/vmfs/devices/deltadisks/baa7f13-W7EN-s001.vmdk" resides is full.

2015-06-17T21:22:12.394Z| vmx| I120+ Select _Retry to attempt the operation again.

2015-06-17T21:22:12.394Z| vmx| I120+ Select Cancel to end the session.

2015-06-17T21:22:12.394Z| vmx| I120: ----------------------------------------

[a_p_ · Accepted solution]

Please attach the "W7EN.vmdk" file - which contains the virtual disk's format - to a reply post.

What I guess that needs to be done is that you need to use VMware Converter to convert the previously (with Winimage) converted disk to ESXi as the target. This will convert the spars (...-s001.vmdk) disk format to a supported one. If you only have the .vmdk file(s), you may want to temporarily create a VMware Workstation (or Player) VM with the converted virtual disk attached, and use this as the source for the Converter.

André

[FrankMunich]

You want me to attach a 35 GB file here? Are you serious? :smileyconfused:

However, thanks for the hint regarding VMWare Player. I installed that, created an image using the Hyper-V disk and am now converting it to ESXi directly.

I will report whether that gives a better result.

[a_p_]

You want me to attach a 35 GB file here? Are you serious?

92305540

0 -rw-------

1 root

root

425 Jun 17 21:13 W7EN.vmdk

According to the file list you posted, its size is only 425 bytes. Anyway, converting should work, so let's see what happens.

André

[FrankMunich]

You are correct, the file was smaller before I did some more tests. The files did change again after the last tests.

However, VMWare Player was SPOT ON! I created 2 VMWare Player Images using the Hyper-V disks and was then able to convert them online via VMWare Converter directly to ESXi - using free software only.

Both images now run perfectly without errors and I can also take snapshots without destroying the environment (which previously happened as well).

I don't know what ESXi does when using the Hyper-V images but it looks like they cannot be used 1:1.

It's all good and resolved, thank you!