bbddpp Posted July 24, 2012 Posted July 24, 2012 (edited) I invested in a few Dual Layer BD-Rs and a new drive (Liteon IHBS112) to backup my precious 3D Blurays. In particular wanted to back up my Avatar since it's still not out and I don't want my only copy to go bad. Installed the drive and upgraded Firmware and Windows 7 installed new driver. Did full power shutdown, restarted, and I got a coaster. First off, OPC failed off the bat but I did a continue figuring that happens sometimes. Ripped down with DVDFab, tested with CloneDVD and mounted, played fine...Then attempted to burn the ISO and bombed out right at LeadIn. This is my first attempt with this disc/drive and TDK TDKBLD-RFB-000 media. I'd hate to waste another one. HELP??? Here's the log: I 17:41:31 ImgBurn Version 2.5.7.0 started! I 17:41:31 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1) I 17:41:31 Total Physical Memory: 4,126,868 KB - Available: 2,360,748 KB I 17:41:31 Initialising SPTI... I 17:41:31 Searching for SCSI / ATAPI devices... I 17:41:31 -> Drive 1 - Info: ATAPI iHBS112 2 PL05 (G:) (ATAPI) I 17:41:31 -> Drive 2 - Info: ELBY CLONEDRIVE 1.4 (F:) (SCSI) I 17:41:31 Found 1 BD-ROM/HD DVD-ROM and 1 BD-RE! I 17:43:14 Operation Started! I 17:43:14 Source File: C:\avatar.iso I 17:43:14 Source File Sectors: 24,438,784 (MODE1/2048) I 17:43:14 Source File Size: 50,050,629,632 bytes I 17:43:14 Source File Volume Identifier: AVATAR_3D I 17:43:14 Source File Volume Set Identifier: 3D2E7CC4RED_BIRD I 17:43:14 Source File Application Identifier: BD Authoring I 17:43:14 Source File Implementation Identifier: MEI I 17:43:14 Source File File System(s): UDF (2.50) I 17:43:14 Destination Device: [0:1:0] ATAPI iHBS112 2 PL05 (G:) (ATAPI) I 17:43:14 Destination Media Type: BD-R (Disc ID: TDKBLD-RFB-000) I 17:43:14 Destination Media Supported Write Speeds: 4x I 17:43:14 Destination Media Sectors: 24,438,784 I 17:43:14 Write Mode: BD I 17:43:14 Write Type: DAO I 17:43:14 Write Speed: 4x I 17:43:14 Hardware Defect Management Active: No I 17:43:14 BD-R Verify Not Required: Yes I 17:43:14 Link Size: Auto I 17:43:14 Lock Volume: Yes I 17:43:14 Test Mode: No I 17:43:14 OPC: Yes I 17:43:14 BURN-Proof: Enabled I 17:43:16 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x) I 17:43:16 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes W 17:44:18 Optimum Power Calibration Failed! - Reason: Timeout on Logical Unit W 17:44:20 Optimum Power Calibration Failed! - Reason: Timeout on Logical Unit I 17:44:21 Filling Buffer... (258 MB) I 17:44:25 Writing LeadIn... W 17:46:18 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write W 17:46:18 Retrying (1 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (2 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (3 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (4 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (5 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (6 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (7 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (8 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (9 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (10 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (11 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (12 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (13 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (14 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (15 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (16 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (17 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (18 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (19 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write W 17:46:18 Retrying (20 of 20)... W 17:46:18 Retry Failed - Reason: Invalid Address For Write E 17:47:47 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write E 17:47:47 Next Writable Address: 0 I 17:47:47 Synchronising Cache... W 17:48:38 User opted to skip the 'Close Track/Session/Disc' functions. E 17:48:38 Failed to Write Image! E 17:48:38 Operation Failed! - Duration: 00:05:23 I 17:48:38 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x) Edited July 24, 2012 by bbddpp
ianymaty Posted July 25, 2012 Posted July 25, 2012 Seems the drive don't like the discs. Try other media with different MID/dye than TDKBLD-RFB-000.
bbddpp Posted July 26, 2012 Author Posted July 26, 2012 Seems the drive don't like the discs. Try other media with different MID/dye than TDKBLD-RFB-000. Thanks so much for your reply. I appreciate it. I'm a little bummed at the wasted cash on the media stack -- Is that almost definitely the case? Is it possible moving the drive to a different PC would have a better effect? Could those type of errors burning the lead-in be caused by anything else? Perhaps, a bad ISO rip on my part even? Also, is the fact that it's failing the OPC test that IMGBurn is doing (and warning me before it attempts the burn) a warning sign that it's almost assuredly going to fail, or does the OPC have nothing to do with the actual burn itself? Again I appreciate the time you took to respond, thanks.
ianymaty Posted July 26, 2012 Posted July 26, 2012 You have to try to be sure. Try without OPC to see if it get to the end.
bbddpp Posted July 31, 2012 Author Posted July 31, 2012 Thanks, I'll give that a try - It didn't even start (couldn't pass leadin) before so I have pretty low faith. It'd be fine to test all this stuff if it didn't result in an expensive coaster every time it failed.
LIGHTNING UK! Posted July 31, 2012 Posted July 31, 2012 Unfortunatly, in order to figure out if your drive can complete a full burn to a disc, you have to attempt exactly that. If you want to just check that what you're burning should be playable etc, burning to a BD-RE DL would do the job.
Recommended Posts