Verify error: no seek complete

[trikztar]

Hi there

 

I'm having some annoying problems burning dvd's, and I just can't figure out what's causing them. I've tried burning various images at varying speeds, but I still get errors. What is odd, is that I can play the dvd's on my computer, but not my standalone dvd-player (philips hdrw-720). Sometimes the dvd's do actually work on the philips as well, but errors still occur during verification. Here's the log:

 

I 13:42:30 ImgBurn Version 2.1.0.0 started!

I 13:42:30 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

W 13:42:30 Drive M:\ (FAT32) does not support single files > 4 GB

W 13:42:30 Drive N:\ (FAT32) does not support single files > 4 GB

W 13:42:30 Drive O:\ (FAT32) does not support single files > 4 GB

I 13:42:30 Initialising SPTI...

I 13:42:30 Searching for SCSI / ATAPI devices...

I 13:42:30 Found 1 CD-RW, 2 DVD-ROMs and 1 DVD?RW!

I 13:45:22 Operation Started!

I 13:45:22 Source File: C:\dvdmovie.ISO

I 13:45:22 Source File Sectors: 2.251.895 (MODE1/2048)

I 13:45:22 Source File Size: 4.611.880.960 bytes

I 13:45:22 Source File Volume Identifier: dvd_movie

I 13:45:22 Source File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR ? 1993 E.YOUNGDALE ? 1997

 

J.PEARSON/J.SCHILLING

I 13:45:22 Source File Implementation Identifier: mkisofs

I 13:45:23 Source File File System(s): ISO9660; UDF (1,02)

I 13:45:23 Destination Device: [1:1:0] _NEC DVD_RW ND-3550A 1.06 (K:) (ATA)

I 13:45:23 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 2,4x; 4x; 6x; 8x; 12x; 16x)

I 13:45:23 Destination Media Sectors: 2.295.104

I 13:45:23 Write Mode: DVD

I 13:45:23 Write Type: DAO

I 13:45:23 Write Speed: 4x

I 13:45:23 Link Size: Auto

I 13:45:23 Test Mode: No

I 13:45:23 BURN-Proof: Enabled

I 13:45:23 Filling Buffer...

I 13:45:24 Writing LeadIn...

I 13:45:53 Writing Image...

I 13:59:32 Synchronising Cache...

I 13:59:33 Closing Track...

I 13:59:45 Finalising Disc...

I 14:00:01 Image MD5: 506445ea1efc53e5d0c8a0a7fe5faf49

I 14:00:01 Operation Successfully Completed! - Duration: 00:14:38

I 14:00:01 Average Write Rate: 5.505 KB/s (4.0x) - Maximum Write Rate: 6.141 KB/s (4.4x)

I 14:00:01 Cycling Tray before Verify...

I 14:00:22 Device Ready!

I 14:00:22 Operation Started!

I 14:00:22 Source Device: [1:1:0] _NEC DVD_RW ND-3550A 1.06 (K:) (ATA)

I 14:00:22 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: MCC-004-00) (Speeds: 2,4x; 4x; 6x; 8x; 12x; 16x)

I 14:00:22 Image File: C:\dvdmovie.ISO

I 14:00:22 Image File Sectors: 2.251.895 (MODE1/2048)

I 14:00:22 Image File Size: 4.611.880.960 bytes

I 14:00:22 Image File Volume Identifier: dvd_movie

I 14:00:22 Image File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR ? 1993 E.YOUNGDALE ? 1997

 

J.PEARSON/J.SCHILLING

I 14:00:22 Image File Implementation Identifier: mkisofs

I 14:00:22 Image File File System(s): ISO9660; UDF (1,02)

I 14:00:22 Verifying Sectors...

W 14:05:42 Failed to read Sector 1864560 - No Seek Complete

W 14:05:42 Sector 1864560 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:48 Failed to read Sector 1864561 - Unrecovered Read Error

W 14:05:48 Sector 1864561 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:50 Failed to read Sector 1864562 - No Seek Complete

W 14:05:50 Sector 1864562 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:52 Failed to read Sector 1864563 - No Seek Complete

W 14:05:52 Sector 1864563 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:54 Failed to read Sector 1864564 - No Seek Complete

W 14:05:54 Sector 1864564 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:55 Failed to read Sector 1864565 - No Seek Complete

W 14:05:55 Sector 1864565 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:57 Failed to read Sector 1864566 - No Seek Complete

W 14:05:57 Sector 1864566 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:05:59 Failed to read Sector 1864567 - No Seek Complete

W 14:05:59 Sector 1864567 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:02 Failed to read Sector 1864568 - No Seek Complete

W 14:06:02 Sector 1864568 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:03 Failed to read Sector 1864569 - No Seek Complete

W 14:06:03 Sector 1864569 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:05 Failed to read Sector 1864570 - No Seek Complete

W 14:06:05 Sector 1864570 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:10 Failed to read Sector 1864571 - No Seek Complete

W 14:06:10 Sector 1864571 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:12 Failed to read Sector 1864572 - No Seek Complete

W 14:06:12 Sector 1864572 maps to File: VIDEO_TS\VTS_01_4.VOB

W 14:06:14 Failed to read Sector 1864573 - No Seek Complete

W 14:06:14 Sector 1864573 maps to File: VIDEO_TS\VTS_01_4.VOB

E 14:06:18 Failed to read Sector 1864574 - No Seek Complete

E 14:06:18 Sector 1864574 maps to File: VIDEO_TS\VTS_01_4.VOB

E 14:06:18 Failed to Verify Sectors!

E 14:06:18 Operation Failed! - Duration: 00:05:56

I 14:06:18 Average Verify Rate: 10.504 KB/s (7.6x) - Maximum Verify Rate: 22.387 KB/s (16.2x)

 

The media used is Verbatim btw...Any ideas what could be wrong? Firmware is "Liggy's ND3550 Bitsetting Firmware 1.06".

 

 

- trikztar

Edited October 19, 2006 by trikztar

[LIGHTNING UK!]

If all write speeds give verify errors and those are genuine verbatim discs (and not a duff batch), I'd have to say your drive is faulty and producing bad burns (or it just can't read back properly).

[trikztar]

If all write speeds give verify errors and those are genuine verbatim discs (and not a duff batch), I'd have to say your drive is faulty and producing bad burns (or it just can't read back properly).

 

Thanks for answering so fast. I forgot to mention that the exact same thing happens on my laptop which also has an NEC burner installed (and has the same software setup as my stationary pc). I'm wondering if it could be a software issue of sorts, since I've had trouble burning audio cd's as well (not imgburn since the audio cd problems occured before installing that) - they've all been flawed as well...Hm, I guess It's not the right place to asker further questions, since imgburn probably isn't the issue here

 

 

- trikztar

[Shamus_McFartfinger]

You're probably right. (Not that we're biased at all) Before ImgBurn version 2.1.0.0 came out, we were burning like madmen trying to break it with various old and new burners, operating systems, weird image files, flogging source drives to death and then queueing up a burn (starving destination drives of data and causing buffer underruns) and the like. (I even created a 400gig ISO to see if it'd fall over during the build stage, which it didn't). What I'm getting at is that if there's a problem with ImgBurn, we'd likely have found it before it was released by The Great One.

 

If you need help with other things outside the scope of the ImgBurn forum, drop a line in the chat forum. That's what it's there for.