Not burning L1 tracks on DL disks correctly

[basejumper]

I recently purchased a LG GSA-H42N DVD Drive (With Rl01 Firmware) after my existing LG GSA-H10A laser started to fail. I have always used Imgburn to burn Dual Layered disks and never had a problem. I have always used Aone DL disks (Ricoh) at 2.4x or 4x and never had a problem on the old drive with bad burns etc.

 

I burnt a full disk with imgburn on my new drive and check the log which was normal with no error or anything reported bad at all. When I try to read the disk is says unreadable. I forced a clone of the disk and its reads fine until its on L1 of the DL disk and then reports lots of bad reads. I thought the disks at bad, but tried on another burner with different burning software and no problems at all.

 

Is there a compatibility issue known with this drive with imgburn or do you think the drive is faulty, just seems strange that the log shows no problems at all and suggests it burnt perfectly when it fact its hasnt?

 

Thanks for any assistance.

[blutach]

I have always used Aone DL disks (Ricoh) at 2.4x or 4x and never had a problem on the old drive with bad burns etc.

Switch to Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore - they are the only good DL discs.

 

Regards

[basejumper]

I have always used Aone DL disks (Ricoh) at 2.4x or 4x and never had a problem on the old drive with bad burns etc.

Switch to Verbatim, +R, 2.4x, MKM-001-00, Made in Singapore - they are the only good DL discs.

 

Regards

 

Just bought some and exactly the same problem at both 2.4x and 4x. After 500+ burns on Aone disks without a problem, I would have been surprised. Its sounds like a drive/imgburn issue as I have just installed Cdclone and tried again and this time the burn works fine. I dont want to switch to CDClone as I am happy with Imgburn, but one works and one doesnt??

[dontasciime]

One works one doesn't "fluke" the one that worked would have worked in any burning program your drive has seen some action so replace it if you cannot write to verbatim.

 

Stick with A-one and clone if your happy with that. But burning to those disc's and not being able to read them back just means the media is poor or your drive has had it's got nothing to do with ImgBurn (how could it)

[LIGHTNING UK!]

Post the log of your latest burn+verify.

 

Drives frequently say a disc has burnt correctly when it hasn't, that's the whole point of the Verify phase.

 

ImgBurn doesn't guess at errors, the drive has to return one for ImgBurn to display it to the user.

[basejumper]

Post the log of your latest burn+verify.

 

Drives frequently say a disc has burnt correctly when it hasn't, that's the whole point of the Verify phase.

 

ImgBurn doesn't guess at errors, the drive has to return one for ImgBurn to display it to the user.

 

As requested:

 

I 09:15:51 ImgBurn Version 2.4.1.0 started!

I 09:15:51 Microsoft Windows XP Home Edition (5.1, Build 2600 : Service Pack 2)

I 09:15:51 Total Physical Memory: 523,760 KB - Available: 280,092 KB

I 09:15:51 Initialising SPTI...

I 09:15:51 Searching for SCSI / ATAPI devices...

I 09:16:03 Found 1 CD-RW, 1 DVD-ROM and 1 DVD

[basejumper]

One works one doesn't "fluke" the one that worked would have worked in any burning program your drive has seen some action so replace it if you cannot write to verbatim.

 

Stick with A-one and clone if your happy with that. But burning to those disc's and not being able to read them back just means the media is poor or your drive has had it's got nothing to do with ImgBurn (how could it)

 

That was my old drive which had worked fine for years with Imgburn and Aone. This problem is on my new brand new drive, which I have tried 10 burns on Aone and 5 on Verbatims, with a mix of 2.4x and 4x all fail to read with Imgburn. Tried CdClone and worked on all media both at 2.4x and 4x.....beats me...?

[dontasciime]

Post a log of the failed ones then and start by ticking the verify and verify every disc you burn.

 

Otherwise any software/ drive combo can say that it wrote 100% but that means nothing until you have verified the drive or any other drive can read back the data supposedly successfully written.

[LIGHTNING UK!]

burn AND verify please.

[basejumper]

burn AND verify please.

 

As requested with verify switched on, still not able to be read on three other DVD readers, says unreadable disk.

 

I 16:28:42 Operation Started!

I 16:28:42 Source File: C:\Downloads\backup biz

I 16:28:42 Source File Sectors: 3,825,924 (MODE1/2048)

I 16:28:42 Source File Size: 7,835,492,352 bytes

I 16:28:42 Source File Volume Identifier: backup2008

I 16:28:42 Source File Volume Set Identifier: 34672923

I 16:28:42 Source File Implementation Identifier: backup.iso

I 16:28:42 Source File File System(s): ISO9660, UDF (1.02)

I 16:28:42 Destination Device: [1:1:0] HL-DT-ST DVDRAM GSA-H42N RL01 (D:) (ATA)

I 16:28:42 Destination Media Type: DVD+R DL (Disc ID: RICOHJPN-D01-67) (Speeds: 2.4x, 4x, 6x, 8x)

I 16:28:42 Destination Media Sectors: 4,173,824

I 16:28:42 Write Mode: DVD

I 16:28:42 Write Type: DAO

I 16:28:42 Write Speed: 4x

I 16:28:42 Link Size: Auto

I 16:28:42 Test Mode: No

I 16:28:42 OPC: No

I 16:28:42 BURN-Proof: Enabled

I 16:28:42 Book Type Setting: DVD-ROM

I 16:28:42 Optimal L0 Data Zone Capacity: 1,913,760

I 16:28:42 Optimal L0 Data Zone Method: Copied From Original Disc

I 16:29:11 Filling Buffer... (20 MB)

I 16:29:12 Writing LeadIn...

I 16:29:28 Writing Session 1 of 1... (1 Track, LBA: 0 - 3825923)

I 16:29:28 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923)

I 16:29:28 Writing Layer 0... (LBA: 0 - 1913759)

I 16:41:15 Writing Layer 1... (LBA: 1913760 - 3825923)

I 16:53:02 Synchronising Cache...

I 16:53:03 Closing Track...

I 16:53:18 Finalising Disc...

I 16:54:24 Image MD5: 83cd5ac7a3d56adfa43d880fbfb12ab7

I 16:54:24 Operation Successfully Completed! - Duration: 00:25:42

I 16:54:24 Average Write Rate: 5,415 KB/s (3.9x) - Maximum Write Rate: 5,566 KB/s (4.0x)

I 16:54:24 Cycling Tray before Verify...

W 16:54:34 Waiting for device to become ready...

I 16:55:02 Device Ready!

I 16:55:04 Operation Started!

I 16:55:04 Source Device: [1:1:0] HL-DT-ST DVDRAM GSA-H42N RL01 (D:) (ATA)

I 16:55:04 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: RICOHJPN-D01-67) (Speeds: 2.4x, 4x, 6x, 8x)

I 16:55:04 Image File: C:\Downloads\backup biz

I 16:55:04 Image File Sectors: 3,825,924 (MODE1/2048)

I 16:55:04 Image File Size: 7,835,492,352 bytes

I 16:55:04 Image File Volume Identifier: backup2008

I 16:55:04 Image File Volume Set Identifier: 34672923

I 16:55:04 Image File Implementation Identifier: backup.iso

I 16:55:04 Image File File System(s): ISO9660, UDF (1.02)

I 16:55:04 Read Speed (Data/Audio): MAX / MAX

I 16:55:04 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3825923)

I 16:55:04 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923)

I 16:55:04 Verifying Layer 0... (LBA: 0 - 1913759)

I 17:03:24 Verifying Layer 1... (LBA: 1913760 - 3825923)

I 17:09:47 Device MD5: 83cd5ac7a3d56adfa43d880fbfb12ab7

I 17:09:47 Device (Padded) MD5: d0bec20aefc4d33e7a185ab825be06ac

I 17:09:47 Image MD5: 83cd5ac7a3d56adfa43d880fbfb12ab7

I 17:09:54 Operation Successfully Completed! - Duration: 00:14:43

I 17:09:54 Average Verify Rate: 8,665 KB/s (6.3x) - Maximum Verify Rate: 11,132 KB/s (8.0x)

[LIGHTNING UK!]

That's weird because the drive there seems to be able to read it back just fine.

 

You could try turning the 'Perform OPC Before Write' option on in the settings (write tab).

[basejumper]

That's weird because the drive there seems to be able to read it back just fine.

 

You could try turning the 'Perform OPC Before Write' option on in the settings (write tab).

 

Its baffled me.... What does this option do? As I mentioned this is only on DL disks, backup on DVD works fine and is read fine. It also seems to be only on L1 either at the Layer break or further along, where if I try to copy the disc it starts to throw up read error. I am beginning to suspect that it could be Firmware in the drive, thats the only thing that has changed. I just came off of the phone to the shop that sold me it and he had updated the drive firmware when he replaced it for me from RL00 to RL01. I just get another and ask them not to update the firmware and see how that goes, unless I'm missed something here?? Thanks for all your help.

[blutach]

It does a test write into the OPC area - search the forums for a better explanation or read the guides.

 

Regards