Jump to content

Recommended Posts

Posted

Four months ago I replaced my 3 year old Pioneer DVD burner with a new DVR-113NP. The first 30 or so burns were flawless.

All of a sudden, about 1 out of every 4 is failing verify because of a "No Seek Complete" error. I only use Verbatim DLs manufactured in

Singapore for dual layers and Taiyos for SL, all purchased from Rima.com. The drive is at firmware v1.01 and I'm using ImgBurn v2.4.2.0.

The log looks normal until it fails during verify.

 

Any thoughts or suggestions?

 

 

Thanks.

Harlock

Posted

As requested, here is the log. I'm not sure how your suggestion to upgrade would help resolve this issue.

Everything has worked fine with the older version until now.

 

I 19:11:06 Operation Started!

I 19:11:06 Source File: D:\DVDs\XXXX\XXXX.MDS

I 19:11:06 Source File Sectors: 3,332,735 (MODE1/2048)

I 19:11:06 Source File Size: 6,825,441,280 bytes

I 19:11:06 Source File Volume Identifier: XXXX

I 19:11:06 Source File Volume Set Identifier: 372c928f

I 19:11:06 Source File Implementation Identifier: Sonic Scenarist 3.1

I 19:11:06 Source File File System(s): ISO9660, UDF (1.02)

I 19:11:06 Destination Device: [1:1:0] PIONEER DVR-113NP 1.01 (F:) (ATA)

I 19:11:06 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2x, 4x, 6x, 8x)

I 19:11:06 Destination Media Sectors: 4,173,824

I 19:11:06 Write Mode: DVD

I 19:11:06 Write Type: DAO

I 19:11:06 Write Speed: 4x

I 19:11:06 Link Size: Auto

I 19:11:06 Test Mode: No

I 19:11:06 OPC: No

I 19:11:06 BURN-Proof: Enabled

I 19:11:06 Optimal L0 Data Zone Capacity: 1,923,184

I 19:11:06 Optimal L0 Data Zone Method: Copied From Original Disc

I 19:11:49 Filling Buffer... (20 MB)

I 19:11:49 Writing LeadIn...

I 19:11:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 3332734)

I 19:11:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3332734)

I 19:11:53 Writing Layer 0... (LBA: 0 - 1923183)

I 19:23:58 Writing Layer 1... (LBA: 1923184 - 3332734)

I 19:32:59 Synchronising Cache...

I 19:33:11 Closing Track...

I 19:33:16 Finalising Disc...

I 19:37:13 Image MD5: 0d6abcd3427ab3f6aa99b3afd683589e

I 19:37:13 Operation Successfully Completed! - Duration: 00:26:07

I 19:37:13 Average Write Rate: 5,269 KB/s (3.8x) - Maximum Write Rate: 5,566 KB/s (4.0x)

I 19:37:13 Cycling Tray before Verify...

W 19:37:20 Waiting for device to become ready...

I 19:37:58 Device Ready!

I 19:38:02 Operation Started!

I 19:38:02 Source Device: [1:1:0] PIONEER DVR-113NP 1.01 (F:) (ATA)

I 19:38:02 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2x, 4x, 6x, 8x)

I 19:38:02 Image File: D:\DVDs\XXXX\XXXX.MDS

I 19:38:02 Image File Sectors: 3,332,735 (MODE1/2048)

I 19:38:02 Image File Size: 6,825,441,280 bytes

I 19:38:02 Image File Volume Identifier: XXXX

I 19:38:02 Image File Volume Set Identifier: 372c928f

I 19:38:02 Image File Implementation Identifier: Sonic Scenarist 3.1

I 19:38:02 Image File File System(s): ISO9660, UDF (1.02)

I 19:38:02 Read Speed (Data/Audio): MAX / MAX

I 19:38:02 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3332734)

I 19:38:02 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3332734)

I 19:38:02 Verifying Layer 0... (LBA: 0 - 1923183)

I 19:46:18 Verifying Layer 1... (LBA: 1923184 - 3332734)

E 19:54:37 Failed to Read Sector 1923200 - Reason: No Seek Complete

E 19:54:37 Sector 1923200 maps to File: \VIDEO_TS\VTS_01_4.VOB

E 19:54:37 Failed to Verify Sectors!

E 19:54:37 Operation Failed! - Duration: 00:16:34

I 19:54:37 Average Verify Rate: 3,869 KB/s (2.8x) - Maximum Verify Rate: 11,128 KB/s (8.0x)

 

 

Thanks for the help.

Harlock

Posted

Thanks for the response.

 

It is a brand new drive, so I'd be surprised if it needs cleaned already, but I'm

willing to try it. What is the best way to clean a drive these days? It's been a while

since I've done it.

 

Do you think a dirty drive would account for the random verify failures? I think I'd lean

towards a bad lot of DVDs, which is unusual for the Verbatims.

 

 

Thanks.

Harlock

Posted

Ah, so you've got an old new drive. I say 'old' because the current model is 117.

 

Like you say, if it's new then I very much doubt it needs cleaning.

 

The random failures would either be because the drive is just shit or because the batch of Verbatims aren't the quality they should be.

 

Try some of the other 'supported' write speeds. Maybe it'll do a better job?

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.