Jump to content

no time-out after being stuck during BD-R verification


Jack_Brody
 Share

Recommended Posts

Does ImgBurn have some sort of a time-out? It has already been over 80 minutes since a BD-R verification started. It stopped on 80%. The drive completely stopped rotating, no head movement can be heard, the LED is off. It is already at the room temperature by now. And ImgBurn is still counting time. This is my 4th BD-R burned, the previous 3 were OK.

image.png.796372b7eb227262a543269ca55a5219.png

 

The log:

I 09:54:19 ImgBurn Version 2.5.8.0 started!
I 09:54:19 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 09:54:19 Total Physical Memory: 14 555 540 KiB  -  Available: 9 784 636 KiB
I 09:54:19 Initialising SPTI...
I 09:54:19 Searching for SCSI / ATAPI devices...
I 09:54:19 -> Drive 1 - Info: PIONEER BD-RW   BDR-UD04 1.11-GENERAL (D:) (USB 2.0)
I 09:54:20 Found 1 BD-RE XL!
I 09:56:45 Operation Started!
I 09:56:45 Building Image Tree...
I 09:56:45 Calculating Totals...
I 09:56:45 Preparing Image...
I 09:56:45 Contents: 165 Files, 9 Folders
I 09:56:45 Content Type: Data
I 09:56:45 Data Type: MODE1/2048
I 09:56:45 File System(s): UDF (2.60)
I 09:56:45 Volume Label: 005
I 09:56:45 Size: 24 789 299 265 bytes
I 09:56:46 Sectors: 12 104 209
I 09:56:46 Image Size: 24 791 089 152 bytes
I 09:56:46 Image Sectors: 12 105 024
I 09:56:47 Operation Successfully Completed! - Duration: 00:00:02
I 09:56:47 Operation Started!
I 09:56:47 Source File: -==/\/[BUILD IMAGE]\/\==-
I 09:56:47 Source File Sectors: 12 105 024 (MODE1/2048)
I 09:56:47 Source File Size: 24 791 089 152 bytes
I 09:56:47 Source File Volume Identifier: 005
I 09:56:47 Source File Volume Set Identifier: 50644F0800B8B431
I 09:56:47 Source File Application Identifier: ImgBurn v2.5.8.0
I 09:56:47 Source File Implementation Identifier: ImgBurn
I 09:56:47 Source File File System(s): UDF (2.60)
I 09:56:47 Destination Device: [0:0:0] PIONEER BD-RW   BDR-UD04 1.11 (D:) (USB)
I 09:56:47 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 09:56:47 Destination Media Supported Write Speeds: 2x; 4x; 6x
I 09:56:48 Destination Media Sectors: 12 219 392
I 09:56:48 Write Mode: BD
I 09:56:48 Write Type: DAO
I 09:56:48 Write Speed: 4x
I 09:56:48 Hardware Defect Management Active: No
I 09:56:48 BD-R Verify Not Required: Yes
I 09:56:48 Link Size: Auto
I 09:56:48 Lock Volume: Yes
I 09:56:48 Test Mode: No
I 09:56:48 OPC: No
I 09:56:48 BURN-Proof: Enabled
I 09:56:48 Write Speed Successfully Set! - Effective: 17 980 KB/s (4x)
I 09:56:48 Advanced Settings - Optimal Writing Speed: No
I 09:56:48 Filling Buffer... (80 MiB)
I 09:56:48 Writing LeadIn...
I 09:57:12 Writing Session 1 of 1... (1 Track, LBA: 0 - 12105023)
I 09:57:12 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12105023)
I 10:22:04 Synchronising Cache...
I 10:22:05 Closing Track...
I 10:22:06 Finalising Disc...
I 10:22:22 Exporting Graph Data...
I 10:22:22 Graph Data File: C:\Users\Paja\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-UD04_1.11_STŘEDA-4-BŘEZEN-2020_9-56_CMCMAG-BA5-000_4x.ibg
I 10:22:22 Export Successfully Completed!
I 10:22:22 Operation Successfully Completed! - Duration: 00:25:34
I 10:22:22 Average Write Rate: 16 237 KiB/s (3.7x) - Maximum Write Rate: 17 623 KiB/s (4.0x)
I 10:22:22 Cycling Tray before Verify...
W 10:29:17 Waiting for device to become ready...
I 10:29:21 Device Ready!
I 10:29:22 Operation Started!
I 10:29:22 Source Device: [0:0:0] PIONEER BD-RW   BDR-UD04 1.11 (D:) (USB)
I 10:29:22 Source Media Type: BD-R (Disc ID: CMCMAG-BA5-000)
I 10:29:22 Source Media Supported Read Speeds: 6x
I 10:29:22 Source Media Supported Write Speeds: 2x; 4x; 6x
I 10:29:22 Source Media Sectors: 12 105 024
I 10:29:22 Source Media Size: 24 791 089 152 bytes
I 10:29:22 Image File: -==/\/[BUILD IMAGE]\/\==-
I 10:29:22 Image File Sectors: 12 105 024 (MODE1/2048)
I 10:29:22 Image File Size: 24 791 089 152 bytes
I 10:29:22 Image File Volume Identifier: 005
I 10:29:22 Image File Volume Set Identifier: 50644F0800B8B431
I 10:29:22 Image File Application Identifier: ImgBurn v2.5.8.0
I 10:29:22 Image File Implementation Identifier: ImgBurn
I 10:29:23 Image File File System(s): UDF (2.60)
I 10:29:23 Read Speed (Data/Audio): MAX / MAX
I 10:29:24 Read Speed - Effective: 2,5x - 6x
I 10:29:24 Verifying Session 1 of 1... (1 Track, LBA: 0 - 12105023)
I 10:29:24 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 12105023)

Interesting that my Win 10 is identified as Win 8.

Link to comment
Share on other sites

Maybe it has something to do with the cheap blanks you're using (cmcmag). But you can safely abort if you want. Verify just reads the disc and checks if it matches with the data it asked to burn, but verifying doesn't burn anything and aborting won't affect the already burned disc.

Sent from my Pixel 3 XL using Tapatalk

Link to comment
Share on other sites

It's been in "Waiting for Read Thread (Device)..." state for about half an hour since I clicked on the red rectangle button for cancelling. When I want to close the program (the usual cross in the top right corner), I get a message:

Please be patient, I'm already cancelling as fast as I can!

image.png.5d6b4cc91c8b32064ce7ef90e706679f.png

 

But nothing's happening.

Going to kill the process, reboot and attempt the verification again.

EDIT: what a shame that Imgburn cannot do a repeated directory verification, it can only verify an image. :-(

Edited by Jack_Brody
Link to comment
Share on other sites

The problem was in the burner much likely. When I chose to reboot the system, the screen went off and nothing was happening until I unplugged the burner from the computer. It then rebooted.

I verified the BD-R, there was no problem at all (I was especially focused on the 80% part), RPM stable and read speed went constantly up. So I guess the drive just stopped communicating with Imgburn during the verification process.

BTW this is the graph of the burning process, nothing suspicios at 80%:

image.png.84903ad5e1cdd6db68458a7cf60861c3.png

Edited by Jack_Brody
Link to comment
Share on other sites

What country do you live in?  I'm seeing more and more instances on this board of Verbatim BD-R being made by CMC Magnetics.  The ones I keep getting from Amazon.com in the US are VERBAT-IM and still continue to be the "good" stuff.

 

Anyway, I'd be wary of those CMC MAG discs, too.  The nature of their media is you can go half way through a stack with "no problems," then encounter the entire rest useless.  That's how cheap and unreliable CMC is.  Unfortunately, CMC now OWNS Verbatim.  :angry:

Link to comment
Share on other sites

In future, if you encounter weird problems like that, try powering off the PC if the BD drive is internal or powering off the enclosure if it's external.  Don't just reboot.  A power cycle can clear out sometimes weird nagging things like that.

Link to comment
Share on other sites

If you want to be really safe should the device ever drop communication, power off the enclosure, power off the PC, restart the PC, and power back on the enclosure.  This would ensure a complete wipe of everything in memory from ImgBurn/Windows/the device.

 

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.