Failed to Read Sector 16580608

[yup]

During last 3 years I am using the same computer, the same DVD burner (LiteOn iHAS124A), and only Verbatim DVD-R MCC 03RG20 made by UAE and Taiwan. Something about 700 disks are burned, and I am quite satisfied with their "Disk Quality" scans. But a few weeks ago I was not able to find the above-mentioned disks and have to buy 03RG20 made by India. Scans of first of these disks were much, much worse. After a series of experiments I found that the only way to get acceptable quality of burn is to use the next combination of drive settings: "speed: 16x; OPC: disabled; Smartburn: disabled; Online Hyper Tuning: enabled; Force Hyper Tuning: enabled".

But now verification of almost every (in fact - successfully written) disk fails at the very beginning with the next diagnostics:

I 19:00:01 Cycling Tray before Verify...
W 19:00:11 Waiting for device to become ready...
I 19:01:11 Device Ready!
I 19:01:11 Operation Started!
I 19:01:11 Source Device: [1:1:0] ATAPI iHAS124   A BL0U (Z:) (ATA)
I 19:01:11 Source Media Type: DVD-R (Book Type: DVD-ROM) (Disc ID: MCC 03RG20)
I 19:01:11 Image File: -==/\/[BUILD IMAGE]\/\==-
I 19:01:11 Image File Sectors: 2 036 192 (MODE1/2048)
I 19:01:11 Image File Size: 4 170 121 216 bytes
I 19:01:11 Image File Volume Identifier: XXXXXXXXXXX
I 19:01:11 Image File Volume Set Identifier: 432296CB001F11DD
I 19:01:11 Image File Application Identifier: IMGBURN V2.5.6.0 - THE ULTIMATE IMAGE BURNER!
I 19:01:11 Image File Implementation Identifier: ImgBurn
I 19:01:11 Image File File System(s): ISO9660; UDF (1.02)
I 19:01:11 Read Speed (Data/Audio): MAX / MAX
I 19:01:12 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2036191)
I 19:01:12 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2036191)
W 19:01:13 Failed to Read Sector 16580608 - Reason: Logical Block Address out of Range
W 19:01:19 Retrying (1)...
W 19:01:19 Retry Failed - Reason: Logical Block Address out of Range
W 19:01:21 Retrying (2)...

And 16580608 is the magic number! It's irrelevant how much data is written (3 GB or 4.5 GB) - that number in the "Failed to Read Sector" message every time is the same.

And yet one strange thing is that program tries to read this sector (quite far from the start of disk) at the very beginning of verification.

 

What's this?

If this a firmware bug, then why program starts disk verification from this sector?

If this a program bug, then why it exposed only now and never happened before?

Edited September 18, 2013 by yup

[LIGHTNING UK!]

You're using an old version of ImgBurn. Try the current release and post a new log if you still have the same issue please.

[yup]

I had tried version 2.5.8.0 even before posting - with the same result:

I 00:07:42 Cycling Tray before Verify...
W 00:07:52 Waiting for device to become ready...
I 00:08:53 Device Ready!
I 00:08:53 Operation Started!
I 00:08:53 Source Device: [1:1:0] ATAPI iHAS124   A BL0U (Z:) (ATA)
I 00:08:53 Source Media Type: DVD-R (Book Type: DVD-ROM) (Disc ID: MCC 03RG20)
I 00:08:53 Source Media Supported Read Speeds: 2x; 4x; 6x; 8x; 12x; 16x
I 00:08:53 Source Media Sectors: 2 293 888 (Track Path: PTP)
I 00:08:53 Source Media Size: 4 697 882 624 bytes
I 00:08:53 Image File: -==/\/[BUILD IMAGE]\/\==-
I 00:08:53 Image File Sectors: 2 293 888 (MODE1/2048)
I 00:08:53 Image File Size: 4 697 882 624 bytes
I 00:08:53 Image File Volume Identifier: XXXXXXXXX
I 00:08:53 Image File Volume Set Identifier: 4333001A00230071
I 00:08:53 Image File Application Identifier: IMGBURN V2.5.8.0 - THE ULTIMATE IMAGE BURNER!
I 00:08:53 Image File Implementation Identifier: ImgBurn
I 00:08:53 Image File File System(s): ISO9660; UDF (1.02)
I 00:08:53 Read Speed (Data/Audio): MAX / MAX
I 00:08:54 Read Speed - Effective: 6,4x - 16x
I 00:08:54 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2293887)
I 00:08:54 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2293887)
W 00:08:56 Failed to Read Sectors 16580608 - 16580639 - Reason: Logical Block Address out of Range
W 00:08:56 Failed to Read Sector 16580608 - Reason: Logical Block Address out of Range
E 00:10:03 Failed to Read Sector 16580608 - Reason: Logical Block Address out of Range
E 00:10:03 Failed to Verify Sectors!
E 00:10:08 Operation Failed! - Duration: 00:01:10

Edited September 18, 2013 by yup

[LIGHTNING UK!]

I have no clue how or why it would be doing that.

 

Can you please go into Read mode and copy + paste the disc info from the box on the right when that disc is in the drive?

[yup]

This info is from a blank disk:

ATAPI iHAS124   A BL0U (ATA)
Current Profile: DVD-R

Disc Information:
Status: Empty
State of Last Session: Empty
Erasable: No
Free Sectors: 2 297 888
Free Space: 4 706 074 624 bytes
Free Time: 510:40:38 (MM:SS:FF)
Next Writable Address: 0
MID: MCC 03RG20
Supported Read Speeds: 2x; 4x; 6x; 8x; 12x; 16x
Current Read Speed: 6,4x - 16x

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Physical Format Information (Last Recorded):
Book Type: DVD-R
Part Version: 5
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196 608
Last Physical Sector of Data Area: 0
Last Physical Sector in Layer 0: 0

and this one is from a burned one:

ATAPI iHAS124   A BL0U (ATA)
Current Profile: DVD-R

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: No
Sessions: 1
Sectors: 2 293 888
Size: 4 697 882 624 bytes
Time: 509:47:13 (MM:SS:FF)
MID: MCC 03RG20
Supported Read Speeds: 2x; 4x; 6x; 8x; 12x; 16x
Current Read Speed: 2,4x - 6x

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2293887)
-> LeadOut  (LBA: 2293888)

Track Information:
Session 1...
-> Track 01 (LTSA: 16580608, LTS: 2293888, LRA: 0)

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Physical Format Information (Last Recorded):
Book Type: DVD-ROM
Part Version: 0
Disc Size: 120 mm
Maximum Read Rate: 2.52 Mbps
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 0
Last Physical Sector of Data Area: 0
Last Physical Sector in Layer 0: 0

Is "Track Information" correct?

 

(BTW, hex representation of that 16580608 is quite interesting.)

 

This is from one of first disks, that were burned with usual (for me) "speed: 6x; OPC: enabled; Smartburn: enabled; Online Hyper Tuning: disabled; Force Hyper Tuning: disabled":

Disc Information:
Status: Complete
State of Last Session: Complete
Erasable: No
Sessions: 1
Sectors: 2 232 256
Size: 4 571 660 288 bytes
Time: 496:05:31 (MM:SS:FF)
MID: MCC 03RG20
Supported Read Speeds: 2x; 4x; 6x; 8x; 12x; 16x
Current Read Speed: 8x

File System Information:
Sectors: 2 232 256
Size: 4 571 660 288 bytes
Time: 496:05:31 (MM:SS:FF)

TOC Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 2232255)
-> LeadOut  (LBA: 2232256)

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2232256, LRA: 2232255)

Pre-recorded Information:
Manufacturer ID: MCC 03RG20

Recording Management Area Information:
ATAPI iHAS124 A

Physical Format Information (Last Recorded):
Book Type: DVD-R
Part Version: 5
Disc Size: 120 mm
Maximum Read Rate: Not Specified
Number of Layers: 1
Track Path: Parallel Track Path (PTP)
Linear Density: 0.267 um/bit
Track Density: 0.74 um/track
First Physical Sector of Data Area: 196 608
Last Physical Sector of Data Area: 2 428 863
Last Physical Sector in Layer 0: 0

Edited September 19, 2013 by yup

[LIGHTNING UK!]

Ah, that info (number) is coming from the drive. You can see it listed in the track information section of the burnt disc.

 

Did you say it doesn't happen when those advanced drive settings are on the default values (just smartburn enabled) ?

 

I assume that's the most recent firmware on the drive?

[yup]

Did you say it doesn't happen when those advanced drive settings are on the default values (just smartburn enabled) ?

Yes, exactly. And "enabled" for "Smartburn" is the default value too.

Three years ago I tried different settings and deduced that different speeds and "enable/disable" for "Smartburn" have no influence on quality, and enabling of "Hyper Tuning" makes it worse. So I left everything in the default state and always burned at min. speed.

 

I assume that's the most recent firmware on the drive?

Yes, BL0U is the latest version for iHAS124A.

Edited September 19, 2013 by yup

[LIGHTNING UK!]

Ok so if it doesn't happen with the drive settings on their default values, the incorrect LTSA (logical track start address) value must be coming from one of those being turned on. This is a firmware bug.

 

If I can reproduce it my end, I may be able to implement some sort of workaround for the problem.

[yup]

Well... I have to live with it somehow... Can you tell how dangerous is this bug? Is it possible that some DVD drives or player will refuse to read these disks?

 

Update: I have borrowed a burner of different model (iHAS122W), and for the disk from the previous post it reports:

Track Information:
Session 1...
-> Track 01 (LTSA: 0, LTS: 2293888, LRA: 2293887)

P.S.  I have some very unusual information. Not about ImgBurn or any particular drive, but about DVD burning in general. May I send a PM to you?

Edited September 19, 2013 by yup

[LIGHTNING UK!]

Is the drive just reporting that weird LTSA for that disc when those drive features are activated? So put them back to their default values and check the disc info again (eject + reinsert the disc before looking). I want to work out if it's messing up when burning or when reading.

 

The iHAS122W uses a non Mediatek chipset I believe - it's more of an Optiarc drive than a traditional LiteOn one.

 

'unusual information'... I'm intrigued, PM away.

[yup]

Is the drive just reporting that weird LTSA for that disc when those drive features are activated?

I started to check this (for already burned disks) immediately after posting info about iHAS122W

Result: even with all default settings (end even after power off - power on) reported LTSA is incorrect.

 

Also I was trying to determine: if this is just a reporting issue - then why it affects newly burned disks only, but not any old one?

It was not mentioned before but all those disks that were burned with "Hyper Tuning: enabled" have the same feature: they take enormously long time for recognizing by the drive - more then a minute. So I supposed a timing problem.

What was discovered then:

If a disk is inserted when ImgBurn already in the "Read" mode then LTSA = 16580608.

If ImgBurn is switched to the "Read" mode almost immediately after recognizing of the disk then LTSA = 16580608.

But if I wait enough time after recognizing and only then switch ImgBurn to the "Read" mode then LTSA = 0!

 

 

The iHAS122W uses a non Mediatek chipset I believe - it's more of an Optiarc drive than a traditional LiteOn one.

It is built on a Renesas processor (as a half of LG models). But it is not a rebadged LG - its mechanics and electronics definitely are LiteOn's own.

Edited September 20, 2013 by yup

[yup]

Yesterday I was informed by one person that he was not able to reproduce my results on his iHAS624A (firmware ver. ZL2U).

So today I crossflashed my 124A to 624A and burned a disk. Really, there was no any problem: no enormously long time for recognition of this disk, no wrong LTSA!

But all disks that were burned before still revealed the same problem on insertion.

Then I converted my drive back to 124A (f/w ver. BL0U) and burned yet one disk. The problem has returned back But not for disk, burned by ZL2U! It still works perfectly.

So there is clear difference between disks burned by f/w for 124A and 624A on the same device.

 

I understand that this is out of your control, and you can't and shouldn't do anything with it. All this is just for your information.

Edited September 24, 2013 by yup