Stuck on endless 'Read Errors'

[limecreek]

Got over 1000 Read Errors and showing 97% complete.  Don't know what to do?

Ideas?

 

Pasted below are the first of the Read Error Messages I'm getting.

 

 

W 17:09:23 Failed to Read Sector 2229386 - Reason: The request could not be performed because of an I/O device error.
W 17:09:23 Sector 2229386 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:09:29 Failed to Read Sector 2229387 - Reason: Unrecovered Read Error
W 17:09:29 Sector 2229387 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:09:36 Failed to Read Sector 2229388 - Reason: Unrecovered Read Error
W 17:09:36 Sector 2229388 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:09:42 Failed to Read Sector 2229389 - Reason: Unrecovered Read Error
W 17:09:42 Sector 2229389 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:09:49 Failed to Read Sector 2229390 - Reason: Unrecovered Read Error
W 17:09:49 Sector 2229390 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:09:55 Failed to Read Sector 2229391 - Reason: Unrecovered Read Error
W 17:09:55 Sector 2229391 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:10:02 Failed to Read Sector 2229440 - Reason: Unrecovered Read Error
W 17:10:02 Sector 2229440 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:10:08 Failed to Read Sector 2229441 - Reason: Unrecovered Read Error
W 17:10:08 Sector 2229441 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:10:14 Failed to Read Sector 2229442 - Reason: Unrecovered Read Error
W 17:10:14 Sector 2229442 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:10:21 Failed to Read Sector 2229443 - Reason: The request could not be performed because of an I/O device error.


W 17:11:37 Failed to Read Sector 2229455 - Reason: Unrecovered Read Error
W 17:11:37 Sector 2229455 maps to File: \VIDEO_TS\VTS_06_4.VOB
W 17:11:46 Failed to Read Sectors 2229584 - 2229615 - Reason: Unrecovered Read Error
W 17:11:53 Failed to Read Sector 2229584 - Reason: Unrecovered Read Error

 

[LIGHTNING UK!]

Your drive seems unable to read the disc.

 

Is it dirty / scratched?

[limecreek]

Thanks for the reply Admin.

 

The program finally waded it's way through the file and successfully wrote it onto the disk.  It just took many hours.

[LIGHTNING UK!]

Ok but obviously you're going to run into problems when anything tries to play that file it kept erroring out on... it's corrupt.