Solved: BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): ...

ZDgdtel · ‎11-20-2017

Hi all,

The error occurred every time during conversions, hoping someone has some more experience.

Source windows server 2008 64bit

Converter 6.1

ESX 6.0

I start conversion and fails at 35% with error:

2017-11-21T02:27:56.877+08:00 error vmware-converter-agent[05728] [Originator@6876 sub=task-3] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Error (type: 2, code: 21) reading 655360 bytes starting at 0x0000002d11ee0000 from the source volume 😧

2017-11-21T02:27:56.877+08:00 error vmware-converter-agent[05728] [Originator@6876 sub=task-3] BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Unrecoverable error (type: 2, code: 21) reading 655360 bytes starting from 0x0000002d11ee0000 from the source volume 😧

2017-11-21T02:27:56.877+08:00 error vmware-converter-agent[05728] [Originator@6876 sub=task-3] BlockLevelVolumeCloneMgr::CloneVolume: failed with exception converter.fault.FileIOFault

2017-11-21T02:27:57.084+08:00 info vmware-converter-agent[45968] [Originator@6876 sub=task-3] CircularBuffer::GetItem: work cancelled

2017-11-21T02:27:57.084+08:00 info vmware-converter-agent[45968] [Originator@6876 sub=task-3] BackgroundWriter::ThreadFunc: Broadcasting "ThreadDone" condition.

2017-11-21T02:27:57.085+08:00 info vmware-converter-agent[45968] [Originator@6876 sub=ThreadPool] Thread delisted

2017-11-21T02:27:57.085+08:00 info vmware-converter-agent[05728] [Originator@6876 sub=task-3] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2017-11-21T02:27:57.086+08:00 info vmware-converter-agent[05728] [Originator@6876 sub=task-3] BackgroundWriter::~BackgroundWriter: Emptying CircularBuffer with abort conditions

2017-11-21T02:27:57.087+08:00 info vmware-converter-agent[05728] [Originator@6876 sub=task-3] [StreamCacheWriter] - TotalZeros : 0, TotalWrites : 288323

-->

2017-11-21T02:27:57.087+08:00 error vmware-converter-agent[05728] [Originator@6876 sub=task-3] SingleVolumeCloneTask::DoRun: Volume cloning failed with error converter.fault.FileIOFault

2017-11-21T02:27:57.087+08:00 error vmware-converter-agent[05728] [Originator@6876 sub=task-3] TaskImpl has failed with MethodFault::Exception: converter.fault.CloneFault

2017-11-21T02:27:57.087+08:00 info vmware-converter-agent[05728] [Originator@6876 sub=task-3] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[E7-92-FF-83-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-7.2)?/3(0000010000000000 updates, state: 4, percentage: 30, xfer rate (Bps): 4258464

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] CompositeTask canceling #3 subtasks

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] TaskImpl issuing Cancel command

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[CD-0C-29-C5-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-=,<0925,0000010000000000 updates, state: 3, percentage: 100, xfer rate (Bps): 6051642

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] TaskImpl issuing Cancel command

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[CD-0C-29-C5-00-00-50-06-00-00-00-00] --> [target VM (unknown name)]-=,<0925,0000028000000000 updates, state: 3, percentage: 100, xfer rate (Bps): 4494524

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] TaskImpl issuing Cancel command

2017-11-21T02:27:57.622+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] SingleVolumeCloneTask [source computer (unknown name)]-\WindowsBitmapDriverVolumeId=[E7-92-FF-83-00-00-10-00-00-00-00-00] --> [target VM (unknown name)]-7.2)?/3(0000010000000000 updates, state: 4, percentage: 30, xfer rate (Bps): 4258464

2017-11-21T02:27:57.660+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] VolumeBasedCloneTask source computer (unknown name) --> target VM (unknown name) updates, state: 4, percentage: 35, xfer rate (Bps): 4258464

2017-11-21T02:27:57.660+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] VolumeBasedCloneTask failed

2017-11-21T02:27:57.660+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] CloneTask updates, state: 4, percentage: 35, xfer rate (Bps): 4258464

2017-11-21T02:27:57.660+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] CloneTask failed

2017-11-21T02:27:57.660+08:00 error vmware-converter-agent[48992] [Originator@6876 sub=Default] Task failed:

2017-11-21T02:27:57.874+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=task-3] Scheduled timer canceled, StopKeepAlive succeeds

2017-11-21T02:27:57.874+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=Default] Task Completed : task-3

2017-11-21T02:27:57.875+08:00 info vmware-converter-agent[48992] [Originator@6876 sub=ThreadPool] Thread delisted

patanassov · ‎11-22-2017

Low free space may cause VSS errors, but that's not what happens here (the conversion would fail even before the cloning starts and with a different error).

Is it possible something is obstructing disk operations sometimes (like faulty hardware or driver issues)? I am just wild guessing here.

Another wild guess for workaround I can think of is to force file level cloning. This may be forced by shrinking the volume (hardly an option in this case) or by changing the cluster size.

You may also set the log level to verbose and the attach the full logs for further examination in the hope something interesting shows up.

View solution in original post

patanassov · ‎11-20-2017

Windows error 21 reads "The device is not ready.". It is being thrown in ReadAndSkipBadBlocks.

Have you checked drive 😧 for bad sectors?

AjayChanana · ‎11-21-2017

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

Please check above if that help you to resolve the issue.

Regards,
Ajay Chanana

ZDgdtel · ‎11-21-2017

Thank you for your suggestion!

I have tried several apps to check the D driver, but none find any issues.

The source machine is a running database server,and the D Driver has only 10MB free space.Dose it matter?

patanassov · ‎11-22-2017

Low free space may cause VSS errors, but that's not what happens here (the conversion would fail even before the cloning starts and with a different error).

Is it possible something is obstructing disk operations sometimes (like faulty hardware or driver issues)? I am just wild guessing here.

Another wild guess for workaround I can think of is to force file level cloning. This may be forced by shrinking the volume (hardly an option in this case) or by changing the cluster size.

You may also set the log level to verbose and the attach the full logs for further examination in the hope something interesting shows up.

ZDgdtel · ‎12-04-2017

I have tried file level cloning and it worked!

Though I still dont know why it happened:smileysilly:

patanassov · ‎12-05-2017

This is good news.

The reason probably is that some volume blocks could not be read in block level mode. Those are not used by files, so file level have succeeded. Why those blocks have not been reported when checking the file system remains in the unknown

All

BlockLevelVolumeCloneMgr::ReadAndSkipBadBlocks(): Error (type: 2, code: 21)