P2V Problem with seeing hard drives

Posted on 2010-09-22
Last Modified: 2012-05-10
Hello, hope someone can help me with this problem.

I have two IBM H Series Blades both connected to the same IBM DS3400 SAN. I want to P2V both blades via VMWare P2V Converter Stand Alone v4.3. I have installed the P2C converter on both servers. Both servers have the same drive configuration - C:\ and D:\ are on one hard drive located in the blade and drive E:\ and F:\ are located on our SAN. When I begin configuring a new P2V task, I click the "View Source Details" link to view the server details including drives.

Blade 1 - when I launch a new conversion task, select the local machine, and click the blue link to "View Source Details", the converter sees all hard drives perfectly (Drives C:\ through F:\) and when I go through the P2V conversion process the task completes 100% without any errors at all. It is a wonderful experience!

Blade 2 - when I launch a new conversion task, select the local machine, and click the blue link to "View Source Details", the converter does not display the drives properly (Drives C:\ and D\: show up fine and F:\ drive shows up with and incorrect size and no D:\ shows up at all). If i follow through with the conversion completes with no errors however the drive configuration is incorrect.

The only difference between the Blades' E:\ and F:\ drives is the size on each blade.
Blade 1: E:\ Total Space 39.9GB In Use Space 24.1GB F:\ Total Space 29.9GB Used Space 24.1GB
Blade 2: E:\ Total Space 74.8BG In Use Space 37.2GB F:\ Total Space 69.9GB Used Space 69.6GB

Any help on this situation would be much appreciated.
Question by:arnold739
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
LVL 23

Expert Comment

by:Luciano Patrão
ID: 33734709

The controllers from both servers are the same?

What is the OS from both servers?

The SAN disks are the same type?

You can also P2V without the SAN disks, and then reattach that disks into the new VM


Author Comment

ID: 33734857
Thank you for the response.

Controllers and San Disks are identical - these are IBM Blade Servers in a H Series Blade Center connected with fiber connection to the same SAN. The blade servers are identical Windows 2003 R2 Servers, both running SQL Server. The drive configuration is::
Drive c:\ & D\: are the hard drive in the blades
Deive e:\ & f:\ are on the SAN

The converter showed all 4 drives perfectly and converted perfectly on the one blade and the problem I am having is the 2nd blade.

The problem is that on the 2nd blade, I cannot see all four disk drives when I first open the P2V Converter, select "Local Machine" and then click "view source details". So if I cannot see them at this preliminary stage, I cannot convert all drives whether together or separately.

Hope this answers your questions.

LVL 23

Expert Comment

by:Luciano Patrão
ID: 33734950

Its strange.

Since this is a SAN with fiber, like i said you can add after the SAN disks into the new VMs. You don't need to import this. And i do not recommend to migrate SAN disks.

Check my article and the SAN disks part. Here you can remove and reattach the SAN disks into the new VM as a RAW disk

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.


Author Comment

ID: 33735149
Ok, I understand what you are referring to now. I have been using P2V to create a test lab on a separate network. You are thinking that if I was P2Ving for production servers, I could connect the VM's to the virtual server after.

I have been reading that file sharing can cause problems - there is on shared folder on the problem server D:\ drive. Do you think that would be causing this issue. The other blade server has no shared folder on the D:\ drive.

You mentioned your "article" - where do I find this?

LVL 23

Accepted Solution

Luciano Patrão earned 500 total points
ID: 33735300

Yes, with shared folders you can get some issues, but this is not the problem the vConverter not seeing all the disks.

This is why i like cold migration in a P2V, doing this we can bypass many issues and use the server as is, not working with the OS etc.

PS: Sorry forget to add the article


Author Comment

ID: 33735473
Thank you for your help - I will read through your document. My next opportunity to try this again is later this week. I will update accordingly once I have done that.

LVL 16

Expert Comment

ID: 33740829
you might check to see if the disks are dynamic or GPT within disk manager of Windows on the 2nd blade.

Author Closing Comment

ID: 33853596
Thanks. I am going to follow your advise. For the other fellow who replied, the disks are not Dynamic. I looked into that one.

Featured Post

Don't miss ATEN at NAB Show April 24-27!

Visit ATEN at NAB Show to learn how our "Seamlessly Entertaining" solutions deliver fast, precise video streaming without delays for the broadcasting and media environment. ATEN will showcase its 16x16 Modular Matrix Switch (VM1600) and KVM Over IP Solution (KE6900 series).

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Find the Size of the Folders in VM and Templates. 11 73
VM delta disk 2 50
VMware Fault Tolerance between remote sites 2 56
ESXi NTP 4 60
When converting a physical machine to a virtual machine using VMware vCenter Converter Standalone or vCenter Converter Enterprise, if an adapter type is not selected during the initial customization the resulting virtual machine may contain an IDE d…
Ransomware is a malware that is again in the list of security  concerns. Not only for companies, but also for Government security and  even at personal use. IT departments should be aware and have the right  knowledge to how to fight it.
Teach the user how to configure vSphere Replication and how to protect and recover VMs Open vSphere Web Client: Verify vsphere Replication is enabled: Enable vSphere Replication for a virtual machine: Verify replicated VM is created: Recover replica…
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…

733 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question