Jump to content

Burn &verify


John_m

Recommended Posts

Hi all.

 

This is my first post to this forum although I've been using imgburn for a while now (a year or so) and it's great.

 

Now, the reason for my posting. When I do a burn and verify in one step, the burn completes ok but the verify fails just as often as it succeeds. However, if I eject the disk, reinsert into the same drive and do the verify again against the same image I get no problems: it verifies clean.

 

Interesting no?

 

I'm running on Vista x64 SP1, C2D 8500, 6GB corsair RAM (no oc), 600GB RAID 0 HDD on Intel ICH9R. My burner is a Pioneer 215BK (upgrading the firmware to 1.22 made no difference). I'm using Verbatim 16x media but it doesn't seem to matter at what speed I burn at the symptoms persist (even at 1x burn). I even leave my machine completely alone after I click the big "burn now" button but that makes no difference either.

 

So, to recap: burn and verify cycle I get mixed results on the verify (fails roughly 50% of the time). But if I burn and then verify separately, I get perfect verifications. This persists no matter what speed I burn at.

 

Ideas anyone?

 

Cheers

John

Edited by John_m
Link to comment
Share on other sites

What sort of failures are you actually getting?

 

I'm getting miscompares.

 

Sample log from today:

 

I 19:15:36 Operation Started!

I 19:15:36 Source File: C:\Users\John\Documents\DVD\TOY_STORY_2.ISO

I 19:15:36 Source File Sectors: 2,285,843 (MODE1/2048)

I 19:15:36 Source File Size: 4,681,406,464 bytes

I 19:15:36 Source File Volume Identifier: TOY_STORY_2

I 19:15:36 Source File Volume Set Identifier: 00E5A0C5DVDSHRNK

I 19:15:36 Source File Implementation Identifier: DVD Shrink

I 19:15:36 Source File File System(s): ISO9660, UDF (1.02)

I 19:15:36 Destination Device: [0:1:0] PIONEER DVD-RW DVR-215 1.22 (E:) (ATAPI)

I 19:15:36 Destination Media Type: DVD+R (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x, 20x)

I 19:15:36 Destination Media Sectors: 2,295,104

I 19:15:36 Write Mode: DVD

I 19:15:36 Write Type: DAO

I 19:15:36 Write Speed: 4x

I 19:15:36 DVD+R Reserve Track: No

I 19:15:36 Link Size: Auto

I 19:15:36 Test Mode: No

I 19:15:36 OPC: No

I 19:15:36 BURN-Proof: Enabled

I 19:15:36 Filling Buffer... (40 MB)

I 19:15:37 Writing LeadIn...

I 19:15:53 Writing Session 1 of 1... (1 Track, LBA: 0 - 2285842)

I 19:15:53 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2285842)

I 19:30:07 Synchronising Cache...

I 19:30:08 Closing Track...

I 19:30:10 Finalising Disc...

I 19:30:36 Exporting Graph Data...

I 19:30:36 Graph Data File: C:\Users\John\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-215_1.22_MONDAY-29-DECEMBER-2008_7-15_PM_MCC-004-00_4x.ibg

I 19:30:36 Export Successfully Completed!

I 19:30:36 Operation Successfully Completed! - Duration: 00:14:59

I 19:30:36 Average Write Rate: 5,359 KB/s (3.9x) - Maximum Write Rate: 5,576 KB/s (4.0x)

I 19:30:36 Cycling Tray before Verify...

I 19:30:57 Device Ready!

I 19:30:57 Operation Started!

I 19:30:57 Source Device: [0:1:0] PIONEER DVD-RW DVR-215 1.22 (E:) (ATAPI)

I 19:30:57 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x, 20x)

I 19:30:57 Image File: C:\Users\John\Documents\DVD\TOY_STORY_2.ISO

I 19:30:57 Image File Sectors: 2,285,843 (MODE1/2048)

I 19:30:57 Image File Size: 4,681,406,464 bytes

I 19:30:57 Image File Volume Identifier: TOY_STORY_2

I 19:30:57 Image File Volume Set Identifier: 00E5A0C5DVDSHRNK

I 19:30:57 Image File Implementation Identifier: DVD Shrink

I 19:30:57 Image File File System(s): ISO9660, UDF (1.02)

I 19:30:57 Read Speed (Data/Audio): MAX / MAX

I 19:30:57 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2285842)

I 19:30:57 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2285842)

E 19:31:47 Miscompare at LBA: 93539, Offset: 1094, File: \VIDEO_TS\VTS_01_1.VOB

E 19:31:47 Device: 0xD1

E 19:31:47 Image File: 0xF1

E 19:31:47 Total Errors in Sector: 1

E 19:31:47 Failed to Verify Sectors!

I 19:31:50 Exporting Graph Data...

I 19:31:50 Graph Data File: C:\Users\John\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-215_1.22_MONDAY-29-DECEMBER-2008_7-15_PM_MCC-004-00_4x.ibg

I 19:31:50 Export Successfully Completed!

E 19:31:50 Operation Failed! - Duration: 00:00:50

I 19:31:50 Average Verify Rate: 3,741 KB/s (2.7x) - Maximum Verify Rate: 10,032 KB/s (7.2x)

I 19:32:19 Operation Started!

I 19:32:19 Source Device: [0:1:0] PIONEER DVD-RW DVR-215 1.22 (E:) (ATAPI)

I 19:32:19 Source Media Type: DVD+R (Book Type: DVD+R) (Disc ID: MCC-004-00) (Speeds: 4x, 6x, 8x, 12x, 16x, 20x)

I 19:32:19 Image File: C:\Users\John\Documents\DVD\TOY_STORY_2.ISO

I 19:32:19 Image File Sectors: 2,285,843 (MODE1/2048)

I 19:32:19 Image File Size: 4,681,406,464 bytes

I 19:32:19 Image File Volume Identifier: TOY_STORY_2

I 19:32:19 Image File Volume Set Identifier: 00E5A0C5DVDSHRNK

I 19:32:19 Image File Implementation Identifier: DVD Shrink

I 19:32:19 Image File File System(s): ISO9660, UDF (1.02)

I 19:32:19 Read Speed (Data/Audio): MAX / MAX

I 19:32:19 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2285842)

I 19:32:19 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2285842)

I 19:37:22 Exporting Graph Data...

I 19:37:22 Graph Data File: C:\Users\John\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_DVD-RW_DVR-215_1.22_MONDAY-29-DECEMBER-2008_7-32_PM_MCC-004-00.ibg

I 19:37:22 Export Successfully Completed!

I 19:37:22 Operation Successfully Completed! - Duration: 00:05:03

I 19:37:22 Average Verify Rate: 15,088 KB/s (10.9x) - Maximum Verify Rate: 22,201 KB/s (16.0x)

 

As you can see I got a miscompare in the verify as part of the burn, but no miscopmpare when I verify as a separate operation.

 

Cheers

JohnM

Link to comment
Share on other sites

Do you have the latest chipset and controller drivers installed for your motherboard (i.e. Intel or nvidia) ?

 

Have you tried running memtest for a couple of hours?

 

Have you tried looking at that specific sector on the disc / within the image file to see which of those two values is actually the correct one? (i.e. 0xD1 or 0xF1)

Link to comment
Share on other sites

I have an ASUS P5K-E mobo (BIOS revision 1202) which includes the Intel P35 chipset. I have the latest chipset drivers (9.1.0.1007 WHQL) and "fakeraid" drivers (8.6.0.1007 WHQL). I tried the newer chipset drivers 9.1.0.1012 WHQL from station-drivers . com but with no change.

 

memtest86+ v2.11 gives my memory a clean bill of health. I ran it from it's boot CD and let it do it's thing for a couple of hours after which it declared that everything was cool.

 

I have tried looking at the specific sector, but I am unsure that I'm doing it right. I used a program called "Hex Editor Neo" to open the VIDEO_TS\VTS_01_1.VOB file on my HDD and then jumped to the specified offset 1094 (decimal, I presume?). However, the data at that offset is zero (00)! I assume that it's an absolute offset and not relative of something? What am I doing wrong?

 

Suffice it to say: I'm confused.

 

Cheers

John

Link to comment
Share on other sites

Ah now that's a very good point, it's at byte offset 1094 within that sectors but it doesn't show the relative sector number within the file!

 

As such you have to work it out based on the start LBA of that file. i.e. ((93539 - start of file LBA) * 2048) + 1094 = total offset within file.

 

It's easier to just open the iso / disc in IsoBuster and view that sector. You can also use ImgBurn but the ISO would need to be mounted in a virtual drive because ImgBurn can only display sectors on a drive.

Link to comment
Share on other sites

Hi again. I can't seem to work out this sector thing.

 

It's easier to just open the iso / disc in IsoBuster and view that sector. You can also use ImgBurn but the ISO would need to be mounted in a virtual drive because ImgBurn can only display sectors on a drive.

 

I just d/l isobuster, but I've never used it. How do I view the specific sector within isobuster?

 

Sorry that I'm being a bit dense ;-)

Cheers and happy new year!

John

Link to comment
Share on other sites

Ok, I think I've got it sorted. The value on both the iso file and on the dvd is 0xf1, which is the 2nd of the two values shown in the log.

 

Just to confirm that I'm doing things right here is how I got the value: I put 93539 into the sector view and then counted forward 1094 (0x446) bytes into that sector. The resulting position contained the magic 0xf1.

 

I suppose the question is where did the 0xd1 come from?

 

By the way, it may be just my imagination but...the verify miscompares (as part of the burn) problem seems to go away if I restart imgburn between one burn to the next...

 

Cheers

John

Link to comment
Share on other sites

i have a similar problem on one pc but it appears rarely that i didn't cared about, i didn't figured where the problem is since it appears rarely;

hardware setup it's so different that i dont' know it has a sense of report it. it's an ati rs600 chipset on mobo, 2gb ram , Xp32sp3 not english and a Liteon lh20A1S burner; the installation is very clean because of the usage type and imgburn it's the only cd/dvd relating software installed (so there are no minifilters neither driver of various kind, only imgburn is present); memory check didn't found nothing, creating and cheching very large archives doesn't show errors.

 

The firt time it happened i did a hex compare and found one single different bit, it was an archive, so archive test failed on the dvd file; later it happened more times and i just trashed the dvd end repeat the burn; i also confirm that one time i didn't quit imgburn and a burning again make the verify failed again; unfortunately i didn't took any log;

also i did first a pi/po scan, since i write at 4x or 6x i got a score 99 with cspdeed+liteon that is an excellent result even on the failed media so it's not a media trouble; i also have ready a new pioneer 216 ready for swap

 

the only different thing it's that the hdd is encrypted but it doesn't seem to be the problem, also i never experienced corruptions on the archives that i created (and they're big).

 

i updated the firmware but the error happened again today and i got here, so i just read this thread and found that a later compare was succesful, i compared the failed file, then all the files and there are no error.

 

i'm on vnc so later at home i'll see if i can catch same of the old failed media and check them; it's easy because they only contains big rars with RR and i have to check for their integrity with the same pc or another one.

 

Still have imgburn running on the desktop after the failed verify and for now i'll leave it as is , do you need any help or same checks?

i'll check the thread in two hours and to write a new media to see if it fail again and if at the same point; do you need any help to get more infos?

 

if not i'll just swap the drive and live with the problem if it happen again, it's a minor problem and if it happen to fail only the verify (i hope to provide same info later) then it's not even a problem to me.

bye for now.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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