Atcair Posted February 18, 2009 Posted February 18, 2009 I downloaded a DVD torrent and tried to burn it to a disk. I have done this several times without error except this one disk. It burns fine but during the Verify part I get errors. The disk will play sections but locks up during other sections. I have tried 2 different blank disks and it failed both times. I verified the downloaded files are correct. What could I be missing? I'm just not sure where things could be going wrong since other disks done the exact same way work fine. I apologize if this is my error in advance but I am a bit new at this. Here's the log for the errors: I 21:18:55 Source File Implementation Identifier: ImgBurn I 21:18:55 Source File File System(s): ISO9660, UDF (1.02) I 21:18:55 Destination Device: [3:0:0] MAD DOG MD-16X3DVD9-8X 1.F2 (D:) (ATA) I 21:18:55 Destination Media Type: DVD+R (Disc ID: PRODISC-R03-03) (Speeds: 2.4x, 4x, 6x, 8x, 12x) I 21:18:55 Destination Media Sectors: 2,295,104 I 21:18:55 Write Mode: DVD I 21:18:55 Write Type: DAO I 21:18:55 Write Speed: MAX I 21:18:55 DVD+R Reserve Track: Yes I 21:18:55 Link Size: Auto I 21:18:55 Test Mode: No I 21:18:55 OPC: No I 21:18:55 BURN-Proof: Enabled D 21:18:55 Logical Unit Most Desirable Link Size: 16 D 21:19:18 Device Buffer Size: 1,769,472 bytes. D 21:19:18 Device Buffer Available: 0 bytes. I 21:19:18 Filling Buffer... (40 MB) I 21:19:19 Writing LeadIn... I 21:19:20 Writing Session 1 of 1... (1 Track, LBA: 0 - 1790143) I 21:19:20 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1790143) I 21:34:44 Synchronising Cache... I 21:34:45 Closing Track... I 21:34:46 Finalising Disc... I 21:35:12 Exporting Graph Data... I 21:35:12 Graph Data File: C:\Documents and Settings\ko\Application Data\ImgBurn\Graph Data Files\MAD_DOG_MD-16X3DVD9-8X_1.F2_TUESDAY-FEBRUARY-17-2009_9-18_PM_PRODISC-R03-03_MAX.ibg I 21:35:12 Export Successfully Completed! I 21:35:12 Operation Successfully Completed! - Duration: 00:16:16 I 21:35:12 Average Write Rate: 3,878 KB/s (2.8x) - Maximum Write Rate: 11,684 KB/s (8.4x) I 21:35:12 Cycling Tray before Verify... I 21:35:43 Device Ready! I 21:35:50 Operation Started! I 21:35:50 Source Device: [3:0:0] MAD DOG MD-16X3DVD9-8X 1.F2 (D:) (ATA) I 21:35:50 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: PRODISC-R03-03) (Speeds: 2.4x, 4x, 6x, 8x, 12x) I 21:35:50 Image File: -==/\/[bUILD IMAGE]\/\==- I 21:35:50 Image File Sectors: 1,790,144 (MODE1/2048) I 21:35:50 Image File Size: 3,666,214,912 bytes I 21:35:50 Image File Volume Identifier: Lick Library - Guns & Roses - Disk One I 21:35:50 Image File Application Identifier: IMGBURN V2.4.2.0 - THE ULTIMATE IMAGE BURNER! I 21:35:50 Image File Implementation Identifier: ImgBurn I 21:35:50 Image File File System(s): ISO9660, UDF (1.02) I 21:35:50 Read Speed (Data/Audio): MAX / MAX I 21:35:50 Verifying Session 1 of 1... (1 Track, LBA: 0 - 1790143) I 21:35:50 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 1790143) W 21:37:16 Failed to Read Sector 0 - Reason: No Seek Complete W 21:37:21 Failed to Read Sector 1 - Reason: No Seek Complete W 21:37:24 Failed to Read Sector 2 - Reason: No Seek Complete W 21:37:28 Failed to Read Sector 3 - Reason: No Seek Complete E 21:37:32 Failed to Read Sector 4 - Reason: No Seek Complete E 21:37:32 Failed to Verify Sectors! I 21:37:32 Exporting Graph Data... I 21:37:32 Graph Data File: C:\Documents and Settings\JD\Application Data\ImgBurn\Graph Data Files\MAD_DOG_MD-16X3DVD9-8X_1.F2_TUESDAY-FEBRUARY-17-2009_9-18_PM_PRODISC-R03-03_MAX.ibg I 21:37:32 Export Successfully Completed! E 21:37:32 Operation Failed! - Duration: 00:01:42 I 21:37:32 Average Verify Rate: 0 KB/s (0.0x) - Maximum Verify Rate: 0 KB/s (0.0x) I 21:39:52 Close Request Acknowledged I 21:39:52 Closing Down... I 21:39:52 Shutting down SPTI... I 21:39:52 ImgBurn closed!
LIGHTNING UK! Posted February 18, 2009 Posted February 18, 2009 Use better discs (Taiyo Yuden or Verbatim), slow the burn down to 8x. At the moment your drive is just producing coasters.
Atcair Posted February 18, 2009 Author Posted February 18, 2009 Use better discs (Taiyo Yuden or Verbatim), slow the burn down to 8x. At the moment your drive is just producing coasters. I'm using Sont disks now. Is it bad disks? I've burned 10 or 15 other dvd's without an issue. Is that what the log will show when a disk is bad? Thanks
LIGHTNING UK! Posted February 18, 2009 Posted February 18, 2009 It's the dye that's important on a disc and yours are using 'PRODISC-R03-03'. Prodisc is just cheapo lower quality one. The drive isn't reporting any problems during the burn but it's unable to read back what it just wrote as the Verify phase kicks in.
Atcair Posted February 24, 2009 Author Posted February 24, 2009 It's the dye that's important on a disc and yours are using 'PRODISC-R03-03'. Prodisc is just cheapo lower quality one. The drive isn't reporting any problems during the burn but it's unable to read back what it just wrote as the Verify phase kicks in. So a failed verify is a bad disk? I guess that is why I am confused. I was thinking there was an error with the files or the way they were uploaded. Thanks
Shamus_McFartfinger Posted February 25, 2009 Posted February 25, 2009 So a failed verify is a bad disk? I guess that is why I am confused. I was thinking there was an error with the files or the way they were uploaded.Thanks Just to clarify what Lightning_UK! has said. In simple terms, a verification error means what it sounds like. Your burner either can't verify that the disk being burnt is readable (read errors) or that ImgBurn can't match the files you've selected to be burned (via a byte-by-byte comparison of the source and destination file). ProDisc media is garbage. There's no substitute for good media. That said, all burning programs such as ImgBurn and Ner0 send a set of instructions to your drive. Nothing more. They tell the drive what to do and then the drive takes over. It's up to your burner (using its internal software or "firmware") and your media to do the job properly. If your media is crap, the drive will refuse to burn. Your drive then reports an error that ImgBurn displays in its logfile.
Recommended Posts