Unable to verify BD DL after burning - "no reference position found"

[jfcarpenter]

I've been trying to burn a Blu-Ray dual layer video disc.  Twice, at the end of the burn, the drive is cycled, as expected, but then I get the error "Device Not Ready - No Reference Position Found" and the verify fails to start.  (Full log is below.) The disc does verify successfully on its own, and I am able to play the disc in my BluRay player, but I'd still like to verify the disc with the source files and be 100% confident that the burn was succesful.

 

I am using the current (2.5.8.0) version of Imgburn.

 

I have burned BD DL discs succesfully before, but it might have been with an older version of Imgburn.  I am using the same computer, same BD drive, and discs from the same batch as when it did work.  I have also successfully burned and verified plenty of DVDs and single layer BDs.

 

I finally created an image from the files instead, and then burned the disc from the image.  In that case, both the burn and the verify worked successfully.  I also did a second verify of the disk against the image, and that completed with no errors as well.

 

Any idea what is going on? The fact that the error happened twice in a row, and that it has worked before, with the only thing different being the version of Imgburn, makes me suspect the program, but I am reluctant to try again (burning from files) because of the cost of the blank BD DL discs. 

 

 

I 00:10:10 Operation Started!

I 00:10:10 Building Image Tree...

I 00:10:10 Calculating Totals...

I 00:10:10 Preparing Image...

I 00:10:11 Contents: 18 Files, 16 Folders

I 00:10:11 Content Type: BD Video

I 00:10:11 Data Type: MODE1/2048

I 00:10:11 File System(s): UDF (2.50)

I 00:10:11 Volume Label: Superbowl XLIX

I 00:10:11 Size: 35,796,400,202 bytes

I 00:10:11 Sectors: 17,478,722

I 00:10:11 Image Size: 35,797,467,136 bytes

I 00:10:11 Image Sectors: 17,479,232

I 00:10:14 Operation Successfully Completed! - Duration: 00:00:03

I 00:10:14 Operation Started!

I 00:10:14 Source File: -==/\/[bUILD IMAGE]\/\==-

I 00:10:14 Source File Sectors: 17,479,232 (MODE1/2048)

I 00:10:14 Source File Size: 35,797,467,136 bytes

I 00:10:14 Source File Volume Identifier: Superbowl XLIX

I 00:10:14 Source File Volume Set Identifier: 467901C0010AB5C2

I 00:10:14 Source File Application Identifier: ImgBurn v2.5.8.0

I 00:10:14 Source File Implementation Identifier: ImgBurn

I 00:10:14 Source File File System(s): UDF (2.50)

I 00:10:14 Destination Device: [18:0:0] ATAPI iHBS212   2 5L06 (G:) (SATA)

I 00:10:14 Destination Media Type: BD-R (Disc ID: VERBAT-IMf-000)

I 00:10:14 Destination Media Supported Write Speeds: 4x, 6x

I 00:10:14 Destination Media Sectors: 24,438,784

I 00:10:14 Write Mode: BD

I 00:10:14 Write Type: DAO

I 00:10:14 Write Speed: 4x

I 00:10:14 Hardware Defect Management Active: No

I 00:10:14 BD-R Verify Not Required: Yes

I 00:10:14 Link Size: Auto

I 00:10:14 Lock Volume: Yes

I 00:10:14 Test Mode: No

I 00:10:14 OPC: No

I 00:10:14 BURN-Proof: Enabled

I 00:10:16 Write Speed Successfully Set! - Effective: 17,980 KB/s (4x)

I 00:10:16 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes

I 00:10:16 CD/DVD Life Record Count: 208 - CD/DVD Record Count: 27

I 00:10:16 BD Life Record Count: 59 - BD Record Count: 7

I 00:11:15 Filling Buffer... (80 MiB)

I 00:11:17 Writing LeadIn...

I 00:11:18 Writing Session 1 of 1... (1 Track, LBA: 0 - 17479231)

I 00:11:18 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 17479231)

I 00:11:18 Writing Layer 0... (LBA: 0 - 12219391)

I 00:34:30 Writing Layer 1... (LBA: 12219392 - 17479231)

I 00:44:30 Synchronising Cache...

I 00:44:33 Closing Track...

I 00:44:34 Finalising Disc...

I 00:45:28 Exporting Graph Data...

I 00:45:28 Graph Data File: C:\Users\Carpenter\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_iHBS212_2_5L06_THURSDAY-MARCH-26-2015_12-10_AM_VERBAT-IMf-000_4x.ibg

I 00:45:28 Export Successfully Completed!

I 00:45:28 Operation Successfully Completed! - Duration: 00:35:14

I 00:45:28 Average Write Rate: 17,558 KiB/s (4.0x) - Maximum Write Rate: 17,920 KiB/s (4.1x)

I 00:45:28 Cycling Tray before Verify...

W 00:45:35 Waiting for device to become ready...

W 00:46:35 Device Not Ready - No Reference Position Found

W 00:46:35 Retrying (1 of 3)...

I 00:46:35 Cycling Tray before Verify...

W 00:46:40 Waiting for device to become ready...

W 00:47:40 Retry Failed - Reason: No Reference Position Found

W 00:47:40 Retrying (2 of 3)...

I 00:47:40 Cycling Tray before Verify...

W 00:47:45 Waiting for device to become ready...

W 00:48:44 Retry Failed - Reason: No Reference Position Found

W 00:48:44 Retrying (3 of 3)...

I 00:48:44 Cycling Tray before Verify...

W 00:48:49 Waiting for device to become ready...

W 00:49:49 Retry Failed - Reason: No Reference Position Found

E 21:22:34 Device Not Ready - Reason: No Reference Position Found

E 21:22:34 Operation Aborted!

I 22:18:10 Device: [18:0:0] ATAPI iHBS212   2 5L06 (G:) (SATA)

I 22:18:10 Family Tree:

I 22:18:10 -> ACPI x64-based PC

I 22:18:10 -> Microsoft ACPI-Compliant System

I 22:18:10 -> PCI bus

I 22:18:10 -> Intel® ICH10 Family 6 Port SATA AHCI Controller - 3A22 (VEN_8086&DEV_3A22 - Intel - msahci - v7.0.0.1013)

I 22:18:10 -> IDE Channel (ATA Channel 4)

I 22:18:10 -> CD-ROM Drive (ATAPI iHBS212   2 ATA Device) (Channel 4, Target 0, Lun 0)

I 22:19:09 Close Request Acknowledged

I 22:19:09 Closing Down...

I 22:19:09 Shutting down SPTI...

I 22:19:09 ImgBurn closed!

[LIGHTNING UK!]

This is purely a hardware combo issue - drive / firmware / discs.

 

Your drive is producing a disc it then can't even initialise, so there's no chance in the software being able to verify it.

 

What I find interesting here is that you say you can verify it 'on its own' ? When and how are you able to do that? If you're reinserting it after a period of time, maybe it's a heat issue.

 

Ensure the drive's firmware is up to date and try cleaning it with a cleaning disc.

[jfcarpenter]

By "verify on its own" I mean selecting Verify from the Mode menu to verify that the disc can be read.  But I wasn't able to verify against the source, since as far as I know, you can only verify the contents of a disc by comparing it with the source, as a separate operation, if you burned the disc from an ISO file.

 

I thought maybe it was a heat issue, so I let the drive cool down for a while before I tried the verify one more time after the burn, but it didn't make any difference.

 

I'm not sure what you mean by "drive is producing a disc it then can't even initialise". This has worked for me previously, and this time I was able to burn the disc, it was just the verify that wouldn't work.  And, I was able to burn and verify the disc if I created an ISO file first.  It was only if I burned the disc from the source files that I had the problem.

 

I have noticed that when I try to mount the disc in WIndows (that I had the problem with) that it can take a long time before I can access it in Windows Explorer. Could the problem not being able to verify the disc be because Windows just takes a long time to mount the disc after it is burned?

 

I'm not going to worry about this, because I burn very few BD DL discs, and I can successfully burn and verify a disc by creating an ISO file first.  I was just hoping there might be some setting in Imgburn that I didn't know about that I could change that might help.

 

Thanks.

[LIGHTNING UK!]

When ImgBurn cycles the tray between the write and verify operations, it's so the drive has to reinitialise the disc (work out what it is and find out everything about it that it needs to know).

The problem you're facing is that the drive is unable to do that as it can't read the disc - eventually giving up and returning that 'reference position not found' error. At that point, no software can do anything with the disc. That's why I don't understand how you've been able to verify it. There must come a point in time where the drive no longer returns that 'reference...' error and the software is allowed access to the disc.

 

You could try enabling the 'perform opc before write' to see if the drive then does a better job of burning.