dbminter

Burn completed. Awaiting Verify results.

Actually, I just looked in the logs folder and found the file containing a full log from a failed burn before. //****************************************\\ ; ImgBurn Version 2.5.8.0 - Log ; Tuesday, 07 October 2014, 19:57:30 ; \\****************************************// ; ; I 18:21:57 Project Successfully Loaded! I 18:21:57 ImgBurn Version 2.5.8.0 started! I 18:21:57 Microsoft Windows 8 Core x64 Edition (6.2, Build 9200) I 18:21:57 Total Physical Memory: 12,532,952 KiB - Available: 9,249,348 KiB I 18:21:57 Initialising SPTI... I 18:21:57 Searching for SCSI / ATAPI devices... I 18:21:57 -> Drive 1 - Info: ELBY CLONEDRIVE 1.4 (N:) (SCSI) I 18:21:58 -> Drive 2 - Info: PIONEER BD-RW BDR-209M 1.20-ID60 (S:) (SATA) I 18:21:58 -> Drive 3 - Info: ELBY CLONEDRIVE 1.4 (L:) (SCSI) I 18:21:58 -> Drive 4 - Info: ELBY CLONEDRIVE 1.4 (Q:) (SCSI) I 18:21:58 -> Drive 5 - Info: HL-DT-ST BD-RE WH14NS40 1.03-A0 (K:) (SATA) I 18:21:58 Found 3 BD-ROM/HD DVD-ROMs and 2 BD-RE XLs! I 18:22:12 Operation Started! I 18:22:12 Building Image Tree... I 18:22:13 Corrected file system selection for DVD Video disc. I 18:22:14 Corrected UDF revision selection for DVD Video disc. I 18:22:14 Calculating Totals... I 18:22:14 Preparing Image... I 18:22:19 Using Layer Break LBA: 1855066 -> 2078128 (VTS_02, PGC: 2, Chapter: 1, Cell: 1, Vob/Cell ID: 2/1, Time: 00:00:00, SPLIP: No) I 18:22:19 Contents: 21 Files, 2 Folders I 18:22:19 Content Type: DVD Video I 18:22:19 Data Type: MODE1/2048 I 18:22:19 File System(s): ISO9660, UDF (1.02) I 18:22:19 Volume Label: [Not Configured] I 18:22:19 IFO/BUP 32K Padding: Enabled I 18:22:19 Region Code: 1, 2, 3, 4, 5, 6, 7, 8 I 18:22:19 TV System: NTSC I 18:22:19 Size: 8,054,568,960 bytes I 18:22:19 Sectors: 3,932,895 I 18:22:19 Image Size: 8,512,012,288 bytes I 18:22:19 Image Sectors: 4,156,256 I 18:22:19 Operation Successfully Completed! - Duration: 00:00:07 I 18:22:40 Operation Started! I 18:22:40 Source File Sectors: 3,994,016 (MODE1/2048) I 18:22:40 Source File Size: 8,179,744,768 bytes I 18:22:40 Source File Volume Set Identifier: 45479250003CF191 I 18:22:40 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER! I 18:22:40 Source File Implementation Identifier: ImgBurn I 18:22:40 Source File File System(s): ISO9660, UDF (1.02) I 18:22:40 Destination Device: [0:0:0] PIONEER BD-RW BDR-209M 1.20 (S:) (SATA) I 18:22:40 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) I 18:22:40 Destination Media Supported Write Speeds: 2.4x, 4x, 6x, 8x I 18:22:40 Destination Media Sectors: 4,173,824 I 18:22:40 Destination Media L0 Data Zone Capacity: 2,086,912 (Changeable: Yes) I 18:22:40 Write Mode: DVD I 18:22:40 Write Type: DAO I 18:22:40 Write Speed: MAX I 18:22:40 DVD+R DL Reserve Track: No I 18:22:40 Link Size: Auto I 18:22:40 Lock Volume: Yes I 18:22:40 Test Mode: No I 18:22:40 OPC: No I 18:22:40 BURN-Proof: Enabled I 18:22:40 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 18:22:40 Advanced Settings - Optimal Writing Speed: No I 18:22:40 Optimal L0 Data Zone Capacity: 1,997,008 I 18:22:40 Optimal L0 Data Zone Method: Copied From Original Disc I 18:23:00 Set L0 Data Zone Capacity Succeeded! I 18:23:00 L0 Data Zone Capacity - Effective: 1,997,008 I 18:23:00 Filling Buffer... (40 MiB) I 18:23:01 Writing LeadIn... I 18:23:06 Writing Session 1 of 1... (1 Track, LBA: 0 - 3994015) I 18:23:06 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3994015) I 18:23:06 Writing Layer 0... (LBA: 0 - 1997007) I 18:30:10 Writing Layer 1... (LBA: 1997008 - 3994015) W 18:31:46 Failed to Write Sectors 2387408 - 2387439 - Reason: Internal Target Failure W 18:31:46 Retrying (1 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (2 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (3 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (4 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (5 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (6 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (7 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (8 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (9 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (10 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (11 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (12 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (13 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (14 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (15 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (16 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (17 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (18 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (19 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write W 18:31:54 Retrying (20 of 20)... W 18:31:54 Retry Failed - Reason: Invalid Address For Write E 18:32:16 Failed to Write Sectors 2387408 - 2387439 - Reason: Internal Target Failure E 18:32:16 Next Writable Address: 2386960 I 18:32:16 Synchronising Cache... W 18:32:19 User opted to skip the 'Close Track/Session/Disc' functions. E 18:32:19 Failed to Write Image! I 18:32:21 Exporting Graph Data... I 18:32:21 Export Successfully Completed! E 18:32:21 Operation Failed! - Duration: 00:09:39 I 18:32:21 Average Write Rate: 8,681 KiB/s (6.4x) - Maximum Write Rate: 10,912 KiB/s (8.1x) I freely admit I removed folder names and disc labels for my own privacy.

Well, I changed the settings and was going to post the log after this burn. However, it appears that changing the OPC setting may have done the trick. I'm past where it bombed out before. 72% right now. I will still need for the Verify to complete. I will post the log regardless.

Yeah, you shouldn't have trouble just Reading the bootable disc to an image file and then Writing the image file to a disc and still have the disc bootable. As long as you do a Read/Write, the boot image should be preserved.

Never mind. Found it right where it should be. Under the Write Options tab.

Where would I turn on this Perform OPC before write option?

Sorry. I only posted what I thought was valid. Besides, there's no need for the Retries 2 through 19. I still have the image file I was testing with so I'll try what you said.

The USB burn has gotten past the layer break. I'll need for the burn to complete and Verify to finish to know for sure, but I seem to have nailed it down. Yeah, the USB burn on the inkjet MKM-003-00 completed and Verified successfully. The Pioneer doesn't like inkjet MKM-003-00, yet likes non-inkjet MKM-003-00. Go figure. I don't think I've ever actually burned one of these inkets in the drive before. Now I know to test each new drive with each media I have for it to make sure. So, I guess Pioneer goes on my list because it can't write a media I need it to write. However, what choice do I have? LG's don't write 8x DVD+RW correctly and possibly all rewritable DVD media. Anyway, not that it probably matters anymore, but can anyone determine anything about this issue from the error codes I posted before?

Well, looks like the non-inkjet discs are still burning okay. I've gotten past the layer break to almost 80%. So, it seems to be these injket discs somehow. I will let the burn complete and Verify complete to make sure it still works and then try burning one of these inkjets in the USB LiteOn. I'm not entirely sure I've ever burned one of these inkjet MKM-003-00 DVD+R DL's in this Pioneer drive. The drive just may not like them. However, the MID is the same for both discs. That doesn't necessarily mean they're exactly the same, does it? So, whatever you can offer on this LUK would be appreciated. EDIT: The non-inkjet MKM-003-00 burned and Verified with no errors.

This is the first time I've tried burning these inkjet Verbatim DVD+R DL's in my new PC. I've burned 2 in a row with the same error. EDIT: This errors out always shortly after the layer break is reached. I/O error ScsiStatus: 0x02 Interpretation: Check condition CDB: 2A 00 00 23 F2 D0 00 00 20 00 Interpretation: Write (10) - Sectors: 2355920 - 2355951 Sense area: 71 00 04 00 23 F0 F0 0E 00 00 00 00 44 00 00 00 00 00 SK Interpretation: Hardware error ASC/ASCQ Interpretation: Internal Target Failure I 18:40:36 Writing Layer 1... (LBA: 1997008 - 3994015) W 18:41:44 Waiting for buffers to recover... (LBA: 2228784) W 18:41:52 Waiting for hard disk activity to reach threshold level... I 18:41:59 Writing Sectors... W 18:42:24 Failed to Write Sectors 2355920 - 2355951 - Reason: Internal Target Failure W 18:42:24 Retrying (1 of 20)... W 18:42:33 Retry Failed - Reason: Invalid Address For Write W 18:42:33 Retrying (20 of 20)... W 18:42:33 Retry Failed - Reason: Invalid Address For Write E 18:46:33 Failed to Write Sectors 2355920 - 2355951 - Reason: Internal Target Failure E 18:46:33 Next Writable Address: 2355472 I 18:46:33 Synchronising Cache... W 18:46:36 User opted to skip the 'Close Track/Session/Disc' functions. E 18:46:36 Failed to Write Image! I just burned a non inkjet Verbatim DVD+R DL with the same MID (MID: MKM-003-00) last week without a problem in this drive. I'll try burning again in the same drive with one of those DVD+R DL's from the same stack that worked. I can't test in my LG BD drive because it stopped writing DVD+R DL's in January and I use it only as a reader now. I could test on my USB LiteOn but as it's not SATA like this internal drive, the tests wouldn't be the same. Although it would show if the stack of inkjet discs had gone bad if it failed, too. In the meantime, I'll test one of these non inkjet MKM-003-00's and see if the drive maybe has gone bad since last week. But, I'd like to get advice from LUK on what this error may actually mean.

What exactly is Synchronising cache? What's being synchronised and why must whatever caches are synchronised be synchronised?

Had to disable Secure Boot in the UEFI to enable legacy booting to boot those CD's. So, the answer is yes and no. Yes, the discs will boot on UEFI but no they won't boot with Secure Boot on.

Yeah, everyone keeps predicting the death of the DVD. However, the DVD was the fastest adopted home technology in history. DVD's aren't going away any time soon. People bought too many DVD players and Blu-Ray came out too soon after DVD to warrant people replacing their collections. The fact is DVD does the job that most people want. Despite what Hollywood wanted, Blu-Ray did not become the got to have replacement for DVD, even when it tried to entice people by no longer putting the extras on the DVD version and instead only on the Blu-Ray version.

My new PC is my first exposure to UEFI. I have a few bootable CD's for applications that used to boot on my old BIOS based Dell XPS 8300 but only one of them boots on my UEFI based Dell XPS 8700 PC! This one application has specific options in its bootable media creator to enable UEFI. The discs are simply not recognized as bootable in the 8700's F12 bootable menu interface. Only the Macrium Reflect media is recognized as bootable. So, I guess my question is do bootable discs that booted on BIOS based computers not necessarily boot on UEFI ones?

You know, there's going to be an issue with creating ISO's in the future on SSD's, the way I see it. Eventually, SSD's will replace mechanical HD's so you will ONLY have an SSD to write ISO's to. And there's the large file issue in general. You shouldn't be writing large files to SSD's. Yet, Windows writes tremendously large files to the SSD in the form of the swapfile and the hiberfil.sys.

Well, Ritek may not solve the problem, depending on where you live. It seems that in Europe, Ritek is problematic. It has been reported to cause errors. My experience with Ritek in R1 is that Ritek/Ricoh is a very good 2nd tier product. Ritek currently makes the Sony DVD-R's and Memorex's BD-R and RE SL's. However, the Ritek BD-R's have playback issues with the Playstation 3; yet, the Ritek 8x DVD+RW don't have playback issues with the PS3. I use those all the time on the PS3. I've used Ritek media for years without problem, except for the BD-RE SL's on the PS3 and their 6x DVD-RW's on everything but LiteOn.

Well, CMC isn't entirely unusable. They used to make a DVD+R that was pretty good. But, the last DVD+R's from them I was stuck with would not even be recognized as inserted in a Memorex DVD player! I've also tried using the BD-RE SL's I've gotten that were CMC's and they wrote okay. However, the problem with CMC is their reputation. I'd trust their media about as far as I can throw their corporate headquarters! For that reason, I'm laying the blame for your problem at the doorstep of CMC. I also don't like LiteOn drives. I used to use them all the time but I discovered something about them after I had their piece of junk Blu-Ray burner that stopped writing to BD-RE's after 3 months. LiteOn drives randomly write incorrectly DVD-Video DVD+R DL's. They insert a random pause into the playback. It's not a layer break and it doesn't happen with any frequency that can be repeated. Except on my Blu-Ray where it did it to 2 out of 3 DVD-Video DVD+R DL's I had written in it. So, after that Blu-Ray drive and discovering this randomness that had happened before on other LiteOn's, I no longer will use LiteOn products. LiteOns, though, do one thing I've never seen any other drive do, though. They write Ritek 6x DVD-RW correctly. No other drive I've ever tried them on succeeded.

No, they don't print the MID/DID on the package because they don't want you to know who manufactured the media. If you did, you might not buy it if you knew the reputation of CMC. The best you're going to get is online reviewers like me. On Amazon.com, I always post reviews of media I buy to list the MID/DID and thus the manufacturer. Just because I lose out doesn't mean CMC has to win. I just recently had to post a negative review of Japanese TDK inkjet BD-RE SL's because they were CMC's. The site that came before this one informed me about CMC. But I learned too late as I'd plunked nearly a $1,000 troubleshooting a formerly good media gone bad, e.g. Optodisc to CMC. Once I read about CMC, I checked the MID on the discs that had been good but were failing and, sure enough, they were CMC.

Have you used these CMC MAG discs before without problems with this drive? I am first pointing the finger at CMC, the worst optical disc manufacturer out there. Lots of times, we encounter people with problems with CMC media that magically fix themselves when they drop the cheap media and go with something like Verbatim (Although they, too, sometimes use CMC. ) or Taiyo Yuden.

Do NOT buy Japanese TDK BD-RE SL inkjet discs! They are made by CMC! Their BD-RE DL, last I bought them, were made by TDK. But now it seems TDK, too, like Verbatim, has sold out to CMC

Well, TDK also sold out to CMC shit! These Japanese made BD-RE SL's I just got are also CMC I'd send them back but I can use them because they're inkjet printable. But I know from now on only to get the BD-RE DL's from TDK.

I've noticed something on some BD-RE SL and DL's when I insert them. The drive light keeps flashing when they're in the drive. Even though ImgBurn starts writing to the discs right away, it still makes me wonder. This usually happens with BD-RE's that have just been erased. I've seen this on both my LG and Pioneer drives and with Ritek BD-RE SL and TDK BD-RE DL. Is this something I should be concerned about?

Yeah, and Microsoft STILL can't get the screen saver to work right! On Windows 7, it wasn't always guaranteed that your screen saver would start. It would start but after a while, it wouldn't until Windows was restarted. On Windows 8, it's even worse. After working initially, now screen saver NEVER starts. I just get that stupid screen you have to press Enter at to get to the sign in prompt! ANOTHER stupid thing! You HAVE to use the login prompt to access Windows. So, Microsoft put a stupid, useless screen that you MUST press a key on to access the login prompt! IDIOTS! In Microsoft's defense, not that I am trying to defend them just being complete for the sake of the facts, the AnyDVD screen was a setting I forgot to set. Now that it's set, its window of information displays on top.

Well, it seems that now the idea of USB monitors may be one step closer to actual reality! Seems that with the upcoming USB 3.1 standard, they're working in DisplayPort into the data channels for it. In effect, USB connected monitors. This would drastically reduce the proprietary format of monitors. So, it most likely means this will never take off. monitor manufacturers want the proprietary scheme forcing you to update your monitor every few years, like I had to recently.

Well, it could be a case that the CMC BD-RE's are actually decent media, like CMC DVD+R. However, I wouldn't trust CMC as far as I can throw their corporate headquarters building! So, I have 10 CMC BD-RE's but I'll only write to them as a last resort. I have some TDK's on the way. I have some TDK BD-RE DL's that seem to be okay. I lost about a $1,000 because of CMC! Optodisc used to make a great DVD-R and then they switched to CMC. I'd never heard of CMC before the forums for a certain other application. Once someone there mentioned the evils of CMC causing bad burns I checked my Optodiscs which were causing me problems. Sure enough, they were all CMC's! I spent about $500 in media back when it cost like $2.50 for a DVD-R from Optodisc and I also replaced my Panasonic DVD video recorder trying to troubleshoot the problem.