error trying to write BluRay disk

[wa4zlw]

Just tried to burn a bluray (DL 50gb) and get the following errors. Any ideas?

Drive is ATAPI iHES112 3

I tried to burn a .ISO and then tried to add folders to a project and got same results

 

Thanks leon

 

I 08:42:26 ImgBurn Version 2.5.8.0 started!
I 08:42:26 Microsoft Windows 8 Professional x64 Edition (6.2, Build 9200)
I 08:42:26 Total Physical Memory: 8,386,536 KiB  -  Available: 5,849,760 KiB
I 08:42:26 Initialising SPTI...
I 08:42:26 Searching for SCSI / ATAPI devices...
I 08:42:28 -> Drive 1 - Info: HL-DT-ST DVD-RAM GH10N EX02 (H:) (SATA)
I 08:42:28 -> Drive 2 - Info: ATAPI iHES112   3 ML02 (I:) (SATA)
I 08:42:28 Found 1 DVD±RW/RAM and 1 BD-ROM/DVD±RW!
I 08:44:31 Operation Started!
I 08:44:31 Source File: D:\xfer\Vault\disk1.iso
I 08:44:31 Source File Sectors: 23,521,056 (MODE1/2048)
I 08:44:31 Source File Size: 48,171,122,688 bytes
I 08:44:31 Source File Volume Identifier: THE RODDENBERRY VAULT  DISC 1
I 08:44:31 Source File Volume Set Identifier: 03C5E5C6        THE RODDENBERRY VAULT  DISC 1
I 08:44:31 Source File Application Identifier: ScenaristScenaristBD
I 08:44:31 Source File Implementation Identifier: ScenaristScenaristBD
I 08:44:31 Source File File System(s): UDF (2.50)
I 08:44:31 Destination Device: [0:0:0] ATAPI iHES112   3 ML02 (I:) (SATA)
I 08:44:31 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000)
I 08:44:31 Destination Media Sectors: 24,438,784
I 08:44:31 Write Mode: BD
I 08:44:31 Write Type: DAO
I 08:44:31 Write Speed: MAX
I 08:44:31 Hardware Defect Management Active: No
I 08:44:31 BD-R Verify Not Required: Yes
I 08:44:31 Link Size: Auto
I 08:44:31 Lock Volume: Yes
I 08:44:31 Test Mode: No
I 08:44:31 OPC: No
I 08:44:31 BURN-Proof: Enabled
I 08:44:31 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x)
I 08:44:31 CD/DVD Life Record Count: 11 - CD/DVD Record Count: 4
I 08:44:32 Filling Buffer... (80 MiB)
I 08:44:33 Writing LeadIn...
W 08:44:33 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (1 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (2 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (3 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (4 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (5 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (6 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:33 Retrying (7 of 20)...
W 08:44:33 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (8 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (9 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (10 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (11 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (12 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (13 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (14 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (15 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (16 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (17 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (18 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (19 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:34 Retrying (20 of 20)...
W 08:44:34 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:44 Retrying (21)...
W 08:44:44 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:46 Retrying (22)...
W 08:44:46 Retry Failed - Reason: Invalid Command Operation Code
W 08:44:47 Retrying (23)...
W 08:44:47 Retry Failed - Reason: Invalid Command Operation Code
E 08:44:48 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
I 08:44:48 Synchronising Cache...
W 08:44:48 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
E 08:44:52 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 08:44:55 User opted to skip the 'Close Track/Session/Disc' functions.
E 08:44:55 Failed to Write Image!
E 08:44:55 Operation Failed! - Duration: 00:00:24
I 08:44:55 Average Write Rate: N/A - Maximum Write Rate: N/A
I 08:46:02 Operation Started!
I 08:46:02 Source File: D:\xfer\Vault\disk1.iso
I 08:46:02 Source File Sectors: 23,521,056 (MODE1/2048)
I 08:46:02 Source File Size: 48,171,122,688 bytes
I 08:46:02 Source File Volume Identifier: THE RODDENBERRY VAULT  DISC 1
I 08:46:02 Source File Volume Set Identifier: 03C5E5C6        THE RODDENBERRY VAULT  DISC 1
I 08:46:02 Source File Application Identifier: ScenaristScenaristBD
I 08:46:02 Source File Implementation Identifier: ScenaristScenaristBD
I 08:46:02 Source File File System(s): UDF (2.50)
I 08:46:02 Destination Device: [0:0:0] ATAPI iHES112   3 ML02 (I:) (SATA)
I 08:46:02 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000)
I 08:46:02 Destination Media Sectors: 24,438,784
I 08:46:02 Write Mode: BD
I 08:46:02 Write Type: DAO
I 08:46:02 Write Speed: MAX
I 08:46:02 Hardware Defect Management Active: No
I 08:46:02 BD-R Verify Not Required: Yes
I 08:46:02 Link Size: Auto
I 08:46:02 Lock Volume: Yes
I 08:46:02 Test Mode: No
I 08:46:02 OPC: No
I 08:46:02 BURN-Proof: Enabled
I 08:46:03 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x)
I 08:46:03 CD/DVD Life Record Count: 11 - CD/DVD Record Count: 4
I 08:46:03 Filling Buffer... (80 MiB)
I 08:46:03 Writing LeadIn...
W 08:46:03 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (1 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (2 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (3 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (4 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (5 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (6 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (7 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (8 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (9 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (10 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (11 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (12 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (13 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (14 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (15 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (16 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (17 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (18 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (19 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:03 Retrying (20 of 20)...
W 08:46:03 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:06 Retrying (21)...
W 08:46:06 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:07 Retrying (22)...
W 08:46:07 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:07 Retrying (23)...
W 08:46:07 Retry Failed - Reason: Invalid Command Operation Code
W 08:46:08 Retrying (24)...
W 08:46:08 Retry Failed - Reason: Invalid Command Operation Code
E 08:46:09 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
I 08:46:09 Synchronising Cache...
W 08:46:09 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 08:46:11 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 08:46:12 User opted to skip the 'Close Track/Session/Disc' functions.
E 08:46:12 Failed to Write Image!
E 08:46:12 Operation Failed! - Duration: 00:00:09
I 08:46:12 Average Write Rate: N/A - Maximum Write Rate: N/A
I 09:34:54 Operation Started!
I 09:34:54 Source File: D:\xfer\Vault\disk1.iso
I 09:34:54 Source File Sectors: 23,521,056 (MODE1/2048)
I 09:34:54 Source File Size: 48,171,122,688 bytes
I 09:34:54 Source File Volume Identifier: THE RODDENBERRY VAULT  DISC 1
I 09:34:54 Source File Volume Set Identifier: 03C5E5C6        THE RODDENBERRY VAULT  DISC 1
I 09:34:54 Source File Application Identifier: ScenaristScenaristBD
I 09:34:54 Source File Implementation Identifier: ScenaristScenaristBD
I 09:34:54 Source File File System(s): UDF (2.50)
I 09:34:54 Destination Device: [0:0:0] ATAPI iHES112   3 ML02 (I:) (SATA)
I 09:34:54 Destination Media Type: BD-R (Disc ID: RITEK-DR3-000)
I 09:34:54 Destination Media Sectors: 24,438,784
I 09:34:54 Write Mode: BD
I 09:34:54 Write Type: DAO
I 09:34:54 Write Speed: MAX
I 09:34:54 Hardware Defect Management Active: No
I 09:34:54 BD-R Verify Not Required: Yes
I 09:34:54 Link Size: Auto
I 09:34:54 Lock Volume: Yes
I 09:34:54 Test Mode: No
I 09:34:54 OPC: No
I 09:34:54 BURN-Proof: Enabled
I 09:34:56 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x)
I 09:34:56 CD/DVD Life Record Count: 11 - CD/DVD Record Count: 4
I 09:34:56 Filling Buffer... (80 MiB)
I 09:34:57 Writing LeadIn...
W 09:34:57 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (1 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (2 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (3 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (4 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (5 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (6 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (7 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (8 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (9 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (10 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (11 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (12 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (13 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (14 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (15 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (16 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (17 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (18 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (19 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
W 09:34:57 Retrying (20 of 20)...
W 09:34:57 Retry Failed - Reason: Invalid Command Operation Code
E 09:35:00 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
I 09:35:00 Synchronising Cache...
W 09:35:00 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
E 09:35:02 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 09:35:04 User opted to skip the 'Close Track/Session/Disc' functions.
E 09:35:04 Failed to Write Image!
E 09:35:04 Operation Failed! - Duration: 00:00:10
I 09:35:04 Average Write Rate: N/A - Maximum Write Rate: N/A
W 09:36:13 User accepted disc space warning and is attempting to overburn!
I 09:36:13 Operation Started!
I 09:36:13 Source File: D:\xfer\Vault\disk1.iso
I 09:36:13 Source File Sectors: 23,521,056 (MODE1/2048)
I 09:36:13 Source File Size: 48,171,122,688 bytes
I 09:36:13 Source File Volume Identifier: THE RODDENBERRY VAULT  DISC 1
I 09:36:13 Source File Volume Set Identifier: 03C5E5C6        THE RODDENBERRY VAULT  DISC 1
I 09:36:13 Source File Application Identifier: ScenaristScenaristBD
I 09:36:13 Source File Implementation Identifier: ScenaristScenaristBD
I 09:36:13 Source File File System(s): UDF (2.50)
I 09:36:13 Destination Device: [0:0:0] ATAPI iHES112   3 ML02 (I:) (SATA)
I 09:36:13 Destination Media Type: BD-R (Disc ID: RITEK-BR2-000)
I 09:36:13 Destination Media Sectors: 12,219,392
I 09:36:13 Write Mode: BD
I 09:36:13 Write Type: DAO
I 09:36:13 Write Speed: MAX
I 09:36:13 Hardware Defect Management Active: No
I 09:36:13 BD-R Verify Not Required: Yes
I 09:36:13 Link Size: Auto
I 09:36:13 Lock Volume: Yes
I 09:36:13 Test Mode: No
I 09:36:13 OPC: No
I 09:36:13 BURN-Proof: Enabled
I 09:36:13 Write Speed Successfully Set! - Effective: 35,960 KB/s (8x)
I 09:36:13 CD/DVD Life Record Count: 11 - CD/DVD Record Count: 4
I 09:36:13 Filling Buffer... (80 MiB)
I 09:36:13 Writing LeadIn...
W 09:36:13 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (1 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (2 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (3 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (4 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (5 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (6 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (7 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (8 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (9 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (10 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (11 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (12 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (13 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (14 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (15 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (16 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (17 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (18 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (19 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:13 Retrying (20 of 20)...
W 09:36:13 Retry Failed - Reason: Invalid Command Operation Code
E 09:36:20 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
I 09:36:20 Synchronising Cache...
W 09:36:20 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
E 09:36:23 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 09:36:24 User opted to skip the 'Close Track/Session/Disc' functions.
E 09:36:24 Failed to Write Image!
E 09:36:24 Operation Failed! - Duration: 00:00:11
I 09:36:24 Average Write Rate: N/A - Maximum Write Rate: N/A
W 09:36:29 User accepted disc space warning and is attempting to truncate!
I 09:36:30 Operation Started!
I 09:36:30 Source File: D:\xfer\Vault\disk1.iso
I 09:36:30 Source File Sectors: 23,521,056 (MODE1/2048)
I 09:36:30 Source File Size: 48,171,122,688 bytes
I 09:36:30 Source File Volume Identifier: THE RODDENBERRY VAULT  DISC 1
I 09:36:30 Source File Volume Set Identifier: 03C5E5C6        THE RODDENBERRY VAULT  DISC 1
I 09:36:30 Source File Application Identifier: ScenaristScenaristBD
I 09:36:30 Source File Implementation Identifier: ScenaristScenaristBD
I 09:36:30 Source File File System(s): UDF (2.50)
I 09:36:30 Destination Device: [0:0:0] ATAPI iHES112   3 ML02 (I:) (SATA)
I 09:36:30 Destination Media Type: BD-R (Disc ID: RITEK-BR2-000)
I 09:36:30 Destination Media Sectors: 12,219,392
I 09:36:30 Write Mode: BD
I 09:36:30 Write Type: DAO
I 09:36:30 Write Speed: MAX
I 09:36:30 Hardware Defect Management Active: No
I 09:36:30 BD-R Verify Not Required: Yes
I 09:36:30 Link Size: Auto
I 09:36:30 Lock Volume: Yes
I 09:36:30 Test Mode: No
I 09:36:30 OPC: No
I 09:36:30 BURN-Proof: Enabled
I 09:36:30 Write Speed Successfully Set! - Effective: 35,960 KB/s (8x)
I 09:36:30 CD/DVD Life Record Count: 11 - CD/DVD Record Count: 4
I 09:36:30 Filling Buffer... (80 MiB)
I 09:36:30 Writing LeadIn...
W 09:36:30 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (1 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (2 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (3 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (4 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (5 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (6 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (7 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (8 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (9 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (10 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (11 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (12 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (13 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (14 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (15 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (16 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (17 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (18 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (19 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
W 09:36:30 Retrying (20 of 20)...
W 09:36:30 Retry Failed - Reason: Invalid Command Operation Code
E 09:36:32 Failed to Write Sectors 0 - 31 - Reason: Invalid Command Operation Code
I 09:36:32 Synchronising Cache...
W 09:36:32 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
E 09:36:33 Synchronise Cache Failed! - Reason: Invalid Command Operation Code
W 09:36:34 User opted to skip the 'Close Track/Session/Disc' functions.
E 09:36:34 Failed to Write Image!
E 09:36:34 Operation Failed! - Duration: 00:00:04
I 09:36:34 Average Write Rate: N/A - Maximum Write Rate: N/A
 

[wa4zlw]

ATAPI iHES112   3 ML02 (SATA)
Current Profile: BD-R

Disc Information:
Status: Empty
State of Last Session: Empty
Erasable: No
Free Sectors: 24,438,784
Free Space: 50,050,629,632 bytes
Free Time: 5430:52:34 (MM:SS:FF)
Next Writable Address: 0
MID: RITEK-DR3-000

Disc Definition Structure:
Certified: No
Scanned: No

BD Disc Information (L0):
Disc ID: RITEK-DR3-000
Disc Type: BD-R
Disc Size: 120 mm
Disc Class: 0
Disc Version: 1
Number of Layers: 2
Layer Type: Writable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50 nm (25 GB Per Layer)
Push-Pull Polarity: Positive
Recorded Mark Polarity: HTL
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 131,072
Last PAA of Data Zone: 1,658,494

BD Disc Information (L1):
Disc ID: RITEK-DR3-000
Disc Type: BD-R
Disc Size: 120 mm
Disc Class: 0
Disc Version: 1
Number of Layers: 2
Layer Type: Writable
DVD Layer Present: No
CD Layer Present: No
Channel Bit Length: 74.50 nm (25 GB Per Layer)
Push-Pull Polarity: Positive
Recorded Mark Polarity: HTL
BCA Present: Yes
Maximum Transfer Rate: Not Specified
First PAA of Data Zone: 2,535,808
Last PAA of Data Zone: 4,063,230

Format Capacities:
DT: 0x01 - NB: 24438784 (0x0174E800) - TDP: 413696
FT: 0x00 - NB: 23652352 (0x0168E800) - TDP: 24576
FT: 0x32 - NB: 0 (0x00000000) - TDP: 0
FT: 0x32 - NB: 23259136 (0x0162E800) - TDP: 0
FT: 0x32 - NB: 24307712 (0x0172E800) - TDP: 0

[dbminter]

Never heard of an Invalid Operation Code error before, so LUK will have to comment further on that.

 

 

If I had to hazard a guess, your drive probably doesn't like the RITEK BD-R DL.  Ritek DVD+R DL were problematic with users and my experience with them was more than half of the ones I successfully burned weren't readable 5 years later.  People have a sort of 50/50 result with Ritek media, even the single layer, on their burners.  RiData was even worse quality.

[wa4zlw]

HNY and thanks for the quick reply. I also tried my single layer memorex with same results.These are labeled quantum and got them since my friend uses them with success.

 

leon

[dbminter]

Memorex single layer BD-R would also, most likely, be Ritek media.  Last time I bought their BD-R SL and BD-RE SL, they were Ritek.  The PS3 didn't like the Ritek BD-R for playback, playing with skips and jumps in the video, sometimes skipping entire video streams on playback.

 

 

If you can find it, try Verbatim BD-R.  I know you can find those at Office Depot, and they're made by Verbatim.  I use them all the time without an issue that wasn't caused by a dying/bad drive.  If you have a problem with those, then it's most likely your drive that's the problem.

 

 

Oh, wait, you said these Memorex were labeled Quantum?  Labeled Quantum on the package?  What's the Disc ID in the Disc Information?  I've never used any of Quantum's labeled media, but it's probably cheap and could be a culprit, too.

[wa4zlw]

no I have memorex single layer and quantum dual. I got the quantum off amazon. I guess I could return and get verbatim.

[dbminter]

I don't have any experience with BD-R DL.  I do have some Verbatim BD-RE DL.  My LG doesn't like the inkjet printable ones Verbatim started making themselves.  Before, Verbatim farmed them out to TDK, which the LG likes.  The LG likes the SAME Disc ID on Verbatim's branded BD-RE DL.  My Pioneer doesn't mind these inkjet BD-RE DL's from Verbatim.

 

 

If the BD-R DL experience is the same experience as DVD+R DL, then only Verbatims are really any choice to go with.  There's always a tricky issue when switching layers.  Although I had no issues with the few TDK DVD+R DL's I tried.  The Ritek DVD+R DL weren't reliable.

[LIGHTNING UK!]

Your drive can't burn BD discs, it can only read them. It'll burn DVDs though.

 

You have what's known as a 'combo' drive.

[dbminter]

Ah, that explains the Invalid Command error.  It can't perform a write command because it's not a writer. 

[wa4zlw]

OMG!!! NO wonder. This should have been a BD writer - UGH no to find one. Many thanks guys for the very prompt replies and happy new year. I'll keep you posted.

 

Leon :

[dbminter]

I've learned you have to be careful with how drives are described online.  I came across what I thought was a BD burner because it listed write speeds prominently.  Closer investigation revealed the drive only read BD, not burned them.  It was a DVD/CD burner, but not a BD writer.  A combo drive.

[wa4zlw]

UPDATE: got the drive thursday and burning discs now. THanks for the assist.

 

Leon