VMware Cloud Community
hmontoliu
Contributor
Contributor
Jump to solution

Unable to obtain hardware information for the selected machine with vmware converter 5.5 (Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32))

Hello

I'm trying to do a P2V with vmware converter standalone 5.5

The source is the same machine that hosts vmware converter 5.5

The operating system is W2003 which acts as domain controller

Vmware-converter is launched by the administrator account.

The error I can see from the vmware-converter.worker logs is:

2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 info 'Default'] Found volume with name "\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:35.592+01:00 [04344 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:41.155+01:00 [04344 warning 'Default'] Warning: no attached disks were detected.
2014-02-13T17:36:41.155+01:00 [04344 error 'Default'] [LiveWindowsComputer] Unable to find any disks attached to the computer.
2014-02-13T17:36:41.170+01:00 [04344 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds
2014-02-13T17:36:41.170+01:00 [04344 error 'Default'] Unknown exception while invoking VMOMI method queryComputerInfo
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.358+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a0a1-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{18297536-8c0b-11da-8528-0014852d7e43}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{caf5e9f8-4e6c-11dd-b440-0014852d7e43}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{2958b89a-b562-11dc-a508-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a09f-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.389+01:00 [05648 info 'Default'] Found volume with name "\\?\Volume{0395a09e-8c42-11da-a7d7-806e6f6e6963}\"
2014-02-13T17:36:50.421+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.421+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.452+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive0: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.452+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive0'
2014-02-13T17:36:50.499+01:00 [05648 warning 'Default'] Failed to get capacity for \\.\PhysicalDrive1: error opening disk device: Unknown error 32 (0x20) (32)
2014-02-13T17:36:50.499+01:00 [05648 warning 'Default'] Skipping hard disk '\\.\PhysicalDrive1'
2014-02-13T17:36:56.155+01:00 [05648 warning 'Default'] Warning: no attached disks were detected.
2014-02-13T17:36:56.155+01:00 [05648 error 'Default'] [LiveWindowsComputer] Unable to find any disks attached to the computer.
2014-02-13T17:36:56.155+01:00 [05648 info 'Default'] Scheduled timer canceled, StopKeepAlive succeeds

This had happened before with another server (also W2003 DC) but which hardware was completely different; unfortunately I wasn't able to solve that time.

Any help or hints would be appreciated, thanks in advance

0 Kudos
1 Solution

Accepted Solutions
hmontoliu
Contributor
Contributor
Jump to solution

Thanks all for your help

I've finally found the guilty service.

It was pcmonitor a remote monitor/control software. Once I've stopped it's service vmware converter could get the capacity of the physical drives.

It's rather curious because I've done several P2V conversions of servers using this software (so far the last one was two weeks ago - the difference between that server and this one was that the former wasn't a DC).

Hope this thread will help others in the future. 

View solution in original post

0 Kudos
7 Replies
ivivanov
Expert
Expert
Jump to solution

The message for error 32 is "The process cannot access the file because it is being used by another process.". It looks to me as a permission error. Are you using the *local* administrator account, but not the domain admin account?

__________
It is worse!
patanassov
VMware Employee
VMware Employee
Jump to solution

Hello

I suppose you are aware that virtualizing domain controllers is a tricky thing. If not, you may want to have a look at VMware KB:     Virtualizing existing domain controllers in VMware vCenter Converter   , and probably other articles about that. Some people even recommend not converting, but rather installing a new DC and syncing it with the old one.

HTH

Plamen

0 Kudos
hmontoliu
Contributor
Contributor
Jump to solution

Thank Plamen you for your hint, however I believe that it is not the case.

I've already converted many DC before (either 2003 and 2008) w/o major issues.

The problem here is that the converter is unable to detect its own hardrives; the hard drives of the source machine, so the converter is not able even to create the converting task. The issue is not related to problems with the resulting VM.

0 Kudos
hmontoliu
Contributor
Contributor
Jump to solution

Thanks ivivanov for your answer.

I'll take a look to see if I find if there is a process blocking the disk access of the converter

Answering your question I'm using the domain administrator to launch the converter. Not sure If I can use the local administrator since lusrmgr.msc won't open in this DC

0 Kudos
hmontoliu
Contributor
Contributor
Jump to solution

Said that I can confirm that the domain user "administrator" is member of the localgroup "administrators"

0 Kudos
patanassov
VMware Employee
VMware Employee
Jump to solution

Yes, I know this is not the case. Just wanted to draw your attention to that.

For the specific error - check for antivirus, backup software, or anything else that could open and use the whole disk.

hmontoliu
Contributor
Contributor
Jump to solution

Thanks all for your help

I've finally found the guilty service.

It was pcmonitor a remote monitor/control software. Once I've stopped it's service vmware converter could get the capacity of the physical drives.

It's rather curious because I've done several P2V conversions of servers using this software (so far the last one was two weeks ago - the difference between that server and this one was that the former wasn't a DC).

Hope this thread will help others in the future. 

0 Kudos