aguilacuervo Posted February 24, 2010 Posted February 24, 2010 (edited) Hi, Why would Verify fail with ImgBurn after burning some iso files I did with ImgBurn a while back? This starts happening on and on: I 21:36:53 Verifying Session 1 of 1... (1 Track, LBA: 0 - 1875068) I 21:36:53 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 1875068) W 21:45:37 Miscompare at LBA: 116126, Offset: 384, File: \VIDEO_TS\VTS_01_0.VOB W 21:45:37 Device: 0xAB W 21:45:37 Image File: 0x5B W 21:45:37 Total Errors in Sector: 1.645 I 21:45:37 Verifying Sectors... W 21:45:38 Miscompare at LBA: 116127, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 21:45:38 Device: 0xB6 W 21:45:38 Image File: 0x00 W 21:45:38 Total Errors in Sector: 2.026 I 21:45:38 Verifying Sectors... W 21:46:09 Miscompare at LBA: 184978, Offset: 184, File: \VIDEO_TS\VTS_04_1.VOB W 21:46:09 Device: 0x04 W 21:46:09 Image File: 0xB1 W 21:46:09 Total Errors in Sector: 1.856 I 21:46:09 Verifying Sectors... W 21:46:10 Miscompare at LBA: 184979, Offset: 0, File: \VIDEO_TS\VTS_04_1.VOB W 21:46:10 Device: 0xE6 W 21:46:10 Image File: 0x00 W 21:46:10 Total Errors in Sector: 2.035 Then the burned DVD works just fine as far as I can tell, but Verify just goes wild like this. Why? Edited February 24, 2010 by aguilacuervo
LIGHTNING UK! Posted February 24, 2010 Posted February 24, 2010 Drive not reading the disc correctly I'd guess. What media did you burn to? Can you verify from a different drive? If you verify from the same drive again, does it pick up the exact same number of errors in the exact same sectors?
aguilacuervo Posted February 25, 2010 Author Posted February 25, 2010 Yes, I tried verifying it from a different drive and it worked just fine. Thanks. Why would my other drive not read OK? Is it getting old or something?
aguilacuervo Posted February 25, 2010 Author Posted February 25, 2010 (edited) I've just realized it's not the drives. What's causing the problem is having Verify Against Image File on. And the number of errors and which sectors they turn up in remains the same from drive to drive and verify to verify (on the same drive). What does this mean? What is it for drive? Sorry, Cynthia. I don't understand the question. Thanks to both of you! Edited February 25, 2010 by aguilacuervo
LIGHTNING UK! Posted February 25, 2010 Posted February 25, 2010 Either that your image is now corrupt or your disc is. Do you have an SFV or PAR/PAR2 type file to check the ISO is still ok?
aguilacuervo Posted February 25, 2010 Author Posted February 25, 2010 I don't have any of that, but I'm not sure that's the problem. Because: 1) This is happening every time more often now, even with iso files I just created. They can't be all corrupt I think. 2) On top of that, nothing seems to be wrong with the discs when I play them. I haven't played them all though, and with some I just did a quick browsing to check. 3) Also, regular verify works just fine on every single one of them. I'm worried because I can't foolproof-test them all inch by inch, and I can't store the images forever either. So all I'm left with is the perspective of maybe finding out too late that something's wrong, etc. Thank you very much!
mmalves Posted February 26, 2010 Posted February 26, 2010 The full log of that burn session would be helpful.
LIGHTNING UK! Posted February 26, 2010 Posted February 26, 2010 What's a 'regular' verify?! One where you don't compare it to an image file? How would it find 'miscompare' errors if you don't 'compare' it to anything in the first place... think about it
aguilacuervo Posted March 10, 2010 Author Posted March 10, 2010 I don't really know what Verify actually is, so I imagined some sort of test sequence took place apart from the comparing. Why is it an option to verify without comparing then? Anyway, the full log is just what you see up there on and on... At some point I just hit Ignore Miscompares or cancel the whole thing. Nothing much to see there I think. So, next time this happens I'll see how some of this stuff helps. Thanks.
aguilacuervo Posted March 11, 2010 Author Posted March 11, 2010 Ok, maybe nobody cares... I kept a copy of one image I had this problem with. I played the DVD while on vacations and it worked just fine. And now I know what these .md5 files are for, so I run the checksum and everything's marvels with the .iso file as well. So, I'm thinking the file is not corrupt, the DVD plays just fine, and still miscompares were reported. Here's the full log: I 18:53:14 ImgBurn Version 2.5.0.0 started! I 18:53:14 Microsoft Windows Vista Ultimate Edition (6.0, Build 6002 : Service Pack 2) I 18:53:14 Total Physical Memory: 1.964.692 KB - Available: 762.232 KB I 18:53:14 Initialising SPTI... I 18:53:14 Searching for SCSI / ATAPI devices... I 18:53:14 Found 1 DVD-ROM and 1 DVD±RW! I 18:54:01 Operation Started! I 18:54:01 Source File: D:\ImgBurn\Image Files\Y_LA_NAVE_VA.ISO I 18:54:01 Source File Sectors: 2.264.352 (MODE1/2048) I 18:54:01 Source File Size: 4.637.392.896 bytes I 18:54:01 Source File Volume Identifier: Y_LA_NAVE_VA I 18:54:01 Source File Volume Set Identifier: 3121AC0FCEDE53F0 I 18:54:02 Source File Application Identifier: NERO BURNING ROM I 18:54:02 Source File Implementation Identifier: AHEAD Nero I 18:54:02 Source File File System(s): ISO9660, UDF (1.02) I 18:54:02 Destination Device: [2:0:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 18:54:02 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 4x, 6x, 8x, 12x, 16x) I 18:54:02 Destination Media Sectors: 2.297.888 I 18:54:02 Write Mode: DVD I 18:54:02 Write Type: Incremental I 18:54:02 Write Speed: 8x I 18:54:02 Link Size: Auto I 18:54:02 Lock Volume: Yes I 18:54:02 Test Mode: No I 18:54:02 OPC: Yes I 18:54:02 BURN-Proof: Enabled I 18:54:03 Advanced Settings - Optimal Writing Speed: No I 18:54:22 Filling Buffer... (40 MB) I 18:54:22 Writing LeadIn... I 18:54:24 Writing Session 1 of 1... (1 Track, LBA: 0 - 2264351) I 18:54:24 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 2264351) I 19:01:58 Synchronising Cache... I 19:01:59 Closing Track... I 19:02:00 Closing Session... I 19:02:39 Image MD5: 1e3936b646235b89d77ddd054555c8dd I 19:02:39 Exporting Graph Data... I 19:02:39 Graph Data File: D:\ImgBurn\Graph Data Files\2010-02-24_18-54_PIONEER_DVD-RW_DVR-111D_1.29_MCC_03RG20_Y_LA_NAVE_VA_8x.ibg I 19:02:39 Export Successfully Completed! I 19:02:39 Operation Successfully Completed! - Duration: 00:08:37 I 19:02:39 Average Write Rate: 9.997 KB/s (7.2x) - Maximum Write Rate: 11.233 KB/s (8.1x) I 19:02:39 Cycling Tray before Verify... I 19:03:00 Device Ready! I 19:03:00 Operation Started! I 19:03:00 Source Device: [2:0:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 19:03:00 Source Media Type: DVD-R (Book Type: DVD-R) (Disc ID: MCC 03RG20) (Speeds: 4x, 6x, 8x, 12x, 16x) I 19:03:00 Image File: D:\ImgBurn\Image Files\Y_LA_NAVE_VA.ISO I 19:03:00 Image File Sectors: 2.264.352 (MODE1/2048) I 19:03:00 Image File Size: 4.637.392.896 bytes I 19:03:00 Image File Volume Identifier: Y_LA_NAVE_VA I 19:03:00 Image File Volume Set Identifier: 3121AC0FCEDE53F0 I 19:03:00 Image File Application Identifier: NERO BURNING ROM I 19:03:01 Image File Implementation Identifier: AHEAD Nero I 19:03:01 Image File File System(s): ISO9660, UDF (1.02) I 19:03:01 Read Speed (Data/Audio): MAX / MAX I 19:03:01 Hardware Read Error Retries: 2 I 19:03:01 Verifying Session 1 of 1... (1 Track, LBA: 0 - 2264351) I 19:03:01 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 2264351) W 21:04:51 Miscompare at LBA: 946429, Offset: 1272, File: \VIDEO_TS\VTS_01_2.VOB W 21:04:51 Device: 0x3B W 21:04:51 Image File: 0x71 W 21:04:51 Total Errors in Sector: 771 I 21:04:51 Verifying Sectors... W 21:04:55 Miscompare at LBA: 946430, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 21:04:55 Device: 0x00 W 21:04:55 Image File: 0x04 W 21:04:55 Total Errors in Sector: 2.036 I 21:04:55 Verifying Sectors... W 21:04:59 Miscompare at LBA: 946431, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 21:04:59 Device: 0x00 W 21:04:59 Image File: 0x95 W 21:04:59 Total Errors in Sector: 2.034 I 21:04:59 Verifying Sectors... W 21:08:12 Miscompare at LBA: 2260319, Offset: 168, File: \VIDEO_TS\VTS_01_5.VOB W 21:08:12 Device: 0xC2 W 21:08:12 Image File: 0xC0 W 21:08:12 Total Errors in Sector: 1.859 I 21:08:12 Verifying Sectors... I 21:08:12 Device MD5: 1e3936b646235b89d77ddd054555c8dd I 21:08:12 Image MD5: 245e6139583776977bba3c5d07f371a5 W 21:08:12 Miscompare between Device and Image MD5 hash values! I 21:08:22 Exporting Graph Data... I 21:08:22 Graph Data File: D:\ImgBurn\Graph Data Files\2010-02-24_18-54_PIONEER_DVD-RW_DVR-111D_1.29_MCC_03RG20_Y_LA_NAVE_VA_8x.ibg I 21:08:22 Export Successfully Completed! I 21:08:22 Operation Successfully Completed! - Duration: 02:05:17 I 21:08:22 Average Verify Rate: 602 KB/s (0.4x) - Maximum Verify Rate: 17.242 KB/s (12.4x) I 21:08:25 Close Request Acknowledged I 21:08:25 Closing Down... I 21:08:25 Shutting down SPTI... I 21:08:25 ImgBurn closed! That's it... I'm officially calling this a bug report! Am I wrong? Thanks!!
LIGHTNING UK! Posted March 11, 2010 Posted March 11, 2010 Put the hardware read error retries back on the default value, you shouldn't be messing with that. In fact, put all the settings back on their default values. No, it's not a bug report because it would be happening for everyone - and it's not. I had to do a run of 150 discs the other week and didn't have a single failure.
aguilacuervo Posted March 11, 2010 Author Posted March 11, 2010 I spent a whole afternoon a while ago reading guides and configuring my settings and the bugger ended up working a lot better than it used to, so I'm not gonna set everything back to default. Sorry. I just thought more is better with retries, I guess I was wrong there. I will correct that. Thank you. I love this program, that's why I get so annoying about it. Thanks for everything, man!!
aguilacuervo Posted March 16, 2010 Author Posted March 16, 2010 To everyone's annoyance I'm prepared to further my inquiry into this matter! I don't know what's happening here. I'd just like to know if I'm doing something wrong. That's all. I'm not deliberately trying to piss anyone off. So, same picture: guy (me) burns DVD (dual layer this time) and everything seems OK, but gets a bunch of miscompares and ends up wondering what's up. This time the case is even more solid. 1) MD5 on image is a match. 2) All retries are set to default. 3) I do two consecutive verifies on different drives and miscompares don't match. 4) What's even more weird: MD5 hash check on both drives for Device is a match, but for Image isn't. That's like totally weird, right? (Compare between verifies) Here's the log of the whole session: ; //****************************************\\ ; ImgBurn Version 2.5.0.0 - Log ; Monday, 15 March 2010, 23:28:50 ; \\****************************************// ; ; I 21:04:43 ImgBurn Version 2.5.0.0 started! I 21:04:43 Microsoft Windows Vista Ultimate Edition (6.0, Build 6002 : Service Pack 2) I 21:04:43 Total Physical Memory: 1.964.692 KB - Available: 986.144 KB I 21:04:43 Initialising SPTI... I 21:04:43 Searching for SCSI / ATAPI devices... I 21:04:43 Found 1 DVD-ROM and 1 DVD±RW! I 21:05:29 Operation Started! I 21:05:29 Source File: D:\Video\Image Files\MOON.MDS I 21:05:29 Source File Sectors: 3.894.659 (MODE1/2048) I 21:05:29 Source File Size: 7.976.261.632 bytes I 21:05:29 Source File Volume Identifier: MOON I 21:05:29 Source File Volume Set Identifier: 3b480d42 I 21:05:29 Source File Implementation Identifier: Sonic Scenarist 3.1 I 21:05:29 Source File File System(s): ISO9660, UDF (1.02) I 21:05:29 Destination Device: [2:0:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 21:05:29 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) (Speeds: 2,4x, 4x, 6x, 8x) I 21:05:29 Destination Media Sectors: 4.173.824 I 21:05:29 Write Mode: DVD I 21:05:29 Write Type: Incremental I 21:05:29 Write Speed: 2,4x I 21:05:29 Link Size: Auto I 21:05:29 Lock Volume: Yes I 21:05:29 Test Mode: No I 21:05:29 OPC: Yes I 21:05:29 BURN-Proof: Enabled I 21:05:29 Advanced Settings - Optimal Writing Speed: No I 21:06:06 Optimal L0 Data Zone Capacity: 1.952.432 I 21:06:06 Optimal L0 Data Zone Method: Copied From Original Disc I 21:06:07 Set L0 Data Zone Capacity Succeeded! I 21:06:07 Filling Buffer... (40 MB) I 21:06:09 Writing LeadIn... I 21:06:10 Writing Session 1 of 1... (1 Track, LBA: 0 - 3894658) I 21:06:10 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3894658) I 21:06:10 Writing Layer 0... (LBA: 0 - 1952431) I 21:26:33 Writing Layer 1... (LBA: 1952432 - 3894658) I 21:46:43 Synchronising Cache... I 21:46:44 Closing Track... I 21:46:46 Finalising Disc... I 21:47:52 Image MD5: 846f435d2080d9b475e4411d1fe62644 I 21:47:52 Exporting Graph Data... I 21:47:52 Graph Data File: D:\Computadora\Log Data\ImgBurn\Graph Data Files\2010-03-15_21-05_PIONEER_DVD-RW_DVR-111D_1.29_MKM-001-00_MOON_2,4x.ibg I 21:47:52 Export Successfully Completed! I 21:47:52 Operation Successfully Completed! - Duration: 00:42:22 I 21:47:52 Average Write Rate: 3.202 KB/s (2.3x) - Maximum Write Rate: 3.370 KB/s (2.4x) I 21:47:52 Cycling Tray before Verify... I 21:48:21 Device Ready! I 21:48:21 Operation Started! I 21:48:21 Source Device: [2:0:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 21:48:22 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x, 4x, 6x, 8x) I 21:48:22 Image File: D:\Video\Image Files\MOON.MDS I 21:48:22 Image File Sectors: 3.894.659 (MODE1/2048) I 21:48:22 Image File Size: 7.976.261.632 bytes I 21:48:22 Image File Volume Identifier: MOON I 21:48:22 Image File Volume Set Identifier: 3b480d42 I 21:48:22 Image File Implementation Identifier: Sonic Scenarist 3.1 I 21:48:22 Image File File System(s): ISO9660, UDF (1.02) I 21:48:22 Read Speed (Data/Audio): MAX / MAX I 21:48:22 Hardware Read Error Retries: 2 I 21:48:22 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3894658) I 21:48:22 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3894658) I 21:48:22 Verifying Layer 0... (LBA: 0 - 1952431) W 22:44:54 Miscompare at LBA: 173308, Offset: 1176, File: \VIDEO_TS\VTS_01_0.VOB W 22:44:54 Device: 0x16 W 22:44:54 Image File: 0xDF W 22:44:54 Total Errors in Sector: 865 I 22:44:54 Verifying Sectors... W 22:44:56 Miscompare at LBA: 173309, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 22:44:56 Device: 0x00 W 22:44:56 Image File: 0x2C W 22:44:56 Total Errors in Sector: 2.026 I 22:44:56 Verifying Sectors... W 22:44:56 Miscompare at LBA: 173310, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 22:44:56 Device: 0x00 W 22:44:57 Image File: 0xBD W 22:44:57 Total Errors in Sector: 2.028 I 22:44:57 Verifying Sectors... W 22:44:57 Miscompare at LBA: 173311, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 22:44:57 Device: 0x00 W 22:44:57 Image File: 0x4D W 22:44:57 Total Errors in Sector: 2.031 I 22:44:57 Verifying Sectors... W 22:49:33 Miscompare at LBA: 1012637, Offset: 16, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:33 Device: 0x01 W 22:49:33 Image File: 0xCA W 22:49:33 Total Errors in Sector: 2.019 I 22:49:36 Verifying Sectors... W 22:49:36 Miscompare at LBA: 1012638, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:36 Device: 0x00 W 22:49:36 Image File: 0x94 W 22:49:36 Total Errors in Sector: 2.038 I 22:49:37 Verifying Sectors... W 22:49:37 Miscompare at LBA: 1012639, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:37 Device: 0x00 W 22:49:37 Image File: 0x25 W 22:49:37 Total Errors in Sector: 2.037 I 22:49:37 Verifying Sectors... W 22:49:38 Miscompare at LBA: 1012659, Offset: 232, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:38 Device: 0x73 W 22:49:38 Image File: 0xBF W 22:49:38 Total Errors in Sector: 1.812 I 22:49:38 Verifying Sectors... W 22:49:38 Miscompare at LBA: 1012660, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:38 Device: 0x00 W 22:49:38 Image File: 0x6B W 22:49:38 Total Errors in Sector: 2.039 I 22:49:38 Verifying Sectors... W 22:49:39 Miscompare at LBA: 1012661, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:39 Device: 0x00 W 22:49:39 Image File: 0x6B W 22:49:39 Total Errors in Sector: 2.040 I 22:49:40 Verifying Sectors... W 22:49:42 Miscompare at LBA: 1012662, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:42 Device: 0x00 W 22:49:42 Image File: 0x6B W 22:49:42 Total Errors in Sector: 2.043 I 22:49:42 Verifying Sectors... W 22:49:43 Miscompare at LBA: 1012663, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:43 Device: 0x00 W 22:49:43 Image File: 0x6B W 22:49:43 Total Errors in Sector: 2.041 I 22:49:43 Verifying Sectors... W 22:49:44 Miscompare at LBA: 1012664, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:44 Device: 0x00 W 22:49:44 Image File: 0x6B W 22:49:44 Total Errors in Sector: 2.042 I 22:49:44 Verifying Sectors... W 22:49:44 Miscompare at LBA: 1012665, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:44 Device: 0x00 W 22:49:44 Image File: 0x6B W 22:49:44 Total Errors in Sector: 2.042 I 22:49:44 Verifying Sectors... W 22:49:45 Miscompare at LBA: 1012666, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:45 Device: 0x00 W 22:49:45 Image File: 0x6B W 22:49:45 Total Errors in Sector: 2.043 I 22:49:45 Verifying Sectors... W 22:49:46 Miscompare at LBA: 1012667, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:46 Device: 0x00 W 22:49:46 Image File: 0x6B W 22:49:46 Total Errors in Sector: 2.039 I 22:49:46 Verifying Sectors... W 22:49:46 Miscompare at LBA: 1012668, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:46 Device: 0x00 W 22:49:46 Image File: 0x6B W 22:49:46 Total Errors in Sector: 2.040 I 22:49:46 Verifying Sectors... W 22:49:47 Miscompare at LBA: 1012669, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:47 Device: 0x00 W 22:49:47 Image File: 0x32 W 22:49:47 Total Errors in Sector: 2.043 I 22:49:47 Verifying Sectors... W 22:49:47 Miscompare at LBA: 1012670, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:47 Device: 0x00 W 22:49:48 Image File: 0x32 W 22:49:48 Total Errors in Sector: 2.048 I 22:49:48 Verifying Sectors... W 22:49:48 Miscompare at LBA: 1012671, Offset: 0, File: \VIDEO_TS\VTS_01_2.VOB W 22:49:48 Device: 0x00 W 22:49:48 Image File: 0x32 W 22:49:48 Total Errors in Sector: 2.026 I 22:49:49 Verifying Sectors... I 22:53:18 Verifying Layer 1... (LBA: 1952432 - 3894658) W 23:01:13 Miscompare at LBA: 3730685, Offset: 1800, File: \VIDEO_TS\VTS_08_1.VOB W 23:01:13 Device: 0x0C W 23:01:13 Image File: 0x5F W 23:01:13 Total Errors in Sector: 246 I 23:01:13 Verifying Sectors... W 23:01:13 Miscompare at LBA: 3730686, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 23:01:13 Device: 0x34 W 23:01:13 Image File: 0x00 W 23:01:13 Total Errors in Sector: 2.030 I 23:01:13 Verifying Sectors... W 23:01:14 Miscompare at LBA: 3730687, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 23:01:14 Device: 0xC4 W 23:01:14 Image File: 0x00 W 23:01:14 Total Errors in Sector: 2.034 I 23:01:14 Verifying Sectors... I 23:02:24 Device MD5: 846f435d2080d9b475e4411d1fe62644 I 23:02:24 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 I 23:02:24 Image MD5: e38377b89bfa3b5ff1f72a4870aa8f31 W 23:02:24 Miscompare between Device and Image MD5 hash values! I 23:02:41 Exporting Graph Data... I 23:02:41 Graph Data File: D:\Computadora\Log Data\ImgBurn\Graph Data Files\2010-03-15_21-05_PIONEER_DVD-RW_DVR-111D_1.29_MKM-001-00_MOON_2,4x.ibg I 23:02:41 Export Successfully Completed! I 23:02:41 Operation Successfully Completed! - Duration: 01:14:15 I 23:02:41 Average Verify Rate: 1.753 KB/s (1.3x) - Maximum Verify Rate: 10.344 KB/s (7.5x) I 23:04:33 Operation Started! I 23:04:33 Source Device: [2:1:0] SONY DVD-ROM DDU1615 FYS3 (E:) (ATA) I 23:04:33 Source Media Type: DVD-ROM (Book Type: DVD-ROM) I 23:04:33 Image File: D:\Video\Image Files\MOON.MDS I 23:04:33 Image File Sectors: 3.894.659 (MODE1/2048) I 23:04:33 Image File Size: 7.976.261.632 bytes I 23:04:33 Image File Volume Identifier: MOON I 23:04:33 Image File Volume Set Identifier: 3b480d42 I 23:04:33 Image File Implementation Identifier: Sonic Scenarist 3.1 I 23:04:33 Image File File System(s): ISO9660, UDF (1.02) I 23:04:33 Read Speed (Data/Audio): MAX / MAX I 23:04:33 Hardware Read Error Retries: 2 I 23:04:33 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3894658) I 23:04:33 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3894658) W 23:06:17 Miscompare at LBA: 159323, Offset: 776, File: \VIDEO_TS\VTS_01_0.VOB W 23:06:17 Device: 0xE7 W 23:06:17 Image File: 0x10 W 23:06:17 Total Errors in Sector: 1.272 I 23:06:17 Verifying Sectors... W 23:06:17 Miscompare at LBA: 159324, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 23:06:17 Device: 0x00 W 23:06:17 Image File: 0xBC W 23:06:17 Total Errors in Sector: 2.041 I 23:06:17 Verifying Sectors... W 23:06:18 Miscompare at LBA: 159325, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 23:06:18 Device: 0x00 W 23:06:18 Image File: 0xBC W 23:06:18 Total Errors in Sector: 2.046 I 23:06:18 Verifying Sectors... W 23:06:19 Miscompare at LBA: 159326, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 23:06:19 Device: 0x00 W 23:06:19 Image File: 0xBC W 23:06:19 Total Errors in Sector: 2.039 I 23:06:19 Verifying Sectors... W 23:06:19 Miscompare at LBA: 159327, Offset: 0, File: \VIDEO_TS\VTS_01_0.VOB W 23:06:19 Device: 0x00 W 23:06:19 Image File: 0xBC W 23:06:19 Total Errors in Sector: 2.040 I 23:06:23 Verifying Sectors... W 23:21:20 Miscompare at LBA: 3098101, Offset: 1992, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:20 Device: 0x9B W 23:21:20 Image File: 0xF9 W 23:21:20 Total Errors in Sector: 56 I 23:21:20 Verifying Sectors... W 23:21:21 Miscompare at LBA: 3098102, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:21 Device: 0x00 W 23:21:21 Image File: 0x9C W 23:21:21 Total Errors in Sector: 2.036 I 23:21:21 Verifying Sectors... W 23:21:21 Miscompare at LBA: 3098103, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:21 Device: 0x00 W 23:21:21 Image File: 0x2D W 23:21:21 Total Errors in Sector: 2.031 I 23:21:21 Verifying Sectors... W 23:21:23 Miscompare at LBA: 3098104, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:23 Device: 0x00 W 23:21:23 Image File: 0x68 W 23:21:23 Total Errors in Sector: 2.042 I 23:21:23 Verifying Sectors... W 23:21:24 Miscompare at LBA: 3098105, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:24 Device: 0x00 W 23:21:24 Image File: 0x68 W 23:21:24 Total Errors in Sector: 2.041 I 23:21:25 Verifying Sectors... W 23:21:25 Miscompare at LBA: 3098106, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:25 Device: 0x00 W 23:21:25 Image File: 0x68 W 23:21:25 Total Errors in Sector: 2.033 I 23:21:25 Verifying Sectors... W 23:21:26 Miscompare at LBA: 3098107, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:26 Device: 0x00 W 23:21:26 Image File: 0x68 W 23:21:26 Total Errors in Sector: 2.034 I 23:21:26 Verifying Sectors... W 23:21:26 Miscompare at LBA: 3098108, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:26 Device: 0x00 W 23:21:26 Image File: 0x68 W 23:21:26 Total Errors in Sector: 2.043 I 23:21:26 Verifying Sectors... W 23:21:27 Miscompare at LBA: 3098109, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:27 Device: 0x00 W 23:21:27 Image File: 0x68 W 23:21:27 Total Errors in Sector: 2.040 I 23:21:27 Verifying Sectors... W 23:21:28 Miscompare at LBA: 3098110, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:28 Device: 0x00 W 23:21:28 Image File: 0x68 W 23:21:28 Total Errors in Sector: 2.029 I 23:21:28 Verifying Sectors... W 23:21:28 Miscompare at LBA: 3098111, Offset: 0, File: \VIDEO_TS\VTS_02_2.VOB W 23:21:28 Device: 0x00 W 23:21:28 Image File: 0x68 W 23:21:28 Total Errors in Sector: 2.035 I 23:21:28 Verifying Sectors... W 23:25:41 Miscompare at LBA: 3730685, Offset: 1800, File: \VIDEO_TS\VTS_08_1.VOB W 23:25:41 Device: 0x0C W 23:25:41 Image File: 0x5F W 23:25:41 Total Errors in Sector: 246 I 23:25:41 Verifying Sectors... W 23:25:41 Miscompare at LBA: 3730686, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 23:25:41 Device: 0x34 W 23:25:41 Image File: 0x00 W 23:25:41 Total Errors in Sector: 2.030 I 23:25:41 Verifying Sectors... W 23:25:42 Miscompare at LBA: 3730687, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 23:25:42 Device: 0xC4 W 23:25:42 Image File: 0x00 W 23:25:42 Total Errors in Sector: 2.034 I 23:25:42 Verifying Sectors... I 23:27:06 Device MD5: 846f435d2080d9b475e4411d1fe62644 I 23:27:06 Image MD5: 32a3e95656e0a3151c2027c9781a00e7 W 23:27:06 Miscompare between Device and Image MD5 hash values! I 23:27:19 Exporting Graph Data... I 23:27:19 Graph Data File: D:\Computadora\Log Data\ImgBurn\Graph Data Files\2010-03-15_23-04_SONY_DVD-ROM_DDU1615_FYS3_N-A_MOON.ibg I 23:27:19 Export Successfully Completed! I 23:27:19 Operation Successfully Completed! - Duration: 00:22:42 I 23:27:19 Average Verify Rate: 5.761 KB/s (4.2x) - Maximum Verify Rate: 10.887 KB/s (7.9x) I 23:28:50 Close Request Acknowledged I 23:28:50 Closing Down... I 23:28:50 Shutting down SPTI... I 23:28:50 ImgBurn closed! Soon enough, I'll be telling you if playback works fine. Thanks a bunch!!
LIGHTNING UK! Posted March 16, 2010 Posted March 16, 2010 2) All retries are set to default. That's not true. It shouldn't be setting the hardware retries at all. Uncheck the box. I use the default settings 24/7. They're the ones that get all the testing and you shouldn't need to change away from any of them - except for the ones where you configure paths etc perhaps. Is this issue just with double layer discs? As the drive MD5 is the constant here, I guess that's not the issue and it shouldn't matter if it's SL or DL. You should keep doing the verifies and see how often the image md5 changes and if the problem sectors keep moving around. Have you run memtest on your PC at all? It might be worth doing that for a couple of passes. If you have a 2nd HDD (internal or external) you could try burning from, that might be worth doing to see if you run into the same issue.
aguilacuervo Posted March 16, 2010 Author Posted March 16, 2010 That's not true. It shouldn't be setting the hardware retries at all. Uncheck the box. Oh, I'm sorry. I didn't realize that. Will do. I use the default settings 24/7. They're the ones that get all the testing and you shouldn't need to change away from any of them - except for the ones where you configure paths etc perhaps. On second thought, I don't think my changes are all that significant, but I'll take a look. From what I can remember I think my greatest victory at the time of changes was due to moving away from TAO to Incremental. Since then, I almost never had Write Errors again. And for a long while, I never had these miscompare problems. Actually, not even with Hardware Retries on did I have this problem for a long time. This is rather recent. You think using Incremental writing might be a problem? I didn't change much else I think. Is this issue just with double layer discs? As the drive MD5 is the constant here, I guess that's not the issue and it shouldn't matter if it's SL or DL. I haven't been testing thoroughly enough with SL discs to tell. This was my first try-all when it happens. We'll see. You should keep doing the verifies and see how often the image md5 changes and if the problem sectors keep moving around. Have you run memtest on your PC at all? It might be worth doing that for a couple of passes. If you have a 2nd HDD (internal or external) you could try burning from, that might be worth doing to see if you run into the same issue. More tests to run! I'll do that. Moreover, playback's fine as far as I can tell. Didn't try every single feature though. Thanks!!!
LIGHTNING UK! Posted March 16, 2010 Posted March 16, 2010 Hopefully you mean DAO/SAO rather than TAO. DAO/SAO is the default and TAO really only applies to CD. I only mentioned SL discs because it's silly to keep wasting DVD+R DL's when a DVD-RW or DVD+RW would do the job equally well. Hell, as it's looking more like an issue with the HDD stream (because the image file MD5 changes and not the drive one), even a CD-RW would probably do the trick. If you're in the mood for doing tests, might as well do a full chkdsk scan on your hdds too
aguilacuervo Posted March 18, 2010 Author Posted March 18, 2010 Yes, I meant DAO/SAO. I seem to be rather forgetful about defaults. Ok, this is what I got so far: I've been running tests over and over with my last burn (the one above). I will jump ahead and post just the md5 values. 1) On image creation: Image MD5: 73c6368066b9f694986d38da1acec4a6 2) On image burn: Image MD5: 846f435d2080d9b475e4411d1fe62644 3) On first verify (with drive 1): Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: e38377b89bfa3b5ff1f72a4870aa8f31 4) On first verify (with drive 2): Device MD5: 846f435d2080d9b475e4411d1fe62644 Image MD5: 32a3e95656e0a3151c2027c9781a00e7 Hardware Retries is on and set to 2 for these two. Upon disabling Hardware Retries, what I did was try to copy the image to another HDD to verify from there, but I couldn't do it with the first alternate HDD I tried. I just kept getting mismatching hash values after copy, so I just did one verify from this alternate HDD, and it didn't bring much to the table: 5) On first and only verify with alternate internal HDD (drive 1): Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: f31dcc525822cf0f54bf6347f54845d0 Then I tried another HDD (external) and copying was successful this time: 6) On first verify with alternate external HDD (drive 1): Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 73c6368066b9f694986d38da1acec4a6 7) On second verify -idem-: Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 73c6368066b9f694986d38da1acec4a6 Notice these two are a mismatch, but the same mismatch both times. By now I had realized that not only the Device MD5 is always the same, but that it's the same as the one originally reported on disc burn (might not mean much). Device (Padded) MD5, whatever that means, is also always the same. Later, I would also see that this mismatching MD5 values that start to keep coming up here show the correct (original) Image MD5 value. I was feeling rather dizzy by this point and I wanted to desperately avoid doing a chkdsk, so I did some more verifies from the original HDD (with Hardware Retries disabled this time): 8) On first verify (second batch) with original HDD, drive 1: Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 42210b10fa4f87a33708a8b55530bf8b 9) On second blah blah blah: Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 73c6368066b9f694986d38da1acec4a6 See now, the first is just plain random again, but the second is the same as the two I got from the external HDD. I caved in and run a chkdsk on the original 2TB HDD. This took forever. I went to bed at one point and when I woke up Windows had restarted. Does anyone know how can I see the results of this? Is there a log somewhere in Windows? Thank you. Also, I ran a few memtests a while back and there seems to be nothing wrong with my RAM. The cards are brand new and ECC. So, anyway, after that I did another verify from the original HDD. 10) Results (drive 1): Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 73c6368066b9f694986d38da1acec4a6 Same as the other three. This is becoming a pattern. I ran one more on the external HDD: 11) Results (drive 1): Device MD5: 846f435d2080d9b475e4411d1fe62644 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 Image MD5: 73c6368066b9f694986d38da1acec4a6 Same again. So, upon writing this now I realize I should have done a few more verifies with drive 2. Here they are: 12) On verify with external HDD (drive 2): Device MD5: 846f435d2080d9b475e4411d1fe62644 Image MD5: 73c6368066b9f694986d38da1acec4a6 13) On verify with original HDD after chkdsk (drive 2): Device MD5: 846f435d2080d9b475e4411d1fe62644 Image MD5: 73c6368066b9f694986d38da1acec4a6 Same again. Any idea what this all means? I'm guessing the repeating verify values are the good ones. They match the original ones from read and burn, but why are they a mismatch? Miscompares here are very few. Just 3 at 95%. Maybe the copy is bad after all (dammit). But not so bad, right? I could live with 3 miscompares I guess. Here's the repeating log: I 11:21:19 Operation Started! I 11:21:19 Source Device: [2:0:0] PIONEER DVD-RW DVR-111D 1.29 (F:) (ATA) I 11:21:19 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-001-00) (Speeds: 2,4x, 4x, 6x, 8x) I 11:21:19 Image File: D:\Videos\Image Files\MOON.MDS I 11:21:19 Image File Sectors: 3.894.659 (MODE1/2048) I 11:21:19 Image File Size: 7.976.261.632 bytes I 11:21:19 Image File Volume Identifier: MOON I 11:21:19 Image File Volume Set Identifier: 3b480d42 I 11:21:19 Image File Implementation Identifier: Sonic Scenarist 3.1 I 11:21:19 Image File File System(s): ISO9660, UDF (1.02) I 11:21:19 Read Speed (Data/Audio): MAX / MAX I 11:21:20 Verifying Session 1 of 1... (1 Track, LBA: 0 - 3894658) I 11:21:20 Verifying Track 1 of 1... (MODE1/2048, LBA: 0 - 3894658) I 11:21:20 Verifying Layer 0... (LBA: 0 - 1952431) I 11:30:27 Verifying Layer 1... (LBA: 1952432 - 3894658) W 11:38:26 Miscompare at LBA: 3730685, Offset: 1800, File: \VIDEO_TS\VTS_08_1.VOB W 11:38:26 Device: 0x0C W 11:38:26 Image File: 0x5F W 11:38:26 Total Errors in Sector: 246 I 11:38:26 Verifying Sectors... W 11:38:26 Miscompare at LBA: 3730686, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 11:38:26 Device: 0x34 W 11:38:26 Image File: 0x00 W 11:38:26 Total Errors in Sector: 2.030 I 11:38:26 Verifying Sectors... W 11:38:27 Miscompare at LBA: 3730687, Offset: 0, File: \VIDEO_TS\VTS_08_1.VOB W 11:38:27 Device: 0xC4 W 11:38:27 Image File: 0x00 W 11:38:27 Total Errors in Sector: 2.034 I 11:38:27 Verifying Sectors... I 11:39:36 Device MD5: 846f435d2080d9b475e4411d1fe62644 I 11:39:37 Device (Padded) MD5: 5668fd8f156aedb84d69fc13bd6d4003 I 11:39:37 Image MD5: 73c6368066b9f694986d38da1acec4a6 W 11:39:37 Miscompare between Device and Image MD5 hash values! I 11:39:42 Exporting Graph Data... I 11:39:42 Graph Data File: D:\Computadora\Log Data\ImgBurn\Graph Data Files\2010-03-18_11-21_PIONEER_DVD-RW_DVR-111D_1.29_MKM-001-00_MOON.ibg I 11:39:42 Export Successfully Completed! I 11:39:42 Operation Successfully Completed! - Duration: 00:18:19 I 11:39:42 Average Verify Rate: 7.107 KB/s (5.1x) - Maximum Verify Rate: 10.301 KB/s (7.4x) Ok, enough detective work for today. Thank you very much!!
aguilacuervo Posted March 18, 2010 Author Posted March 18, 2010 (edited) OK, I guess this is pretty much solved already. Just one more thing. I just played this famous VTS_08_1.VOB that keeps getting miscompared, and there's a definite glitch there that's not in the original version stored in the image. What is causing this? I will check the other DVDs I had problems with now that I know how to spot the failure if there is any. Edited March 18, 2010 by aguilacuervo
aguilacuervo Posted March 27, 2010 Author Posted March 27, 2010 Ok, I think I might have an idea of what's going on. The problem seems to be in the HDD, right? Ok, tell me if I'm wrong, but I think this could have something to do with other apps using the HDD at the same time I'm burning a disc. Like downloading apps writing to it. Could this be? I don't have memory or CPU problems, so most of the time I keep uTorrent running in the backround. Could this be a problem? On top of this, uTorrent has a few peculiar Disk-Cache-handling settings that could be interfering as well. Are you familiar with uTorrent? Let me know if this is it (or if I'm on the right track!). Most default settings (and I never touched these) tend to minimize HDD usage in favor of memory, but some don't. It also disables Windows caching of disc writes by default. This seems pretty wide-ranging and it might have some impact on other programs. I don't know. Please advice. Thanks!
Recommended Posts