Verify error, but disk is ok

[amln]

I've burned a 50GB Bluray DL disk (Xlayer brand, seems to be Ritek) and during the verify session I got countless miscompare error messages for some files. So many that Imgburn asked if I wanted to ignore them (which I did). After the verify session Imgburn generates a success message (despite all miscompare errors).

 

Then I checked if those files for which the miscompare messages were generated were ok. They were fine.

 

Finally I used Winmerge to compare again all files on the Bluray disk with the origin files. It turned out that they were identical with the origin files.

 

So why exactly is Imgburn giving all these miscompare errors?

 

The setup used for burning was the following:

• Asus EeeBook F205T netbook with Win 8.1
• External 3TB disk connected via USB
• External Bluray burner

[LIGHTNING UK!]

Can you post the log please?

[amln]

Unless it was saved somewhere, I don't have it. After this problem happened, I've burned other Bluray disks without this problem.

[LIGHTNING UK!]

You can access the auto saved log via the Help menu.

[amln]

I found the log. It's over 3500 lines long. Shall I post it here completely?

 

Anyway, here are the probably most interesting parts. What follows is the log part after the start of the verify:

 

W 22:07:48 Waiting for device to become ready...
I 22:08:10 Device Ready!
I 22:08:13 Operation Started!
I 22:08:13 Source Device: [0:0:0] PLEXTOR BD-R  PX-LB950UE 1.01 (E:) (USB)
I 22:08:13 Source Media Type: BD-R (Disc ID: RITEK-DR2-000) (Speeds: 4x)
I 22:08:13 Image File: -==/\/[bUILD IMAGE]\/\==-
I 22:08:13 Image File Sectors: 24.437.408 (MODE1/2048)
I 22:08:13 Image File Size: 50.047.811.584 bytes
I 22:08:13 Image File Volume Identifier: RAW
I 22:08:13 Image File Volume Set Identifier: 4633AA040174E29F
I 22:08:13 Image File Application Identifier: IMGBURN V2.5.5.0 - THE ULTIMATE IMAGE BURNER!
I 22:08:13 Image File Implementation Identifier: ImgBurn
I 22:08:13 Image File File System(s): ISO9660; UDF (1.02)
I 22:08:13 Read Speed (Data/Audio): MAX / MAX
I 22:08:13 Verifying Session 1 of 1... (1 Track, LBA: 0 - 24437407)
I 22:08:13 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 24437407)
I 22:08:13 Verifying Layer 0... (LBA: 0 - 12219391)
I 22:31:31 Verifying Layer 1... (LBA: 12219392 - 24437407)
W 23:44:25 Miscompare at LBA: 12219392, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:25 Device: 0x00 (Empty Sector!)
W 23:44:25 Image File: 0x6C
W 23:44:25 Total Errors in Sector: 1.952
I 23:44:25 Verifying Sectors...
W 23:44:28 Miscompare at LBA: 12219393, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:28 Device: 0x00 (Empty Sector!)
W 23:44:28 Image File: 0x02
W 23:44:28 Total Errors in Sector: 2.026
I 23:44:28 Verifying Sectors...

 

Then there is around 3000 lines of this miscompare. Something like this:

 

W 23:44:28 Miscompare at LBA: 12219394, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:28 Device: 0x00 (Empty Sector!)
W 23:44:28 Image File: 0xA0
W 23:44:28 Total Errors in Sector: 1.931
I 23:44:28 Verifying Sectors...
W 23:44:29 Miscompare at LBA: 12219395, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:29 Device: 0x00 (Empty Sector!)
W 23:44:29 Image File: 0x01
W 23:44:29 Total Errors in Sector: 2.027
I 23:44:29 Verifying Sectors...
W 23:44:30 Miscompare at LBA: 12219396, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:30 Device: 0x00 (Empty Sector!)
W 23:44:30 Image File: 0xC8
W 23:44:30 Total Errors in Sector: 1.986
I 23:44:37 Verifying Sectors...
W 23:44:37 Miscompare at LBA: 12219397, Offset: 0, File: \2004\RAW\PC083678.ORF
W 23:44:37 Device: 0x00 (Empty Sector!)
W 23:44:37 Image File: 0xB0
W 23:44:37 Total Errors in Sector: 1.967
I 23:44:37 Verifying Sectors...

Edited January 23, 2015 by amln

[LIGHTNING UK!]

The 'empty sector' bit suggests something weird started going on where the drive stopped returning actual data or a driver started messing things up and breaking the I/O chain so the data never made it back to the program.

[amln]

The strange thing is also the long time after the verify layer 1 event:

 

I 22:08:13 Verifying Layer 0... (LBA: 0 - 12219391)
I 22:31:31 Verifying Layer 1... (LBA: 12219392 - 24437407)
W 23:44:25 Miscompare at LBA: 12219392, Offset: 0, File: \2004\RAW\PC083678.ORF

 

23 minutes between layer 0 and layer 1, then over an hour after the start of verify layer 1 comes this error. The verification of layer 1 should also have lasted about 23 minutes (assuming both layers have the same size).

[LIGHTNING UK!]

Unless that's where it was waiting for user input?

 

You're using an old version of the program there btw.

[amln]

Well no, for sure no user input. But if you also have no other explanation, I wonder if this could have been caused by something going into sleep mode, given the long burn times.

 

The burning takes so long, because the netbook has only USB2 and very few GB of disk space (around 10). The source drive is a 3TB external HDD connected via USB2, the bluray burner is also connected via USB2. I've now set the energy options to make the netbook go into sleep mode only after 3 hours. But before, this interval was lower and I would let the netbook run alone unattended.

Perhaps it went into sleep mode during the burning and when I would find it in sleep mode and wake it up, it might have had trouble reconnecting to the external drive and Bluray burner.

 

Just a speculation from my side.

 

Anyway, since I've set the sleep mode interval to 3 hours (burning + verify takes about one and a half hours), I haven't had this problem again. Hopefully it won't happen again.