Sizzlechest Posted May 3, 2018 Posted May 3, 2018 I've been periodically getting this kind of error on my new LG burner: I 11:47:56 ImgBurn Version 2.5.8.0 started!I 11:47:56 Microsoft Windows 7 Professional x64 Edition (6.1, Build 7601 : Service Pack 1)I 11:47:56 Total Physical Memory: 6,193,436 KiB - Available: 3,280,584 KiBI 11:47:56 Initialising SPTI...I 11:47:56 Searching for SCSI / ATAPI devices...I 11:47:56 -> Drive 1 - Info: HL-DT-ST DVDRAM GH70N UGA0-01 (E:) (ATAPI)I 11:47:57 -> Drive 2 - Info: HL-DT-ST BD-RE WH16NS58 TST4 (F:) (USB 2.0)I 11:47:59 -> Drive 3 - Info: HL-DT-ST BD-RE WH16NS58 TST4 (D:) (USB 2.0)I 11:47:59 Found 1 DVD±RW/RAM and 2 BD-RE XLs!I 11:48:09 Operation Started!I 11:48:09 Source File: U:\Disc Images\MPOE\MPOE 6.0.5.0B1\MPOE 6.0.5.0B1 - Disc 1 of 5 - RHEL 6.8 64-bit DVD.isoI 11:48:09 Source File Sectors: 1,924,219 (MODE1/2048)I 11:48:09 Source File Size: 3,940,800,512 bytesI 11:48:09 Source File Volume Identifier: RHEL 6.1I 11:48:09 Source File Application Identifier: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR © 1993 E.YOUNGDALE © 1997-2006 J.PEARSON/J.SCHILLING © 2006-2007 CDRKIT TEAMI 11:48:09 Source File File System(s): ISO9660 (Bootable), JolietI 11:48:09 Destination Device: [0:0:0] HL-DT-ST BD-RE WH16NS58 TST4 (F:) (USB)I 11:48:09 Destination Media Type: DVD+R (Disc ID: YUDEN000-T02-00)I 11:48:09 Destination Media Supported Write Speeds: 4x, 8xI 11:48:09 Destination Media Sectors: 2,295,104I 11:48:09 Write Mode: DVDI 11:48:09 Write Type: DAOI 11:48:09 Write Speed: MAXI 11:48:09 DVD+R Reserve Track: NoI 11:48:09 Link Size: AutoI 11:48:09 Lock Volume: YesI 11:48:09 Test Mode: NoI 11:48:09 OPC: NoI 11:48:09 BURN-Proof: EnabledI 11:48:09 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)I 11:48:09 Book Type Setting: N/A (Reason: Invalid Command Operation Code)I 11:48:10 Filling Buffer... (80 MiB)I 11:48:13 Writing LeadIn...I 11:48:22 Writing Session 1 of 1... (1 Track, LBA: 0 - 1924218)I 11:48:22 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1924218)W 11:54:34 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase ErrorW 11:54:34 Retrying (1 of 20)...W 11:54:53 Retry Failed - Reason: Invalid Address For WriteW 11:54:53 Retrying (2 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (3 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (4 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (5 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (6 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (7 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (8 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (9 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (10 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (11 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (12 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (13 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (14 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (15 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (16 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (17 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (18 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (19 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteW 11:54:54 Retrying (20 of 20)...W 11:54:54 Retry Failed - Reason: Invalid Address For WriteE 11:55:08 Failed to Write Sectors 1894432 - 1894463 - Reason: Data Phase ErrorE 11:55:08 Next Writable Address: 1893472I 11:55:08 Synchronising Cache...W 11:55:11 User opted to skip the 'Close Track/Session/Disc' functions.E 11:55:11 Failed to Write Image!I 11:55:14 Exporting Graph Data...I 11:55:14 Graph Data File: C:\Users\Pvcsadmin\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_WH16NS58_TST4_THURSDAY-MAY-03-2018_11-48_AM_YUDEN000-T02-00_MAX.ibgI 11:55:14 Export Successfully Completed!E 11:55:14 Operation Failed! - Duration: 00:07:01I 11:55:14 Average Write Rate: 9,355 KiB/s (6.9x) - Maximum Write Rate: 10,972 KiB/s (8.1x)I 11:55:14 Close Request AcknowledgedI 11:55:14 Closing Down...I 11:55:14 Shutting down SPTI...I 11:55:14 ImgBurn closed!
dbminter Posted May 3, 2018 Posted May 3, 2018 Are those actual Taiyo Yuden media or cheap knockoffs? TY no longer makes media and it's good name may have been sold to cheap manufacturer CMC. Since I question whether those are legitimate TY media, I'd first try Verbatim DataLife Plus series DVD's and see if your problem goes away. If it doesn't, then your drive probably is the problem. You can only find Verbatim DataLife Plus media online. DON'T get the Life Series you find in stores. They're cheap CMC.
Sizzlechest Posted May 3, 2018 Author Posted May 3, 2018 These are CMC Pro, which are all you can get since TYs are no longer made in the old Japanese factory. Other people have tested these and found they were good.
Sizzlechest Posted May 3, 2018 Author Posted May 3, 2018 BTW, you can't get the CMC Pro DVD+Rs anymore. Only DVD-R is produced now.
dbminter Posted May 3, 2018 Posted May 3, 2018 I wouldn't trust CMC with anything. I spent hundreds of dollars before I learned CMC was the problem with everything I was experiencing. More discs, replaced DVD burners, replaced DVD video recorders. Then, on another forum, I randomly came across CMC being cheap and problematic. When I checked my discs, sure enough, the Optodiscs that used to work and were good were made by Optodisc and all the ones that were failing were CMC because they had switched manufacturers! So, both Optodisc and CMC went on my list. Anyway, I'd still try Verbatims. If you know the known really good stuff doesn't work on your drive, the problem is the drive and probably needs replacing. I looked up your drive. It's not a slim line junk model, so that's not the cause. It does appear to be about 5 years old, so it could be the age. Your drive's firmware may not simply support a newer CMC Pro type of disc. Try updating the firmware of your model. In Write mode, right click on the drive target and choose Check for firmware updates. See if there any.
Sizzlechest Posted May 3, 2018 Author Posted May 3, 2018 The drives are in a Primera Disc duplicator and it's new. The failures don't occur often. Maybe 1 every 50-100. I'm trying a different brand soon.
dbminter Posted May 3, 2018 Posted May 3, 2018 That was my experience with the CMC's from Optodisc. About 50 percent of the discs would complete writes (and verifies if applicable) and half would fail to complete burns or verifies. You may want to see if you get the same random failures on the Verbatims. A drive can be bad out of the box. I've had 2 Pioneer BD drives that were that way and 1 LiteOn DVD burner that was.
LIGHTNING UK! Posted May 4, 2018 Posted May 4, 2018 "Data Phase Error" is not a common error... not common at all! In fact, this thread is the only one on the forum that Google finds containing that exact phrase. I wouldn't be surprised if it was down to some sort of communication issue. Google it and see what you think.
Sizzlechest Posted May 4, 2018 Author Posted May 4, 2018 I know. I googled first before posting. I'm beginning to wonder if the solution is to change the USB cable! FYI, when the error occurs, the retries fly by almost instantaneously. It's not like it's reading a bad disc where it has to re-seek. It usually happened early on in the burn, but this one was near the end.
dbminter Posted May 4, 2018 Posted May 4, 2018 Oh, sorry. Ignore what I said earlier about your drive's age, etc. I googled the wrong product. I misread the log and thought the target drive was the first one in the list.
dbminter Posted May 4, 2018 Posted May 4, 2018 I looked up the CORRECT model this time. I've used that drive for many years, with a few different copies of it over those years, since it needs replacing about every 11 months. I never encountered a problem with DVD writing. However, you mentioned a new USB cable, which implies you've put that model in an enclosure, since that's an internal drive. Did you mean SATA cable, the internal connection for the internal drive internally? Or did you mean a USB cable because that internal drive is an external enclosure connected by USB?
Sizzlechest Posted May 4, 2018 Author Posted May 4, 2018 I looked up the CORRECT model this time. I've used that drive for many years, with a few different copies of it over those years, since it needs replacing about every 11 months. I never encountered a problem with DVD writing. However, you mentioned a new USB cable, which implies you've put that model in an enclosure, since that's an internal drive. Did you mean SATA cable, the internal connection for the internal drive internally? Or did you mean a USB cable because that internal drive is an external enclosure connected by USB? Sorry, let me explain. There are two LG drives inside a Primera 4202 Blu-ray disc duplicator. The third drive in the log is the one that's inside the computer that operates the duplicator. It's an old computer that doesn't have USB 3.0 ports. That's why the log shows USB 2.0 even though the "enclosure" can support USB 3.0. It's a single USB cable for both drives. I have not attempted simultaneous burns yet. When I get a new computer with USB 3.0 capability, I will attempt it. Considering how rare this error is and that it might be related to a communications issue rather than an inability of the drive to read/write the disc, I suggested troubleshooting by changing out the USB cable. I might have re-used the USB 2.0 cable from the old duplicator rather than use a new USB 3.0 cable.
dbminter Posted May 5, 2018 Posted May 5, 2018 Well, the log would still show up USB 2.0 even on USB 3.0 connections. It's a feature limitation in the current version of ImgBurn. It will be fixed in the next release. Even on my USB 3.0 ASUS BD drive, it showed up as USB 2.0.
Sizzlechest Posted May 7, 2018 Author Posted May 7, 2018 (edited) Good to know. I just verified that I did use the new cable. It's a rare occurrence, so it's not easy to test a fix. The only two other options would be to try a different cable and/or upgrade the computer. Edited May 7, 2018 by Sizzlechest
Recommended Posts