VMware Cloud Community
NetManOne
Enthusiast
Enthusiast
Jump to solution

converter V5.1.0 fails at 71%, Warning: Unable to read the block at offset '28,243,914,752' on volume 'D:

Hello:

I am converting physical machines to VM sot hat we can consolidate our environment. The converter V5.1.0 Build1087880 fails at 71%, with a Warning:

so far, I have good progress on other physical machines except for this stubborn XP -X64 machine. We need to keep it for legacy reasons until there are replacement apps for all sw running on it (; This machine has SSD drive and no spinning HD

each time the conversion is able to start and complete the first on two drives. The GUI states its fine , but the log shows

2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading partition table

2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 1 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

When it gets to the second drive, I stops as it cant read some sector block.

2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading partition table

2013-08-11T09:00:00.782-04:00 [02748 warning 'Default'] Disk number 2 has been skipped because of errors while reading dynamic disks header or LDM database is corrupted

2013-08-11T10:16:13.706-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():

Error (type: 2, code: 27) reading 223232 bytes starting at 0x000000069377f000 from the source volume 😧

2013-08-11T10:16:53.800-04:00 [04324 error 'task-2'] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks():

Error (type 2, code: 27), detected bad sector at offset 0x0000000693796000 on the source volume 😧

I have run several apps to check and fix the D drive, but none find any issues. the XP-X64 machine has been restated after each test and re run. no issues are found on either drive

I have tried to run the converter without  the D drive. It wont let me do so as it states that the D drive Is critical to the conversion and wont proceed without it

I have attached GUI screen shots and two logs files

Can anyone please help?

Is there is a way to find the root problem or proceed?

if windows cant find an issue with  the D Drive why does the converter?

xp-x64-converstion status.png

unable to read block.png

xp-x64-summary status.png


Reply
0 Kudos
1 Solution

Accepted Solutions
NetManOne
Enthusiast
Enthusiast
Jump to solution

As mention, now and then the VSS writers for VM’s will go haywire, causing backups to fail and the converter to not finish.
The solution from google searches is  simple. i an now able to once complete the xp-64 converter and do backups

To resolve this problem, follow these steps:
1.Click Start, click Run, type Regedit, and then click OK.
2.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
3.On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
4.Exit Registry Editor.
5.Click Start, click Run, type services.msc, and then click OK.
6.Right-click the following services one at a time. For each service, click Restart:

COM+ Event System
COM+ System Application
Microsoft Software Shadow Copy Provider
Volume Shadow Copy

7.Click Start, click Run, type cmd, and then click OK.
8. At the command prompt, type vssadmin list writers, and then press ENTER.
9.If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps.

If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.?cd /d %windir%\system32

net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
regsvr32 msxml6.dll

Note The last two command may not run successfully.
10. At the command prompt, enter

vssadmin list providers
vssadmin list writers

11.Confirm that the VSS writers are now listed. sample are shown  below

C:\Documents and Settings\Administrator>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

-Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {a7ab6df2-8ec3-4af6-b85c-2720101125cd}
   State: [1] Stable
   Last error: No error

+Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {706b5f2f-acf8-4ca3-bd19-0d3944470455}
   State: [1] Stable
   Last error: No error

+Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {40d12f58-1899-480e-8ded-b86aa712897d}
   State: [1] Stable
   Last error: No error

+Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {aa8285e9-fbdf-4814-a30c-fb9072da4ad9}
   State: [1] Stable
   Last error: No error

=Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fc777263-7ce8-490d-8aa3-2ca6a4af8f72}
   State: [1] Stable
   Last error: No error

+Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {25cae1bb-968f-4c5a-86ee-d1d111f2fadd}
   State: [1] Stable
   Last error: No error

View solution in original post

Reply
0 Kudos
5 Replies
NetManOne
Enthusiast
Enthusiast
Jump to solution

it now stops after 4.5 hours with 95% completed

it shows

FAILED: Unable to create a VSS snapshot of the source volume(s).

Error code:2147549183 (0x8000FFFF).

xp-x64-converstion status4.5 hours-94percent.png

LOG highlights4.5 hours-94percent..png

and here are the latest LOGS

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

There are many threads about VSS because there are different problem with VSS, try to play with vssadmin and ensure you have enough free disk space for snapshot. HTH

Reply
0 Kudos
POCEH
VMware Employee
VMware Employee
Jump to solution

Run the command "chkdsk d: /r" and try conversion again.

Reply
0 Kudos
NetManOne
Enthusiast
Enthusiast
Jump to solution

Hello:

I have  plenty of destination space; not the issue

I have run that chkdsk command; it comes back clean

I found this  note. I will double check the VSS area. Funny thgough is the backup of the machine runs fine and it uses the VSS system

This is a known Microsoft issue.

To resolve this issue, see the Microsoft Knowledge Base article 940184 or 2009533.

also another suggestion

In order to rebuild it the VSS related services need to be restarted:
?COM+ Event System
?COM+ System Application
?Microsoft Software Shadow Copy Provider
?Volume Shadow Copy

Even though it rebuilt my registry, it wasn’t enough.. so after a small research of the related DLLs, I re-registered them
(Volume Shadow Copy and  Microsoft Software Shadow Copy services MUST BE STOPPED FIRST)
1.regsvr32 ole32.dll
2.regsvr32 oleaut32.dll
3.regsvr32 eventcls.dll
4.regsvr32 vss_ps.dll ?
   Re-register the service after this command:
    vssvc /register

5.regsvr32 swprv.dll
6.regsvr32 stdprov.dll
7.regsvr32 vssui.dll
8.regsvr32 msxml.dll
9.regsvr32 msxml3.dll
10.regsvr32 msxml4.dll
11.regsvr32 msxml6.dll

I will re post after checking this

Reply
0 Kudos
NetManOne
Enthusiast
Enthusiast
Jump to solution

As mention, now and then the VSS writers for VM’s will go haywire, causing backups to fail and the converter to not finish.
The solution from google searches is  simple. i an now able to once complete the xp-64 converter and do backups

To resolve this problem, follow these steps:
1.Click Start, click Run, type Regedit, and then click OK.
2.Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions
3.On the Edit menu, click Delete, and then click Yes to confirm that you want to delete the subkey.
4.Exit Registry Editor.
5.Click Start, click Run, type services.msc, and then click OK.
6.Right-click the following services one at a time. For each service, click Restart:

COM+ Event System
COM+ System Application
Microsoft Software Shadow Copy Provider
Volume Shadow Copy

7.Click Start, click Run, type cmd, and then click OK.
8. At the command prompt, type vssadmin list writers, and then press ENTER.
9.If the VSS writers are now listed, close the Command Prompt window. You do not have to complete the remaining steps.

If the VSS writers are not listed, type the following commands at the command prompt. Press ENTER after each command.?cd /d %windir%\system32

net stop vss
net stop swprv
regsvr32 ole32.dll
regsvr32 oleaut32.dll
regsvr32 /i eventcls.dll
regsvr32 vss_ps.dll
vssvc /register
regsvr32 /i swprv.dll
regsvr32 es.dll
regsvr32 stdprov.dll
regsvr32 vssui.dll
regsvr32 msxml.dll
regsvr32 msxml3.dll
regsvr32 msxml4.dll
regsvr32 msxml6.dll

Note The last two command may not run successfully.
10. At the command prompt, enter

vssadmin list providers
vssadmin list writers

11.Confirm that the VSS writers are now listed. sample are shown  below

C:\Documents and Settings\Administrator>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
   Provider type: System
   Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   Version: 1.0.0.7

C:\Documents and Settings\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.

-Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {a7ab6df2-8ec3-4af6-b85c-2720101125cd}
   State: [1] Stable
   Last error: No error

+Writer name: 'MSDEWriter'
   Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
   Writer Instance Id: {706b5f2f-acf8-4ca3-bd19-0d3944470455}
   State: [1] Stable
   Last error: No error

+Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {40d12f58-1899-480e-8ded-b86aa712897d}
   State: [1] Stable
   Last error: No error

+Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {aa8285e9-fbdf-4814-a30c-fb9072da4ad9}
   State: [1] Stable
   Last error: No error

=Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fc777263-7ce8-490d-8aa3-2ca6a4af8f72}
   State: [1] Stable
   Last error: No error

+Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {25cae1bb-968f-4c5a-86ee-d1d111f2fadd}
   State: [1] Stable
   Last error: No error

Reply
0 Kudos