Forum

Bildirimler
Hepsini Temizle

windows hyper -v Migrate Converte Sorunu

4 Yazılar
3 Üyeler
0 Reactions
569 Görüntüleme
(@SamiOzdemir)
Gönderiler: 90
Estimable Member
Konu başlatıcı
 

Merhaba

 1 Adet windows 2012 r2  fiziksel sunucum var bunu sanal sunucu çevirmek işin

Microsoft Virtual Machine Converter 3.1  kurdum ve işleme başladım ama   işlem bir kısımdan sonra hata verdi neden bu hata alıyorum lütfen yardımcı olurmusunuz  ?

 

 

 

Hata log ise bunlar yazıyor

 

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Copying directly to target Vm folder: True. Disk-to-VHD BITS client machine: xxxx, target location E:\Bulut\.

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Using https: True.

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Physical machine drives:

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Device ID: \\?\Volume{a5f820f8-ac64-11e4-80b4-806e6f6e6963}\. Mounted device value: 673d9f5c0000100000000000. Volume Guid: \\?\Volume{a5f820f8-ac64-11e4-80b4-806e6f6e6963}\. IsBoot: True. IsWindows: False.

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Device ID: C. Mounted device value: 673d9f5c0000f01500000000. Volume Guid: \\?\Volume{a5f820f9-ac64-11e4-80b4-806e6f6e6963}\. IsBoot: False. IsWindows: True.

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Selected drives:

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Device ID: \\?\Volume{a5f820f8-ac64-11e4-80b4-806e6f6e6963}\. Mounted device value: 673d9f5c0000100000000000. Volume Guid: \\?\Volume{a5f820f8-ac64-11e4-80b4-806e6f6e6963}\. IsBoot: True. IsWindows: False.

02/15/2015 18:00:27 +02:00  [28]  VERBOSE: Device ID: C. Mounted device value: 673d9f5c0000f01500000000. Volume Guid: \\?\Volume{a5f820f9-ac64-11e4-80b4-806e6f6e6963}\. IsBoot: False. IsWindows: True.

02/15/2015 18:00:56 +02:00  [28]  VERBOSE: Source machine image deployment file name: 0.1.0x15e00000.1.0xec5b4291.0x0.\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1

02/15/2015 18:00:56 +02:00  [28]  VERBOSE: Target file name: E:\Bulut\xxxx\a5f820f8-ac64-11e4-80b4-806e6f6e6963.vhd

02/15/2015 18:00:56 +02:00  [28]  VERBOSE: Source machine image deployment file name: 0.1.0x1173a000000.0.0x4be1a460.0x0.\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2

02/15/2015 18:00:56 +02:00  [28]  VERBOSE: Target file name: E:\Bulut\xxx\C.vhd

02/15/2015 20:10:06 +02:00  [28]  EXCEPTION: System.InvalidOperationException: Unable to extract the physical drive number from the physical path.

   konum: Microsoft.Accelerators.Mvmc.Engine.Drive.Virtual.VirtualDiskBase.GetAttachedPhysicalDriveNumberFromPath(TaskContext taskContext)

   konum: Microsoft.Accelerators.Mvmc.Engine.ServiceLayer.Internal.PhysicalMachineConversionService.FixupWindowsDrive(String tempDirectory, TaskContext taskContext)

   konum: Microsoft.Accelerators.Mvmc.Engine.ServiceLayer.Internal.PhysicalMachineConversionService.Fixup(String tempDirectory, IPostProgress fixupDiskPhase, TaskContext taskContext)

   konum: Microsoft.Accelerators.Mvmc.Engine.ServiceLayer.Internal.PhysicalMachineConversionService.ConvertToMachine(IP2VMachineConversionRequest p2vMachineConversionRequest, TaskContext taskContext)

   konum: Microsoft.Accelerators.Mvmc.Engine.ServiceLayer.Internal.PhysicalMachineConversionService.<>c__DisplayClass4.<ConvertToMachineAsync>b__3()

   konum: System.Threading.Tasks.Task`1.InnerInvoke()

   konum: System.Threading.Tasks.Task.Execute()

02/15/2015 20:10:06 +02:00  [28]  Exception caught : System.InvalidOperationException: Unable to extract the physical drive number from the physical path.

   konum: Microsoft.Accelerators.Mvmc.Gui.Model.ConversionModel.ConvertGuestMachine()

   konum: Microsoft.Accelerators.Mvmc.Gui.ViewModels.Machine.MachineCompletionViewModel.OnWorkerDoWork()

02/15/2015 20:10:06 +02:00  [1]  Background task is complete.

02/15/2015 20:10:06 +02:00  [1]  Conversion error message is displayed.

02/15/2015 20:10:06 +02:00  [1]  Conversion info message is displayed.

02/15/2015 20:10:06 +02:00  [1]  Value of 'ErrorMessage' = 'Unable to extract the physical drive number from the physical path.'

 

 
Gönderildi : 15/02/2015 23:15

(@GokceKARGI)
Gönderiler: 160
Estimable Member
 

Aşağıdaki uygulamayı denermisin

 

https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx

 
Gönderildi : 16/02/2015 12:08

(@SamiOzdemir)
Gönderiler: 90
Estimable Member
Konu başlatıcı
 

Aşağıdaki uygulamayı denermisin

 

https://technet.microsoft.com/en-us/sysinternals/ee656415.aspx

 

Merhaba o şekilde yedek alıp aktardım bu seferde sanal sunucu boot etmedi.

1 kere değil  15 20 kere denedim  yedek alınan server baktım program falan mı çakışıyor diye sorun yok

vmware  deneyim dedim vmware esxi sorunsuz aktarıldı ama gel gelelim hyper -v  olunca olmıyor.
veren hatata hep aynı

02/16/2015 06:22:12 +02:00  [1]  Background task is complete.

02/16/2015 06:22:12 +02:00  [1]  Conversion error message is displayed.

02/16/2015 06:22:12 +02:00  [1]  Value of 'ErrorMessage' = 'Unable to extract the physical drive number from the physical path.'

 Konu microsoft destek sayfasınada açılmışdır.

 

https://social.msdn.microsoft.com/Forums/en-US/9692a4d0-536d-458d-a58a-c1b4d18f2c7c/windows-hyper-v-migrate-converte-sorunu?forum=konudisitr  

 

 
Gönderildi : 16/02/2015 12:48

(@aytacarslan)
Gönderiler: 799
Noble Member
 

üstad sunucu sistemlere birer tane sata yada benzeri normal bir disk takıp disk2vhd ile imajı aktarın. imajı hyper v makineye aynı disk ile taktığınızda açılıyormu kontrol edin.

 
Gönderildi : 03/04/2015 18:06

Paylaş: