How to find list of all files that did not burn when a failed burn occurs (at any percentage of failure)

Audrey · November 18, 2016

First, background info.

Be aware that the timestamps on the logs reflect different days.

Using ImgBurn 2.5.8.0, my most recent Bluray burn project failed at 85%:

I 05:15:26 Writing Session 1 of 1... (1 Track, LBA: 0 - 12195199)
I 05:15:26 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12195199)
W 05:35:22 Failed to Write Sectors 9560384 - 9560415 - Reason: No Write Current

W 05:35:22 Retrying (1 of 20)...

<snipped Retries #2-20>
W 05:35:38 Retrying (21)...

W 05:35:38 Retry Failed - Reason: Invalid Address For Write

W 05:35:39 Retrying (22)...

W 05:35:39 Retry Failed - Reason: Invalid Address For Write

E 05:35:50 Failed to Write Sectors 9560384 - 9560415 - Reason: No Write Current
E 05:35:50 Next Writable Address: 9559904
I 05:35:50 Synchronising Cache...
I 05:35:55 Closing Track...
I 05:36:00 Finalising Disc...
E 05:36:05 Failed to Write Image!

(complete log is at the end of this post)

It was a compilation of individual 1,534 FLAC and MP3 audio files (plus 131 folders), not an ISO image. The "Image Information" tab resulted in the following information:

I 05:59:34 Operation Started!

I 05:59:34 Building Image Tree...

I 05:59:34 Calculating Totals...

I 05:59:34 Preparing Image...

I 05:59:35 Contents: 1,534 Files, 131 Folders

I 05:59:35 Content Type: Data

I 05:59:35 Data Type: MODE1/2048

I 05:59:35 File System(s): ISO9660, UDF (1.02)

I 05:59:35 Volume Label: 161104_0437 FLAC MP3

I 05:59:35 Size: 24,969,591,980 bytes

I 05:59:35 Sectors: 12,192,949

I 05:59:35 Image Size: 24,975,769,600 bytes

I 05:59:35 Image Sectors: 12,195,200

I 05:59:35 Operation Successfully Completed! - Duration: 00:00:00

Thus the complete compilation was supposed to be 24,969,591,980 bytes but the Verify process (with Verify Against Image File unticked) showed that only 19,578,617,856 bytes were burned out of the total 24,969,591,980 bytes. Subtraction shows that 5,390,974,124 bytes (5.0207 gb) of data was not burned. It is nearly impossible to find which 15% of the files/folders did not get burned.

Here is the verify log:

I 06:07:51 Operation Started!

I 06:07:51 Source Device: [0:0:0] MATSHITA BD-MLT UJ240AS 1.40 (E:) (RAID)

I 06:07:51 Source Media Type: BD-R (Disc ID: VERBAT-IMu-000)

I 06:07:51 Source Media Supported Read Speeds: 1.6x, 2x, 5.4x

I 06:07:51 Source Media Supported Write Speeds: 2x, 4x

I 06:07:51 Source Media Sectors: 9,559,872

I 06:07:51 Source Media Size: 19,578,617,856 bytes

I 06:07:51 Verify Against Image File: No

I 06:07:51 Read Speed (Data/Audio): MAX / MAX

I 06:07:52 Read Speed - Effective: 2.5x - 5.4x

I 06:07:53 Verifying Session 1 of 1... (1 Track, LBA: 0 - 9559871)

I 06:07:53 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 9559871)

I 06:25:57 Exporting Graph Data...

I 06:25:57 Graph Data File: C:\Users\USER\AppData\Roaming\ImgBurn\Graph Data Files\MATSHITA_BD-MLT_UJ240AS_1.40_FRIDAY-NOVEMBER-18-2016_6-07_AM_VERBAT-IMu-000.ibg

I 06:25:57 Export Successfully Completed!

I 06:25:57 Operation Successfully Completed! - Duration: 00:18:04

My question is this: How can I find out which files did not successfully burn? In this project, I could add every audio file to VLC and listen to each song from start to finish to be certain that they can play without errors from beginning to end. But that is incredibly tedious and time-consuming, not to mention an absurd waste of time. There must be a way to compare the files that are listed in the compilation list (the .IBB file) against the files that were successfully written to the disc. In VLC, I selected 3 tracks at random from the disc and 2 of the 3 yielded the error "inaccessible". I understand that an optical disc contains a "TOC" of some type that lists the folders and files contained on the disc. However, the presence of this "TOC" does not tell whether each item is readable, let alone present. (A useful TOC discussion is found here https://www.isobuster.com/help/cd_dvd_layout, para #6. I may not have used the "TOC" phrase correctly in the above sentence.)

As can be seen from the log, I used a Verbatim BD-R 25gb disc, a reputable name brand. The lack of write current seems to have initiated the failure. I don't understand how the write current could "disappear." My laptop was running on electricity, not battery. The error " Retry Failed - Reason: Invalid Address For Write " occurs right after the lack of write current. In any event, my forum question is really about how to determine which files are not written when there is a failed burn. In the burn window, this project displayed a message saying something like "failed at 85% done, do you want to close/finalize the disc?" I clicked YES.

So, Sir Lightning UK ( J ), in all the years since you first coded and released this wonderful freeware program, have you ever been asked how to one could determine which files/folders have failed to burn? Surely there must be a way. I have Googled the web for answers to this question (using many permutations of my problem), but no luck. Not even similar questions popped up in the search results.

An additional question (or three):

- 1a) How does ImgBurn determine the order in which it will burn the current compilation's files?

- 1b) And then how does it select the 2nd file, 3rd file, 4th, and so on, until the 1,534th file? I have always wondered how any burning program chooses the order in which the compilation's list of files and folders are burned. If I were able to know the order that the files were burned, I could easily determine the names of the last 15%. Thus I would quickly know which files did not get burned onto my disc.

- 2) A related question (that isn't an ImgBurn question) is: How does Windows/Linux/Mac select which file it begins a copy (or move) operation that contains multiple files in the selection set?

Thank you for helping,

-Audrey

Complete ImgBurn log of the failed burn:

I 05:14:45 Operation Started!

I 05:14:45 Building Image Tree...

I 05:14:46 Calculating Totals...

I 05:14:46 Preparing Image...

I 05:14:46 Contents: 1,534 Files, 131 Folders

I 05:14:46 Content Type: Data

I 05:14:46 Data Type: MODE1/2048

I 05:14:46 File System(s): ISO9660, UDF (1.02)

I 05:14:46 Volume Label: 161104_0437 FLAC MP3

I 05:14:46 Size: 24,969,591,980 bytes

I 05:14:46 Sectors: 12,192,949

I 05:14:46 Image Size: 24,975,769,600 bytes

I 05:14:46 Image Sectors: 12,195,200

I 05:14:46 Operation Successfully Completed! - Duration: 00:00:00

I 05:14:46 Operation Started!

I 05:14:46 Source File: -==/\/[bUILD IMAGE]\/\==-

I 05:14:46 Source File Sectors: 12,195,200 (MODE1/2048)

I 05:14:46 Source File Size: 24,975,769,600 bytes

I 05:14:46 Source File Volume Identifier: 161104_0437 FLAC MP3

I 05:14:46 Source File Volume Set Identifier: 496729D600BA1568

I 05:14:46 Source File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!

I 05:14:46 Source File Implementation Identifier: ImgBurn

I 05:14:46 Source File File System(s): ISO9660, UDF (1.02)

I 05:14:46 Destination Device: [0:0:0] MATSHITA BD-MLT UJ240AS 1.40 (E:) (RAID)

I 05:14:46 Destination Media Type: BD-R (Disc ID: VERBAT-IMu-000)

I 05:14:46 Destination Media Supported Write Speeds: 2x, 4x

I 05:14:46 Destination Media Sectors: 12,219,392

I 05:14:46 Write Mode: BD

I 05:14:46 Write Type: DAO

I 05:14:46 Write Speed: MAX

I 05:14:46 Hardware Defect Management Active: No

I 05:14:46 BD-R Verify Not Required: Yes

I 05:14:46 Link Size: Auto

I 05:14:46 Lock Volume: Yes

I 05:14:46 Test Mode: No

I 05:14:46 OPC: No

I 05:14:46 BURN-Proof: Enabled

I 05:14:46 Write Speed Successfully Set! - Effective: 17,983 KB/s (4x)

I 05:14:49 Filling Buffer... (256 MiB)

I 05:15:10 Writing LeadIn...

I 05:15:26 Writing Session 1 of 1... (1 Track, LBA: 0 - 12195199)

I 05:15:26 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12195199)

W 05:35:22 Failed to Write Sectors 9560384 - 9560415 - Reason: No Write Current

W 05:35:22 Retrying (1 of 20)...