Hello, I was told to ask here from the good folks at the AnyDVD HD forums.
I tried to burn the ISO of IT (original film on BR) to a 50gig disc) and got a coaster.
Any advice?
Thanks.
Edited by NewUserGuy1, 10 December 2017 - 10:49 PM.
Read the Guides forum if you don't know how to do something.
If you have a question or a problem, check the FAQ and use the Search to see if you can find the answer for yourself.
If you're having trouble burning double layer media, read Here.
Still stuck? Create a new thread and describe your issue in detail.
Make sure you include a copy of the program's log in your post. No log =
Posted 10 December 2017 - 10:09 PM
Edited by Ch3vr0n, 10 December 2017 - 10:11 PM.
Official Dutch (nl-BE) translator for:
Internet Download Manager, ALL Slysoft products, VSO ConvertXtoDVD, various joomla extensions & components
Posted 10 December 2017 - 10:45 PM
Edited by NewUserGuy1, 11 December 2017 - 03:10 AM.
Posted 11 December 2017 - 09:21 AM
Posted 11 December 2017 - 06:48 PM
Could be the LG burner you're using. I've tried 5 different LG BD burners for burning Verbatim good quality BD-RE DL and only 1 didn't fail Verify. So, I've come to the conclusion that LG drives are not good at writing BD DL media. Now, I've never burned a BD-R DL before, but I would think if all the LG's I've ever tested BD-RE DL failed more times than succeeded, I would say it's the fault of LG burners.
I only use my Pioneer BD burner for writing BD-RE DL, which writes to them perfectly. So, you may want to try a Pioneer BD drive if you can't get this issue resolved on your LG.
Posted 11 December 2017 - 07:16 PM
Hard to tell with this one as it looks like something is messing up the error codes your drive is actually returning and all the program is getting back is that 'invalid field in cdb' one.
Right click the drive selection box and pick 'family tree'. Close the box that comes up and copy + paste everything from the log window please.
D Drive Family Tree:
Edited by NewUserGuy1, 11 December 2017 - 07:16 PM.
Posted 11 December 2017 - 08:22 PM
Tried two more times and two more coasters.
Even after I updated the LG firmware from 1.02 to 1.03!!! ARGH!!!
Edited by NewUserGuy1, 11 December 2017 - 08:22 PM.
Posted 11 December 2017 - 08:34 PM
I still will fall back on it's the fault of the LG drive.
See this thread for a similar issue that was "resolved."
http://forum.imgburn.com/index.php?/topic/24807-errors-when-verifying/
Posted 11 December 2017 - 08:44 PM
Wait, there's a 1.03 firmware update to that drive? I have that LG drive because it writes properly to all other media except for BD-RE DL and firmwarehq only lists 1.02, my firmware.
Found the firmware on LG's site for the drive. It appears it was just released 3 days ago. After over 3 years of no new firmware updates, it seems LG finally updated this drive. Seems it didn't fix the BD-RE DL issue, but I'll test it out, anyway.
If it makes you feel any better, I, at least, found some useful information from this post. Thanks!
Posted 11 December 2017 - 10:55 PM
If it makes you feel any better, I, at least, found some useful information from this post. Thanks!
You are very welcome .
Now hopefully we can see what's going on. Lightning?
Posted 11 December 2017 - 11:37 PM
The problem is with LG drives and Verbatim BD DL. I updated the firmware to 1.03, performed another BD-RE DL test. Of course, it STILL failed Verify at the layer break change.
I 15:23:00 Operation Started!
I 15:23:00 Source File Sectors: 15,957,344 (MODE1/2048)
I 15:23:00 Source File Size: 32,680,640,512 bytes
I 15:23:00 Source File Volume Set Identifier: 4B8B79FA00F37D0A
I 15:23:00 Source File Application Identifier: ImgBurn v2.5.8.0
I 15:23:00 Source File Implementation Identifier: ImgBurn
I 15:23:00 Source File File System(s): UDF (2.60)
I 15:23:00 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA)
I 15:23:00 Destination Media Type: BD-RE (Disc ID: VERBAT-IM1-000)
I 15:23:00 Destination Media Supported Write Speeds: 2x
I 15:23:00 Destination Media Sectors: 24,438,784
I 15:23:01 Write Mode: BD
I 15:23:01 Write Type: DAO
I 15:23:01 Write Speed: MAX
I 15:23:01 Hardware Defect Management Active: No
I 15:23:01 BD-RE FastWrite: No
I 15:23:01 Link Size: Auto
I 15:23:01 Lock Volume: Yes
I 15:23:01 Test Mode: No
I 15:23:01 OPC: No
I 15:23:01 BURN-Proof: Enabled
I 15:23:01 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x)
I 15:23:02 Filling Buffer... (40 MiB)
I 15:23:03 Writing LeadIn...
I 15:23:27 Writing Session 1 of 1... (1 Track, LBA: 0 - 15957343)
I 15:23:27 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343)
I 15:23:27 Writing Layer 0... (LBA: 0 - 12219391)
I 16:08:25 Writing Layer 1... (LBA: 12219392 - 15957343)
I 16:22:34 Synchronising Cache...
I 16:22:58 Exporting Graph Data...
I 16:22:58 Export Successfully Completed!
I 16:22:58 Operation Successfully Completed! - Duration: 00:59:57
I 16:22:58 Average Write Rate: 9,000 KiB/s (2.1x) - Maximum Write Rate: 9,560 KiB/s (2.2x)
I 16:22:58 Cycling Tray before Verify...
W 16:23:05 Waiting for device to become ready...
I 16:23:20 Device Ready!
I 16:23:24 Operation Started!
I 16:23:24 Source Device: [0:0:0] HL-DT-ST BD-RE WH16NS40 1.03 (S:) (SATA)
I 16:23:24 Source Media Type: BD-RE (Disc ID: VERBAT-IM1-000)
I 16:23:24 Source Media Supported Read Speeds: 2x, 4x, 6x
I 16:23:24 Source Media Supported Write Speeds: 2x
I 16:23:24 Source Media Sectors: 24,438,784
I 16:23:24 Source Media Size: 50,050,629,632 bytes
I 16:23:24 Image File Sectors: 15,957,344 (MODE1/2048)
I 16:23:24 Image File Size: 32,680,640,512 bytes
I 16:23:24 Image File Volume Identifier: 12 - December
I 16:23:24 Image File Volume Set Identifier: 4B8B79FA00F37D0A
I 16:23:24 Image File Application Identifier: ImgBurn v2.5.8.0
I 16:23:24 Image File Implementation Identifier: ImgBurn
I 16:23:24 Image File File System(s): UDF (2.60)
I 16:23:24 Read Speed (Data/Audio): MAX / MAX
I 16:23:25 Read Speed - Effective: 2x - 6x, 6x - 2x
I 16:23:25 Verifying Session 1 of 1... (1 Track, LBA: 0 - 15957343)
I 16:23:25 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 15957343)
I 16:23:25 Verifying Layer 0... (LBA: 0 - 12219391)
I 16:59:06 Verifying Layer 1... (LBA: 12219392 - 15957343)
W 16:59:10 Failed to Read Sectors 12219616 - 12219647 - Reason: L-EC Uncorrectable Error
W 16:59:16 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error
W 16:59:16 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg
E 17:31:27 Failed to Read Sector 12219616 - Reason: L-EC Uncorrectable Error
E 17:31:27 Sector 12219616 maps to File: \12 - December\12 - December-00-03.mrimg
E 17:31:27 Failed to Verify Sectors!
I 17:31:33 Exporting Graph Data...
I 17:31:33 Export Successfully Completed!
E 17:31:33 Operation Failed! - Duration: 01:08:03
I 17:31:33 Average Verify Rate: 5,987 KiB/s (1.4x) - Maximum Verify Rate: 32,591 KiB/s (7.4x)
Notice how it failed Verify with less than 300 sectors into the 2nd layer? The issue is an inherent problem with LG drives and (at least) Verbatim BD-RE DL. Since it happens on your drive, too, it happens on all Verbatim BD-R DL and BD-RE DL. And it may even happen on ALL manufacturers of BD DL media.
Nothing had ever been written to this Verbatim BD-RE DL before. It had only been "written once" when it was formatted in a Pioneer drive. So, it's highly unlikely the disc is bad. And it's highly unlikely that the Pioneer formatted it wrong because the Pioneer and my USB ASUS write to these kinds of discs fine. Only the 5 LG's I've tested do this. They all fail Verify except for one Verify, and the contents were NOT written correctly to the disc when I compared the written contents with the source. Ergo, the problem is with all LG drives. QED.
Posted 11 December 2017 - 11:44 PM
Posted 11 December 2017 - 11:47 PM
After that, I'd start looking at various drivers for your SATA controller. Is the bios up-to-date for your motherboard?
Bios up to date. Brand new, top of the line Core I7 7700.
Posted 12 December 2017 - 01:11 AM
Discovered another LG/Verbatim incompatibility after testing more 1.03 media burns. The LG's never liked writing to Verbatim 6x DVD-RW media, either. 1.03 does nothing to fix this. They still fail at the, guess where? Verify! My Pioneer writes them fine.
Posted 12 December 2017 - 03:01 AM
I just ordered this Pioneer: https://www.amazon.com/gp/product/B00GD792US/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1
Wills see how it works and if better, will return the LG.
Posted 12 December 2017 - 03:30 AM
Good to have both on hand. That way, when you get one, you can test it and if it doesn't work, send it back. Then, you'll have the other on hand, too, to try next.
That model of Pioneer is the one I have always used. In fact, I have 2 of them. The 2nd one I got I still use and the first one I got still works. Just sitting around to swap in.
Pioneer's have a few flaws of their own. After a few months, the eject button doesn't always work the first time it's pressed. Pressing it again works. Issuing an Eject command in ImgBurn does the same thing. However, all eject commands issued after a write if directed by ImgBurn seem to work.
The current firmware is borked for Ritek 8x DVD+RW media. However, it's a moot point as you can't find 8x DVD+RW new anymore.
The quality of that drive may have declined if my experience is any indication. I don't know yet. Can only relate my story. As I said, my first 2 drives have performed well. My first is almost 3 years old and still works. My current one is almost 2 years old and still works. The 3rd one I had, though, I had to replace after 7 months. The 4th one I got I had to send back to Amazon.com because it was borked for writing Verbatim BD-R out of the box.
However, with all that said, I'd still recommend trying a Pioneer first for a BD burner.
Posted 12 December 2017 - 06:45 AM
Any additional insight Lightning?
Posted 13 December 2017 - 02:18 PM
Posted 13 December 2017 - 08:09 PM
Thanks for the reply Lightning, but I am confused. Didn't I print your programs error logs? Shouldn't they provide what you need ?
Let me know what you need or if I did not provide the right information.
Thanks again .
Posted 13 December 2017 - 08:13 PM
You did everything right, the issue is that the DRIVE is reporting a generic error (invalid field in cdb) that doesn't mean much, instead of reporting an actual real informative error such as 'write error...'. combining both topics on 2 forums and the fact that you're using quality media, I'd go with faulty drive.Thanks for the reply Lightning, but I am confused. Didn't I print your programs error logs? Shouldn't they provide what you need ?
Let me know what you need or if I did not provide the right information.
Thanks again.
Official Dutch (nl-BE) translator for:
Internet Download Manager, ALL Slysoft products, VSO ConvertXtoDVD, various joomla extensions & components
0 members, 0 guests, 0 anonymous users