I/O Error when burning DVD's/Hardware or software issue?

[alegator]

Hi, I have an LG DVD burner (GSA-H42N) that I've used for the last year without any problems. For burning DVD's I use either Nero Burning Rom v7.9.6.0 or ImgBurnv2.4.1.0 and I never had any issues with them either. I always include the burn verification as part of the burning process.Yesterday as I was trying to burn a DVD5 with Nero everything went fine except that in the verification process when it reached 90% it started reporting I/O Read Errors in various sector ranges of the DVD disk. So I aborted the process. Thinking that it might've been Nero the issue, I burned a new DVD5 with ImgBurn and the sane problem: when it reached the verification stage it started reporting the same error after 90% of the verification. Both DVD's can be exploired in its contents with Windows Explorer and can be played with any DVD player (VLC, PowerDVD, etc). So,
- Is this a software issue or is it the DVD burner that is failing?
- The DVD's I burned as described above are "coasters" or can I keep them as valid DVD's?
Thanks

[VegasBud]

alegator,

By any chance did the problem come up when you started using different media than you normally do, or a new batch of disks you've successfully used before? If so, the problem is most likely to be media related.

If you're using the same batch/brand of media that has worked fine before, posting a burn log would help to identify the source of the problem.

[VegasBud]

Sorry, I forgot to answer your second question.

A coaster is a disk that is unuseable. If it's a dvd-video disk that appears to play correctly, a little data corruption isn't a big problem. If it's a data disk, any data corruption makes it unuseable, which qualifies the disk as a coaster.

[alegator]

alegator,

By any chance did the problem come up when you started using different media than you normally do, or a new batch of disks you've successfully used before? If so, the problem is most likely to be media related.

If you're using the same batch/brand of media that has worked fine before, posting a burn log would help to identify the source of the problem.

VegasBud, the media used is the same as the one I normally use, never had any issue with it, and on top of it it belongs to the same batch/brand of DVD's I used before successfully. Unfortunately I did not save the log (unless it's automatically saved?) but as said when the Verification process reached 90% it started to slow down a lot and displayed "I/O Error in sector ...." in various disk ranges after which I aborted.

[VegasBud]

alegator,

In ImgBurn's menus click "Help" - "ImgBurn Logs". There may be many logs in the file, in which case it would be best if you select one where the problem shows. If you also have a log in there from a successful burn, you could also post that, to maybe see what changed between the burns.

[alegator]

alegator,

In ImgBurn's menus click "Help" - "ImgBurn Logs". There may be many logs in the file, in which case it would be best if you select one where the problem shows. If you also have a log in there from a successful burn, you could also post that, to maybe see what changed between the burns.

VegasBud, thanks, I could locate the log, here it is:

; //****************************************\\
; ImgBurn Version 2.4.1.0 - Log
; Wednesday, 21 May 2008, 10:21:02
; \\****************************************//
;
;
I 04:44:33 ImgBurn Version 2.4.1.0 started!
I 04:44:33 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 04:44:33 Total Physical Memory: 2,096,136 KB - Available: 1,474,092 KB
I 04:44:33 Initialising SPTI...
I 04:44:33 Searching for SCSI / ATAPI devices...
I 04:44:34 Found 1 DVD-ROM, 1 DVD±RW and 1 DVD±RW/RAM!
I 04:49:56 Operation Started!
I 04:49:56 Building Image Tree...
I 04:50:06 Checking Directory Depth...
I 04:50:06 Calculating Totals...
I 04:50:06 Preparing Image...
I 04:50:07 Checking Path Length...
I 04:50:07 Contents: 22 Files, 2 Folders
I 04:50:07 Size: 4,702,863,360 bytes
I 04:50:07 Sectors: 2,296,320
I 04:50:07 Image Size: 4,703,485,952 bytes
I 04:50:07 Image Sectors: 2,296,624
E 04:50:15 Operation Aborted! - Duration: 00:00:18
I 04:51:16 Operation Started!
I 04:51:16 Building Image Tree...
I 04:51:16 Checking Directory Depth...
I 04:51:16 Calculating Totals...
I 04:51:16 Preparing Image...
I 04:51:16 Checking Path Length...
I 04:51:16 Contents: 22 Files, 2 Folders
I 04:51:16 Size: 4,702,863,360 bytes
I 04:51:16 Sectors: 2,296,320
I 04:51:16 Image Size: 4,703,485,952 bytes
I 04:51:16 Image Sectors: 2,296,624
I 04:51:22 Operation Successfully Completed! - Duration: 00:00:05
I 04:51:22 Operation Started!
I 04:51:22 Source File: -==/\/[BUILD IMAGE]\/\==-
I 04:51:22 Source File Sectors: 2,296,624 (MODE1/2048)
I 04:51:22 Source File Size: 4,703,485,952 bytes
I 04:51:22 Source File Volume Identifier: JohnsBirthday
I 04:51:22 Source File Application Identifier: IMGBURN V2.4.1.0 - THE ULTIMATE IMAGE BURNER!
I 04:51:22 Source File Implementation Identifier: ImgBurn
I 04:51:22 Source File File System(s): ISO9660, UDF (1.02)
I 04:51:22 Destination Device: [1:0:0] HL-DT-ST DVDRAM GSA-H42N RL01 (G (ATA)
I 04:51:22 Destination Media Type: DVD-R (Disc ID: PRINCO) (Speeds: 2x)
I 04:51:22 Destination Media Sectors: 2,297,888
I 04:51:22 Write Mode: DVD
I 04:51:22 Write Type: DAO
I 04:51:22 Write Speed: 2x
I 04:51:22 Link Size: Auto
I 04:51:22 Test Mode: No
I 04:51:22 OPC: No
I 04:51:22 BURN-Proof: Enabled
I 04:51:22 Filling Buffer... (40 MB)
I 04:51:23 Writing LeadIn...
I 04:52:07 Writing Session 1 of 1... (1 Track, LBA: 0 - 2296623)
I 04:52:07 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2296623)
I 05:20:20 Synchronising Cache...
I 05:20:57 Exporting Graph Data...
I 05:20:57 Graph Data File: C:\Documents and Settings\Dell\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GSA-H42N_RL01_WEDNESDAY-MAY-21-2008_4-51_AM_PRINCO_2x.ibg
I 05:20:57 Export Successfully Completed!
I 05:20:57 Operation Successfully Completed! - Duration: 00:29:35
I 05:20:57 Average Write Rate: 2,714 KB/s (2.0x) - Maximum Write Rate: 2,809 KB/s (2.0x)
I 05:20:57 Cycling Tray before Verify...
W 05:21:05 Waiting for device to become ready...
I 05:21:22 Device Ready!
I 05:21:33 Operation Started!
I 05:21:33 Source Device: [1:0:0] HL-DT-ST DVDRAM GSA-H42N RL01 (G (ATA)
I 05:21:33 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: PRINCO) (Speeds: 2x)
I 05:21:33 Image File: -==/\/[BUILD IMAGE]\/\==-
I 05:21:33 Image File Sectors: 2,296,624 (MODE1/2048)
I 05:21:33 Image File Size: 4,703,485,952 bytes
I 05:21:33 Image File Volume Identifier: JohnsBirthday
I 05:21:33 Image File Application Identifier: IMGBURN V2.4.1.0 - THE ULTIMATE IMAGE BURNER!
I 05:21:33 Image File Implementation Identifier: ImgBurn
I 05:21:33 Image File File System(s): ISO9660, UDF (1.02)
I 05:21:33 Read Speed (Data/Audio): MAX / MAX
I 05:21:33 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2296623)
I 05:21:33 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2296623)
W 06:08:23 Failed to Read Sector 2182192 - Reason: Unrecovered Read Error
W 06:08:23 Sector 2182192 maps to File: \VIDEO_TS\VTS_02_5.VOB
E 06:11:04 Failed to Read Sector 2184624 - Reason: Unrecovered Read Error
E 06:11:04 Sector 2184624 maps to File: \VIDEO_TS\VTS_02_5.VOB
E 06:11:04 Failed to Verify Sectors!
I 06:11:05 Exporting Graph Data...
I 06:11:05 Graph Data File: C:\Documents and Settings\Dell\Application Data\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GSA-H42N_RL01_WEDNESDAY-MAY-21-2008_4-51_AM_PRINCO_2x.ibg
I 06:11:05 Export Successfully Completed!
E 06:11:05 Operation Failed! - Duration: 00:49:31
I 06:11:05 Average Verify Rate: 1,471 KB/s (1.1x) - Maximum Verify Rate: 3,360 KB/s (2.4x)
I 06:22:53 Close Request Acknowledged
I 06:22:53 Closing Down...
I 06:22:54 Shutting down SPTI...
I 06:22:54 ImgBurn closed!

[VegasBud]

alegator,

The drive identifies the media as "PRINCO", which is very, very likely to be the source of the problem. Quality variation, even in the same batch, is one of the characteristics of lower quality media. Click here to go to the "Blank Media Quality Guide" at nomorecoasters.com. You can use that page to help you determine what would be better media to use.

The reason you were having the problem at about 90% is the outer 10% of a disk is the least reliable, so that's frequently the area where borderline media turns into coasters.

A side benefit to getting better quality media would be that you will be able to use that 18x burner you have to burn waaaaay faster than the 2x you're getting with the princos.

[alegator]

alegator,

The drive identifies the media as "PRINCO", which is very, very likely to be the source of the problem. Quality variation, even in the same batch, is one of the characteristics of lower quality media. Click here to go to the "Blank Media Quality Guide" at nomorecoasters.com. You can use that page to help you determine what would be better media to use.

The reason you were having the problem at about 90% is the outer 10% of a disk is the least reliable, so that's frequently the area where borderline media turns into coasters.

A side benefit to getting better quality media would be that you will be able to use that 18x burner you have to burn waaaaay faster than the 2x you're getting with the princos.

VegasBud, I bought a cake of 100 Princo's like 4 years ago, that's why they burn only at 2X. From those 100, I burned 80 approx. and never had a single coaster, plus they are 100% compatible with many standalone DVD players I tried (Sony, Philips, etc). Yesterday was the first time I encountered this burning error from two of the 20 left in the cake. I agree with you that it pays off to buy Verbatim always, they are the best, but I really doubt that in this case the issue is media related for the reasons stated above. I could try burning other brands (I have Verbatim and another generic brand too) but I'm afraid wasting DVD's along the way, I'd rather identify the reason for this happening before trying burning more DVD's. What about burning in "Test" mode? I the Test mode ends successfully, will that guarantee that the actual burn will also be successfull?

[budz]

your problem is PRINCO media as already mentioned. the problem has already been identified.....try playing back those PRINCO media in a few months, in a year or so and you'll see the that the files will not be able to be read back correctly. use VERBATIM end of story....just my 2 cents!

[MOVIEGEEK]

This is the second post(this week) I've read about problems using verify on Imgburn,IMO it is worthless.As your log states the burn was successfull so don't worry about it.Princo is crap but as long as it plays it's ok(for the time being),as others have said use better media.
https://forum.videohelp.com/topic351188.html

[VegasBud]

alegator,

A test mode burn is most useful to show the overall system setup and communication between the components prior to, and during, a (simulated) burn. That information was already provided in the actual burn log you posted, so a test mode burn wouldn't provide any additional details.

The log you posted shows the drive reported no errors during the burn. As far as the drive is concerned, it did its' job. It was only when the drive attempted to read the burned disk that the error occurred, and the error reported only concerned the interaction of the media and the drive. Specifically, the drive reported that it was unable to access the contents of selected sectors on the disk starting at just past 95% of disk capacity, which is well into the "make it or break it" area of a disk.

Since it was the drive that reported a read error, only the drive or the media could be to blame. Of the two, a change of media is the easiest and cheapest to test. If known good quality media (like Verbatim) also fails, then the drive is the only suspect left.

I doubt it's the drive. The pattern doesn't fit for drive failure, but is classic for media errors.

[VegasBud]

For the record, in this case there can be no doubt the error was caused by a hardware failure to read multiple sectors on a disk. It has absolutely nothing to do with a byte comparison performed by the verification function of a piece of software.

[alegator]

Well, I just tested another generic brand, "ProdiscS03" and I burned the DVD5 at 4X successfully onto it with Nero (all burning stages reported no errors, including the verification). So apparently you were correct, the problem was Princo. I was hesitant just because as I mentioned I burned 80 discs from the same cake successfully, but apparently these two failed. I am aware that most generic brands are not worth buying, that Verbatim is the way to go, but I was just trying to make sure this issue was not hardware related.

.....try playing back those PRINCO media in a few months, in a year or so and you'll see the that the files will not be able to be read back correctly...!

If a PRINCO or for that matter any DVD burns correctly, with no errors whatsoever, what makes them unreadable "in a year or so" as you claim? Of course I would understand if we are talking about 100 years which is the lifetime of a DVD...

For the record, in this case there can be no doubt the error was caused by a hardware failure to read multiple sectors on a disk. It has absolutely nothing to do with a byte comparison performed by the verification function of a piece of software.

VegasBud, I'm confused by your statement. I must conclude that my problem was media related (Princo) and NOT hardware related (the DVD burner). Are you supporting this too? Thanks.

[budz]

If a PRINCO or for that matter any DVD burns correctly, with no errors whatsoever, what makes them unreadable "in a year or so" as you claim? Of course I would understand if we are talking about 100 years which is the lifetime of a DVD...

Because PRINCO uses cheap dye for their discs and over a period of time they supposedly deteriorate. I explained this to one of my cousins a few years ago since she was buying cheap COMPUSA dvd discs which were PRINCO. A few months later she tells me the discs can't playback correctly and she couldn't rip the files off the disc.

[VegasBud]

alegator,

I'm sorry if that was confusing. The error occurred when the drive (hardware) was unable (failed) to access the contents of selected sectors on the disk. As you've now demonstrated, the drive's failure to access the sectors wasn't the drive's fault at all, but the media that was responsible. Nevertheless, the error reported was that the hardware (the drive) failed to complete a task it had been assigned, hence the "hardware failure to read multiple sectors on a disk" phrase. It just demonstrates that identifying burn problems has less to do with the errors reported than an understanding of why the error occurred in the first place.

If that confuses you even more, let me know and I'll try again.

[alegator]

[quote="budz"]

Because PRINCO uses cheap dye for their discs and over a period of time they supposedly deteriorate. I explained this to one of my cousins a few years ago since she was buying cheap COMPUSA dvd discs which were PRINCO. A few months later she tells me the discs can't playback correctly and she couldn't rip the files off the disc.

Budz, yes I thought that cheap DVD's use cheap materials and therefore degrade faster over time. I guess it also helps if you handle them carefully and you store them the right way. In my case I have these Princo's for 4 years already and all the videos/files I burned on them are readable/playable. However it's good to know that Princo is junk, so I might be better off cloning them onto Verbatim media (at least the essential ones). Regards.

alegator,

I'm sorry if that was confusing. The error occurred when the drive (hardware) was unable (failed) to access the contents of selected sectors on the disk. As you've now demonstrated, the drive's failure to access the sectors wasn't the drive's fault at all, but the media that was responsible. Nevertheless, the error reported was that the hardware (the drive) failed to complete a task it had been assigned, hence the "hardware failure to read multiple sectors on a disk" phrase. It just demonstrates that identifying burn problems has less to do with the errors reported than an understanding of why the error occurred in the first place.

If that confuses you even more, let me know and I'll try again.

Very clear now VegasBud! Thanks and regards.