VMware Cloud Community
rwelcomme
Contributor
Contributor

Error Unable to find the System Volime, reconfiguration is not possible in 2008 R2

Hi Guys,

very frustrating issue.  I'm currently using the latest version of vmware convertor 5.5.1 while the version of my ESXi is 5.1.0, if this helps.  I am converting a 2008 server R2 and at 96% it keeps on failing with the status "vmware converter FAILED: Unable to find the system volume, reconfiguration is not possible."

I've seen similar post where the solution is to modify boot.ini; but 2008 R2 does not have any boot.ini file. And my error logs are different  Any suggestions is highly appreciated.  Attached is the log file.

Reply
0 Kudos
5 Replies
SanjaySP1
VMware Employee
VMware Employee

Hi

From the worker log snippet I see that converter is finding two partitions. (Refer to first line).


2014-06-12T21:02:49.250-05:00 [02032 info 'Default'] Disk with signature 2012837881, recognized partitions 2

2014-06-12T21:02:49.250-05:00 [02032 warning 'task-11'] [MoveActiveDiskIfNeeded] GetFirstBootDisk failed, mntapi error: 176

2014-06-12T21:02:49.250-05:00 [02032 info 'task-11'] Reusing existing VIM connection to VCenter.cio.net

2014-06-12T21:02:49.266-05:00 [12596 info 'ThreadPool'] Thread enlisted

2014-06-12T21:02:49.890-05:00 [02032 info 'Default'] MNTAPI: Mounted volume \\.\vstor2-mntapi20-shared-F977F977000010000000000033000000\ FS:<NTFS>

2014-06-12T21:02:50.280-05:00 [12596 info 'ThreadPool'] Thread delisted

2014-06-12T21:02:50.280-05:00 [08296 info 'ThreadPool'] Thread enlisted

2014-06-12T21:02:50.794-05:00 [02032 info 'Default'] MNTAPI: Mounted volume \\.\vstor2-mntapi20-shared-F977F977000010400C00000034000000\ FS:<NTFS>

2014-06-12T21:02:51.106-05:00 [08296 info 'ThreadPool'] Thread delisted

2014-06-12T21:02:51.106-05:00 [02032 error 'task-11'] [GetMntapiOsInfo] Got an error getting MNTAPI OS information

2014-06-12T21:02:51.106-05:00 [02032 error 'task-11'] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 176 MNTAPI errorType = 0, errorCode = 11

2014-06-12T21:02:51.106-05:00 [02032 warning 'task-11'] [PopulateDetailedOsInfo] Failed to get MNTAPI OS version information

2014-06-12T21:02:51.106-05:00 [02032 warning 'task-11'] [PopulateDetailedOsInfo] Failed to get MNTAPI system volume: 176 (type = 0, code=11)

2014-06-12T21:02:51.106-05:00 [02032 warning 'task-11'] [PopulateDetailedOsInfo] Failed to get MNTAPI active volume: 176 (type = 0, code=11)

2014-06-12T21:02:51.106-05:00 [02032 warning 'task-11'] [PopulateVolumeMountPoints] Failed to get mountpoints for volume 9/779/770000010000000000: 176 (type = 0, code=11)

2014-06-12T21:02:51.106-05:00 [02032 warning 'task-11'] [PopulateVolumeMountPoints] Failed to get mountpoints for volume 9/779/7700000104<0000000: 176 (type = 0, code=11)

2014-06-12T21:02:51.106-05:00 [02032 info 'task-11'] [LogMessagesForQA] System volume is not detected.

Please note that Converter Standalone 5.5 cannot convert dynamic disks which have more than one partition regardless of whether both partitions are active or not. Converter Standalone will not be able to convert disks which are multi-boot or have more than one active partitions however this is expected behaviour.


This is a regression which was fixed in Converter Standalone 5.0.1. Hence please try the conversion using Converter Standalone 5.0.1.



If the above solution helps please consider marking this thread as answered.






Alternatively I see a workaround provided in Converter 5.5 release notes for this issue. Please visit below URL and find the section 'Configuration of Windows virtual machines with multiple active partitions might not complete'.


VMware vCenter Converter Standalone Release Notes

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

It's ridiculous - where you see the dynamic disks? Just curious...

For your information dynamic disks are transferred in almost all cases Smiley Happy

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

Seems you skip the active volume in transfer - as result there is no active (i.e. bootable) volume on destination.

Please retry the conversion with all volumes selected.

HTH

Reply
0 Kudos
SanjaySP1
VMware Employee
VMware Employee

Hi

I agree dynamic disks are allowed. But dynamic disks identified with more than one partition is where the problem arises.

'Disk with signature 2012837881, recognized partitions 2'

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee

Absolutely not! The dynamic disks uses *different* partition type!

Also every MBR disk could contain 4 different partitions.

Please do not post a misleading information if you not sure what happens.

Reply
0 Kudos