Jump to content

Burning Errors - Dual Layer Dvd+R


Winston
 Share

Recommended Posts

I would appreciate any help anyone can provide...I've just recently started having issues burning only dual layered DVD+R

discs. Regular dvd burns just fine, as do 25gb & 50gb blu-ray discs. I've burned 35 of these discs with no coasters, but

suddenly i'm having issues. The drive is a super Slim Drive USB3.0 model purchased on Amazon. Model ODP95-SU3

After reading the DL layer FAQ, it seems these slim, external laptop style drives are not great. The discs are GIGABLOCK

brand dvd+r discs, rated at 8X.

 

The error i'm getting is: Set L0 Data Zone Capacity Failed! Reason: ID CRC or ECC Error

The logs is as follows...

I 14:03:17 ImgBurn Version 2.5.8.0 started!
I 14:03:17 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 14:03:17 Total Physical Memory: 67,038,552 KiB  -  Available: 58,335,276 KiB
I 14:03:17 Initialising SPTI...
I 14:03:17 Searching for SCSI / ATAPI devices...
I 14:03:17 -> Drive 1 - Info: MATSHITA BD-MLT UJ272 1.01 (F:) (USB 2.0)
I 14:03:17 Found 1 BD-RE XL!
I 14:04:43 Operation Started!
I 14:04:43 Source File: D:\@Films\Dune (1984) Alternative Edition Redux [fanedit][DVD-9][2h58m]\DUNEALTRDXDISC.MDS
I 14:04:43 Source File Sectors: 4,165,440 (MODE1/2048)
I 14:04:43 Source File Size: 8,530,821,120 bytes
I 14:04:43 Source File Volume Identifier: DUNEALTRDX
I 14:04:43 Source File Volume Set Identifier: 40EF5DEE003F8F3E
I 14:04:43 Source File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER!
I 14:04:43 Source File Implementation Identifier: ImgBurn
I 14:04:43 Source File File System(s): ISO9660, UDF (1.02)
I 14:04:43 Destination Device: [0:0:0] MATSHITA BD-MLT UJ272 1.01 (F:) (USB)
I 14:04:43 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67)
I 14:04:43 Destination Media Supported Write Speeds: 2.4x
I 14:04:43 Destination Media Sectors: 4,173,824
I 14:04:43 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)
I 14:04:43 Write Mode: DVD
I 14:04:43 Write Type: DAO
I 14:04:43 Write Speed: 4x
I 14:04:43 DVD+R DL Reserve Track: No
I 14:04:43 Link Size: Auto
I 14:04:43 Lock Volume: Yes
I 14:04:43 Test Mode: No
I 14:04:43 OPC: No
I 14:04:43 BURN-Proof: Enabled
W 14:04:43 Write Speed Miscompare! - Wanted: 5,540 KB/s (4x), Got: 3,324 KB/s (2.4x)
W 14:04:43 The drive only supports writing these discs at 2.4x.
I 14:04:43 Optimal L0 Data Zone Capacity: 2,082,720
I 14:04:43 Optimal L0 Data Zone Method: Copied From Original Disc
W 14:05:22 Set L0 Data Zone Capacity Failed! - Reason: ID CRC or ECC Error
E 14:05:51 Set L0 Data Zone Capacity Failed! - Reason: ID CRC or ECC Error
E 14:05:51 Operation Failed! - Duration: 00:01:08
I 14:05:51 Average Write Rate: N/A - Maximum Write Rate: N/A

I've no idea whats going on, unless suddenly the drive doesn't like this cheap media.

thanks,

 

Winston

 

Link to comment
Share on other sites

Well, you could have one of two issues or a combination of both.  As was noted in the FAQ, slim models tend to be junk.  It could have simply given up the ghost.  As you note, Ritek/Ricoh media can be cheap discs.  Depending on where you live in the world, it can be either decent 2nd tier quality media or junk.  It could just be you got lucky 35 times in a row as the nature of cheap media means something you get a burn that works and sometimes you don't.

 

Given you had no problems up until recently, it seems less likely the problem would be cheap media and more likely a problem of a cheap slim drive model burner.

Link to comment
Share on other sites

First, thanks for the reply. One thing of note, is all other media burns just fine on this drive. Is it normal that a drive

would start having issues burning one type of disc, and not the other? Also, I have 2 of these drives, and they both

suddenly have the same issue. Which made me think it might be the pc, the software settings, or obviously the media.

I guess my first test would be try a better quality DL disc type.

thanks again.

Winston

Link to comment
Share on other sites

It is entirely within my experience that a drive can work with all other kinds of media but one particular one and need replacing.  For instance, a BD burner has 2 lasers: one for CD and DVD and one for BD.  So, it can be a case where BD works and CD or DVD don't and CD and DVD are fine but BD aren't.  And even in DVD only burners, it has been my experience that DVD+R DL function will fail first but SL media burn fine.

 

It is generally not a case where PC's have gone wrong that cause bad burns.  It's either the drive or the media.

 

Since you said you had 2 of these drives and got the same results, the problem is most likely a combination of that media you're using in the drive you're using.  You could try and see if there's a firmware update for your drive that might be better compatibility with the media.  In Write mode, right click on the drive you're burning to and choose the last option in the context menu to check for firmware updates.

Link to comment
Share on other sites

Thank for the reply. I tried the firmware update, and my exact models doesn't show up. MATSHITA BD-MLT UJ272 (firmware 1.01)

One thing that struck me as odd, and it may be that I'm uneducated about most of this stuff. When I boot up the imgburn software,

I get the following, and it shows Windows 8. Is this supposed to be the O.S. i'm running? I ask because I'm running Windows 10.

I 18:13:55 ImgBurn Version 2.5.8.0 started!
I 18:13:55 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 18:13:55 Total Physical Memory: 67,038,552 KiB  -  Available: 56,122,924 KiB
I 18:13:55 Initialising SPTI...
I 18:13:55 Searching for SCSI / ATAPI devices...
I 18:13:55 -> Drive 1 - Info: MATSHITA BD-MLT UJ272 1.01 (F:) (USB 2.0)
I 18:13:55 Found 1 BD-RE XL!

thanks again,

 

Winston

Link to comment
Share on other sites

I didn't think the updating firmware would work.  Most external drives rarely have firmware updates released for them.  Don't know why.

 

The Windows 10 recognized as Windows 8 is a holdover from how old ImgBurn's last gold release was.  Between Windows 8 and Windows 10, Microsoft changed how Windows identifies itself.  ImgBurn simply doesn't have the necessary code to differentiate Windows 10 yet.  So, that's normal.  This will be addressed in the next version.  Of course, I can't say when that will be, obviously.

Link to comment
Share on other sites

ah, thanks for the info. I did find some sites with firmware updates for other similar Matshita units, just not mine.

I was told by the seller it typically doesn't have updates like you mentioned.

 

thanks,

 

Win

Link to comment
Share on other sites

Well, i was able to get some VERBATIM discs, as suggested, but i'm still having errors. The first discs I burned progressed about 70% before an error.

The second discs gave me this error, which I've attached, and here is the log.....Anyone have any suggestions?

thanks,

Win

I 13:07:11 ImgBurn Version 2.5.8.0 started!
I 13:07:11 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 13:07:11 Total Physical Memory: 67,038,552 KiB  -  Available: 57,971,684 KiB
I 13:07:11 Initialising SPTI...
I 13:07:11 Searching for SCSI / ATAPI devices...
I 13:07:11 -> Drive 1 - Info: MATSHITA BD-MLT UJ272 1.01 (F:) (USB 2.0)
I 13:07:11 Found 1 BD-RE XL!
I 13:07:43 Operation Started!
I 13:07:43 Source File: D:\@Films\Dune (1984) Alternative Edition Redux [fanedit][DVD-9][2h58m]\DUNEALTRDXDISC.MDS
I 13:07:43 Source File Sectors: 4,165,440 (MODE1/2048)
I 13:07:43 Source File Size: 8,530,821,120 bytes
I 13:07:43 Source File Volume Identifier: DUNEALTRDX
I 13:07:43 Source File Volume Set Identifier: 40EF5DEE003F8F3E
I 13:07:43 Source File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER!
I 13:07:43 Source File Implementation Identifier: ImgBurn
I 13:07:43 Source File File System(s): ISO9660, UDF (1.02)
I 13:07:43 Destination Device: [0:0:0] MATSHITA BD-MLT UJ272 1.01 (F:) (USB)
I 13:07:43 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)
I 13:07:43 Destination Media Supported Write Speeds: 2.4x, 6x
I 13:07:43 Destination Media Sectors: 4,173,824
I 13:07:43 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes)
I 13:07:43 Write Mode: DVD
I 13:07:43 Write Type: DAO
I 13:07:43 Write Speed: MAX
I 13:07:43 DVD+R DL Reserve Track: No
I 13:07:43 Link Size: Auto
I 13:07:43 Lock Volume: Yes
I 13:07:43 Test Mode: No
I 13:07:43 OPC: No
I 13:07:43 BURN-Proof: Enabled
I 13:07:43 Write Speed Successfully Set! - Effective: 8,355 KB/s (6x)
I 13:07:43 Optimal L0 Data Zone Capacity: 2,082,720
I 13:07:43 Optimal L0 Data Zone Method: Copied From Original Disc
I 13:08:16 Set L0 Data Zone Capacity Succeeded!
I 13:08:16 L0 Data Zone Capacity - Effective: 2,082,720
I 13:08:16 Filling Buffer... (80 MiB)
I 13:08:17 Writing LeadIn...
I 13:08:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 4165439)
I 13:08:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 4165439)
I 13:08:22 Writing Layer 0... (LBA: 0 - 2082719)
I 13:18:29 Writing Layer 1... (LBA: 2082720 - 4165439)
W 13:21:59 Failed to Write Sectors 2877056 - 2877087 - Reason: Peripheral Device Write Fault
W 13:21:59 Retrying (1 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (2 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (3 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (4 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (5 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (6 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (7 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (8 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (9 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (10 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (11 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (12 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (13 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (14 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (15 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (16 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (17 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (18 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (19 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:21:59 Retrying (20 of 20)...
W 13:21:59 Retry Failed - Reason: Unable to Recover TOC
W 13:22:58 Retrying (21)...
W 13:22:58 Retry Failed - Reason: Unable to Recover TOC
W 13:22:59 Retrying (22)...
W 13:22:59 Retry Failed - Reason: Unable to Recover TOC
E 13:23:16 Failed to Write Sectors 2877056 - 2877087 - Reason: Peripheral Device Write Fault
I 13:23:16 Synchronising Cache...
I 13:23:23 Closing Track...
W 13:23:23 Close Track Failed! - Reason: Unable to Recover TOC
W 13:23:26 Retrying (1)...
E 13:23:27 Close Track Failed! - Reason: Unable to Recover TOC
I 13:23:27 Finalising Disc...
W 13:23:27 Finalise Disc Failed! - Reason: Unable to Recover TOC
W 13:23:28 Finalise Disc Failed! - Reason: Unable to Recover TOC
E 13:23:28 Failed to Write Image!
I 13:23:28 Exporting Graph Data...
I 13:23:28 Graph Data File: C:\Users\Winston\AppData\Roaming\ImgBurn\Graph Data Files\MATSHITA_BD-MLT_UJ272_1.01_SATURDAY-MARCH-6-2021_1-07_PM_MKM-003-00_MAX.ibg
I 13:23:28 Export Successfully Completed!
E 13:23:28 Operation Failed! - Duration: 00:15:45
I 13:23:28 Average Write Rate: 6,436 KiB/s (4.8x) - Maximum Write Rate: 8,202 KiB/s (6.1x)

 

ImgBurnError.jpg

Link to comment
Share on other sites

You've got a slim drive.  Slim drives are notorious for being a lot of junk.  Your best solution is replacing the drive, since at this point, the problem is mostly down to the drive.  It doesn't like any DL you've thrown at it.  Don't replace it with another slim model, though.  Best to get a half height 5.25" burner and put it in an external USB enclosure, like I do.  Plus, Matshita is known for making shita drives.  You can, of course, keep trying multiple slim models hoping you get a good one.  Like LG's slim internal BD burner, BU40N, in my Dell is, even though it became useless after a short amount of time because the cap holding discs in place keeps popping off.  But, then, you'd have to find a slim model external enclosure, which I know nothing about.

Link to comment
Share on other sites

Thanks for the quick reply. I was finally able to get a Verbatim disc to burn properly. I think in my adjustment of settings, I changed the I/O settings to the Microsoft SPTI interface.

I changed it to the ElbyCDIO - Elaborate Bytes interface, and was able to get a good burn. I'll keep an eye on in the future, as see if discs continue to burn proeprly.

 

thanks again

Winston

Link to comment
Share on other sites

Yes, that shouldn't really matter what interface you use.  You generally change interfaces, though, when one might be a problem and another works better.  So, maybe in your case, it helped.  I would generally only change interfaces if one particular one offers additional features and options.  Elby's does over SPTI, though.

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

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