Jump to content

Recommended Posts

Posted (edited)

I was 90% with done with a burn when the following error cropped up:

Quote

Failed to Write Sectors 32869568 - 32869599 - Reason: Write Error
Retry Failed - Reason: Invalid Address For Write

Drive, Plugged in via Micro-USB to USB-A into a USB-3 powered USB Hub. Drive has been able to rip disks over long periods of time without issue. 

Firmware is going to reflect a different model, this is unofficial firmware that allows the drivee to access UHD format disks. Given the use case I would prefer to not alter the firmware. 

Discs

Log:

Quote

I 16:45:33 Operation Started!
I 16:45:33 Source File: B:\ISOs\Disc_001.iso
I 16:45:33 Source File Sectors: 36,257,088 (MODE1/2048)
I 16:45:33 Source File Size: 74,254,516,224 bytes
I 16:45:33 Source File Volume Identifier: PXCS_4K_001
I 16:45:33 Source File Volume Set Identifier: 597A777402293CF1
I 16:45:33 Source File Application Identifier: ImgBurn v2.5.8.0
I 16:45:33 Source File Implementation Identifier: ImgBurn
I 16:45:33 Source File File System(s): UDF (2.60)
I 16:45:33 Destination Device: [0:0:0] HL-DT-ST BD-RE BP60NB10 1.00 (D:) (USB)
I 16:45:33 Destination Media Type: BD-R (Disc ID: VERBAT-IMk-000)
I 16:45:33 Destination Media Supported Write Speeds: 2x, 4x
I 16:45:33 Destination Media Sectors: 48,878,592
I 16:45:33 Write Mode: BD
I 16:45:33 Write Type: DAO
I 16:45:33 Write Speed: 2x
I 16:45:33 Hardware Defect Management Active: No
I 16:45:33 BD-R Verify Not Required: Yes
I 16:45:33 Link Size: Auto
I 16:45:33 Lock Volume: Yes
I 16:45:33 Test Mode: No
I 16:45:33 OPC: No
I 16:45:33 BURN-Proof: Enabled
I 16:45:36 Write Speed Successfully Set! - Effective: 8,992 KB/s (2x)
I 16:46:45 Filling Buffer... (80 MiB)
I 16:46:46 Writing LeadIn...
I 16:46:56 Writing Session 1 of 1... (1 Track, LBA: 0 - 36257087)
I 16:46:56 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 36257087)
W 18:52:03 Failed to Write Sectors 32869568 - 32869599 - Reason: Write Error
W 18:52:03 Retrying (1 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (2 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (3 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (4 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (5 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (6 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (7 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:03 Retrying (8 of 20)...
W 18:52:03 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (9 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (10 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (11 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (12 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (13 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (14 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (15 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (16 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (17 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (18 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (19 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:04 Retrying (20 of 20)...
W 18:52:04 Retry Failed - Reason: Invalid Address For Write
W 18:52:21 Retrying (21)...
W 18:52:21 Retry Failed - Reason: Invalid Address For Write
W 18:52:22 Retrying (22)...
W 18:52:22 Retry Failed - Reason: Invalid Address For Write
W 18:52:22 Retrying (23)...
W 18:52:22 Retry Failed - Reason: Invalid Address For Write
W 18:52:23 Retrying (24)...
W 18:52:23 Retry Failed - Reason: Invalid Address For Write
W 18:52:23 Retrying (25)...
W 18:52:23 Retry Failed - Reason: Invalid Address For Write
W 18:52:23 Retrying (26)...
W 18:52:23 Retry Failed - Reason: Invalid Address For Write
W 18:52:44 Retrying (27)...
W 18:52:44 Retry Failed - Reason: Invalid Address For Write
W 18:52:45 Retrying (28)...
W 18:52:45 Retry Failed - Reason: Invalid Address For Write
W 18:52:46 Retrying (29)...
W 18:52:46 Retry Failed - Reason: Invalid Address For Write
W 18:52:46 Retrying (30)...
W 18:52:46 Retry Failed - Reason: Invalid Address For Write
W 18:52:46 Retrying (31)...
W 18:52:46 Retry Failed - Reason: Invalid Address For Write
W 18:52:46 Retrying (32)...
W 18:52:46 Retry Failed - Reason: Invalid Address For Write
W 18:52:47 Retrying (33)...
W 18:52:47 Retry Failed - Reason: Invalid Address For Write
W 18:52:47 Retrying (34)...
W 18:52:47 Retry Failed - Reason: Invalid Address For Write
W 18:52:47 Retrying (35)...
W 18:52:47 Retry Failed - Reason: Invalid Address For Write
W 18:52:48 Retrying (36)...
W 18:52:48 Retry Failed - Reason: Invalid Address For Write
W 18:52:48 Retrying (37)...
W 18:52:48 Retry Failed - Reason: Invalid Address For Write
W 18:52:48 Retrying (38)...
W 18:52:48 Retry Failed - Reason: Invalid Address For Write
W 18:52:48 Retrying (39)...
W 18:52:48 Retry Failed - Reason: Invalid Address For Write
W 18:52:49 Retrying (40)...
W 18:52:49 Retry Failed - Reason: Invalid Address For Write
W 18:52:49 Retrying (41)...
W 18:52:49 Retry Failed - Reason: Invalid Address For Write
W 18:52:51 Retrying (42)...
W 18:52:51 Retry Failed - Reason: Invalid Address For Write
W 18:52:51 Retrying (43)...
W 18:52:51 Retry Failed - Reason: Invalid Address For Write
W 18:52:51 Retrying (44)...
W 18:52:51 Retry Failed - Reason: Invalid Address For Write
 

 

Error.png

Error2.png

Log Output.txt

Edited by Jim777
Posted

The first error is the important one, not a thing that pops up after a retry. 
 

Your drive reported a ‘write error’ while trying to burn the disc. So, it didn’t like something about it. 
 

if there’s no better firmware you can use, there’s little you can do about it. 
 

if it’s a fluke failure, try another disc. If it keeps failing, you could try enabling the ‘perform opc before write’ option to see if it enables the drive to do a better job. 
Enabling defect management is also an option, but that slows down the burn and uses up disc space. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

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