OrionsQwest Posted October 3, 2008 Share Posted October 3, 2008 i have been using this program for awhile, great prog Btw, but today i got a failed burn, i usually get thelocking the drive prob,that i just eject the disk and it usually works, but i got a error today, before i paste, i use verbatims so i dont think its the disk, please help, i only have like 3 disk left and i just used one for a coaster, thanks guys. I 19:03:42 Microsoft Windows Vista Ultimate Edition (6.0, Build 6001 : Service Pack 1) I 19:03:42 Total Physical Memory: 2,094,792 KB - Available: 936,256 KB W 19:03:42 Drive H:\ (FAT32) does not support single files > 4 GB in size. W 19:03:42 Drive I:\ (FAT32) does not support single files > 4 GB in size. I 19:03:42 Initialising SPTI... I 19:03:42 Searching for SCSI / ATAPI devices... I 19:03:43 Found 1 DVD-ROM and 1 BD-RE! I 19:04:01 Operation Started! II 19:04:01 Source File Sectors: 3,825,924 (MODE1/2048) I 19:04:01 Source File Size: 7,835,492,352 bytes I 19:04:01 Source File Volume Identifier: XGD2DVD_NTSC I 19:04:01 Source File Volume Set Identifier: 34672923 I 19:04:01 Source File Implementation Identifier: Sonic Scenarist 3.1 I 19:04:01 Source File File System(s): ISO9660, UDF (1.02) I 19:04:01 Destination Device: [1:0:0] MATSHITA BD-MLT UJ-225S Q110 (F:) (ATA) I 19:04:01 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2.4x) I 19:04:01 Destination Media Sectors: 4,173,824 I 19:04:01 Write Mode: DVD I 19:04:01 Write Type: DAO I 19:04:01 Write Speed: 2.4x I 19:04:01 Link Size: Auto I 19:04:01 Test Mode: No I 19:04:01 OPC: No I 19:04:01 BURN-Proof: Enabled I 19:04:01 Optimal L0 Data Zone Capacity: 1,913,760 I 19:04:01 Optimal L0 Data Zone Method: Copied From Original Disc I 19:04:26 Filling Buffer... (40 MB) I 19:04:27 Writing LeadIn... I 19:04:28 Writing Session 1 of 1... (1 Track, LBA: 0 - 3825923) I 19:04:28 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923) I 19:04:28 Writing Layer 0... (LBA: 0 - 1913759) I 19:24:17 Writing Layer 1... (LBA: 1913760 - 3825923) W 19:24:21 Failed to Write Sectors 1917504 - 1917535 - Reason: No Write Current W 19:24:21 Retrying (1 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (2 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (3 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (4 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (5 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (6 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (7 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (8 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (9 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (10 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (11 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (12 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (13 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (14 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (15 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (16 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (17 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (18 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (19 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:24:21 Retrying (20 of 20)... W 19:24:21 Retry Failed - Reason: Unable to Recover TOC W 19:40:47 Retrying (21)... W 19:40:47 Retry Failed - Reason: Unable to Recover TOC E 19:40:49 Failed to Write Sectors 1917504 - 1917535 - Reason: No Write Current I 19:40:49 Synchronising Cache... W 19:40:55 User opted to skip the 'Close Track/Session/Disc' functions. E 19:40:55 Failed to Write Image! I 19:40:55 Exporting Graph Data... I 19:40:55 Graph Data File: C:\Users\Matt\AppData\Roaming\ImgBurn\Graph Data Files\MATSHITA_BD-MLT_UJ-225S_Q110_THURSDAY-OCTOBER-02-2008_7-04_PM_MKM-001-00_2.4x.ibg I 19:40:55 Export Successfully Completed! E 19:40:55 Operation Failed! - Duration: 00:36:53 I 19:40:55 Average Write Rate: 1,759 KB/s (1.3x) - Maximum Write Rate: 3,399 KB/s (2.5x) k tks Link to comment Share on other sites More sharing options...
blutach Posted October 3, 2008 Share Posted October 3, 2008 Check your firmware is up to date. But I have to say, that is not one of the most reliable drives out there. Regards Link to comment Share on other sites More sharing options...
OrionsQwest Posted October 3, 2008 Author Share Posted October 3, 2008 i will check firmware,tks,actually though this drives been pretty good, havent had hardly any probs with it, and i've used it a bit, ill check firmware though Link to comment Share on other sites More sharing options...
OrionsQwest Posted October 3, 2008 Author Share Posted October 3, 2008 i just re burnt and it worked, actually had a restart i was putting off from a windows update,maybe screwed it up, anyways all seet tks Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 3, 2008 Share Posted October 3, 2008 Fluke bad burn - defect in the dye perhaps or dirt on the disc, nothing to worry about. Do as you say you've done and just burn it again. Link to comment Share on other sites More sharing options...
Recommended Posts