Not Able To Migrate Dynamic Disks With VSMT? I Think Not.

While tinkering around with a recent migration that of an older production server running Windows 2000 server on a Compaq DL320 G1 server, I discovered that it was configured with software RAID 1 with Dynamic Disks.  Once I saw this I immediately thought that I was in for a long night of potentially ghosting and then manually stripping out the HAL and potentially a repair install.  When I ran the hardware validate on my XML file, my fears were confirmed where it stated that no drives were available for migration. 
Microsoft (R) Virtual Server Migration Toolkit – VmScript Tool ver.5.2.5149.0
Copyright (C) 2004 Microsoft Corporation. All rights reserved.
 
Parsing file: C:\Program Files\Microsoft VSMT\DH517.xml
WARNING: Found a partition of "Unknown" type.
         The partition will be skipped from imaging.
         Details: (Disk:0 Partition:1 Type:255 Hosted Logical Drives:)
 
WARNING: Dynamic disks are not supported.
         The disk/partition will be skipped from imaging.
         Details: (Disk:0 Partition:2 Type:66 Hosted Logical Drives:C:)
 
WARNING: Dynamic disks are not supported.
         The disk/partition will be skipped from imaging.
         Details: (Disk:0 Partition:3 Type:66 Hosted Logical Drives:D:)
 
WARNING: Found a partition of "Unknown" type.
         The partition will be skipped from imaging.
         Details: (Disk:1 Partition:1 Type:255 Hosted Logical Drives:C:)
 
WARNING: Dynamic disks are not supported.
         The disk/partition will be skipped from imaging.
         Details: (Disk:1 Partition:2 Type:66 Hosted Logical Drives:)
 
WARNING: Dynamic disks are not supported.
         The disk/partition will be skipped from imaging.
         Details: (Disk:1 Partition:3 Type:66 Hosted Logical Drives:D:)
 
WARNING: Dynamic disks are not supported.
         The disk/partition will be skipped from imaging.
         Details: (Disk:1 Partition:4 Type:66 Hosted Logical Drives:)
 
Checking configuration for incompatibilities.
 
ERROR: Could not find a supported partition type that hosts the windows directory.
ERROR: Configuration is not compatible.
Warning: Incompatibilities found in hardware config.
Error: Result Code:10
 
The only good thing I could think of coming out of this night was that the 24 hour AuBon Pan gives reduced price pastries starting at midnight.   Even with this late night temptation in mind, I started to think about alternate options.
From what I tried with WinImage v8.0 on a previous migration (See this post), changing the drive type within the XML file so that it would not migrate a specific drive, I thought that I would try to modify the XML file in this case to try to see if for some strange reason the dynamic drives would migrate.  Below are the lines that I changed to make the process work. 
 

<SystemComponent name="Partition">

                        <Data item="Index"><![CDATA[1]]></Data>

                        <Data item="Caption"><![CDATA[Disk #0, Partition #1]]></Data>

                        <Data item="Size"><![CDATA[6292339200]]></Data>

                        <Data item="NumberOfBlocks"><![CDATA[12289725]]></Data>

                        <Data item="StartingOffset"><![CDATA[41126400]]></Data>

                        <Data item="DiskIndex"><![CDATA[0]]></Data>

                        <Data item="Bootable"><![CDATA[-1]]></Data>

                        <Data item="PrimaryPartition"><![CDATA[-1]]></Data>

                        <Data item="Type"><![CDATA[Logical Disk Manager]]></Data>

                                    <SystemComponent name="PartitionLogicalDrive">

                                                <Data item="LogicalDrive"><![CDATA[C:]]></Data>

                                                <Data item="StartAddress"><![CDATA[41126400]]></Data>

                                                <Data item="EndAddress"><![CDATA[6333465599]]></Data>

                                                <Data item="BootINI"><![CDATA[[boot loader]

timeout=5

default=multi(0)disk(0)rdisk(0)partition(2)\WINNT

[operating systems]

multi(0)disk(0)rdisk(0)partition(2)\WINNT="Microsoft Windows 2000 Server" /fastdetect

]]></Data>

            </SystemComponent>

            </SystemComponent>

            <SystemComponent name="Partition">

                        <Data item="Index"><![CDATA[2]]></Data>

                        <Data item="Caption"><![CDATA[Disk #0, Partition #2]]></Data>

                        <Data item="Size"><![CDATA[11869079040]]></Data>

                        <Data item="NumberOfBlocks"><![CDATA[23181795]]></Data>

                        <Data item="StartingOffset"><![CDATA[6333465600]]></Data>

                        <Data item="DiskIndex"><![CDATA[0]]></Data>

                        <Data item="PrimaryPartition"><![CDATA[0]]></Data>

                        <Data item="Type"><![CDATA[Logical Disk Manager]]></Data>

                                    <SystemComponent name="PartitionLogicalDrive">

                                                <Data item="LogicalDrive"><![CDATA[D:]]></Data>

                                                <Data item="StartAddress"><![CDATA[6333465600]]></Data>

                                                <Data item="EndAddress"><![CDATA[18202544639]]></Data>

                                    </SystemComponent>

 

 

I changed the lines above that are in bold and underlined to the following:

<Data item="Type"><![CDATA[Installable File System]]></Data>

 

Note: Since this was a software mirror with dynamic disk,  I only changed the first references to C: and D: in the XML file that resided on the first SCSI disk.

The end result, the process worked.  I expected it to quit during the capture stage, but it finished.  Then I figured that it would fail on the deploy stage, but it proceeded as normal.  I would certainly be faced with a blue screen on boot, but all was well with the first boot.   So what did it look like when I finished?  It migrated all data drives from the first SCSI disk flawlessly and made them Basic disks on deployment into virtual.  Since I did not change the XML entries for the Second SCSI disk in the XML file, it did not migrate them at all.  Strange, but it worked.   Give it a try and let me know what you get for results.

Advertisements
This entry was posted in Virtual Server Technology. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s