Jump to content

Verify stops with DL at 99%


Sliztzan

Recommended Posts

It stops but the time elapsed still running and time remaining at Unknown. There is no error message. In status it still says verifying sectors and verify rate 0 Kb/s. I've tried this on two drives. On the first drive it completed verify with no errors the second try. I did it again and same problem. Moved to another drive no success. What is wrong?

Thank you!

 

; //****************************************\\

; ImgBurn Version 2.4.0.0 - Log

; Wednesday, 27 February 2008, 21:48:29

; \\****************************************//

;

;

I 21:35:23 ImgBurn Version 2.4.0.0 started!

I 21:35:23 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 21:35:23 Total Physical Memory: 3,143,404 KB - Available: 2,225,604 KB

I 21:35:23 Initialising SPTI...

I 21:35:23 Searching for SCSI / ATAPI devices...

I 21:35:24 Found 1 DVD-ROM and 2 DVD±RWs!

I 21:35:45 Operation Started!

I 21:35:45 Source Device: [3:0:0] PLEXTOR DVDR PX-740A 1.02 (G:) (ATA)

I 21:35:45 Source Media Type: DVD+R DL (Book Type: DVD-ROM) (Disc ID: MKM-003-00) (Speeds: 2.4x, 4x, 8x)

I 21:35:45 Image File: C:\Program Files\NewsRover\Projects\88\Files\SCCV\SCCV.MDS

I 21:35:45 Image File Sectors: 2,752,112 (MODE1/2048)

I 21:35:45 Image File Size: 5,636,325,376 bytes

I 21:35:45 Image File Volume Identifier: SCHOOL_CRUISE

I 21:35:45 Image File Volume Set Identifier: 422F79A10000004D

I 21:35:45 Image File Application Identifier: MKISOFS ISO 9660/HFS FILESYSTEM BUILDER & CDRECORD CD-R/DVD CREATOR

Edited by Sliztzan
Link to comment
Share on other sites

Nope, not really!

 

If it happens again and again, get back to me with a screenshot of the main window so I can see exactly how much data it's thinks it's read and how much it's supposed to be reading.

 

EDIT:

 

Mount the MDS in DEAMON Tools and then use Verify mode to verify the virtual drive against the image. Just to see if that works!

 

Also please copy + paste everything from the info window on the right when the 'problem' burnt DL disc is in a 'problem' drive.

Link to comment
Share on other sites

Ok I mounted the image with Daemon Tools and verified the mounted image drive against the image file and it verified OK.

 

Since this problem I've burned about 10 more DL DVD's and the problem hasn't happened again.

 

Here is the copied information you requested from the 'problem' disc. Thank you!

 

PLEXTOR DVDR PX-755A 1.08 (ATA)

Current Profile: DVD+R DL

 

Disc Information:

Status: Complete

Erasable: No

Sessions: 1

Sectors: 2,752,096

Size: 5,636,292,608 bytes

Time: 611:36:46 (MM:SS:FF)

 

TOC Information:

Session 1...

-> Track 01 (Mode ???, LBA: 0 - 2752095) ------------ I JUST NOTICED THESE QUESTION MARKS HERE ???

-> LeadOut (LBA: 2752096)

 

Physical Format Information (ADIP):

Disc ID: MKM-003-00

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,580,607

Last Physical Sector in Layer 0: 2,283,519

 

Physical Format Information (Last Recorded):

Disc ID: MKM-003-00

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 15,760,703

Last Physical Sector in Layer 0: 1,982,607

 

Layer Information:

Layer 0 Sectors: 1,786,000 (64.9%)

Layer 1 Sectors: 966,096 (35.1%)

Edited by Sliztzan
Link to comment
Share on other sites

Before the burn...

I 15:23:59 Source File Sectors: 2,752,112 (MODE1/2048)

I 20:20:12 Image File Size: 5,636,325,376 bytes

 

Size on disc after the burn...

Sectors: 2,752,096

Size: 5,636,292,608 bytes

 

So somewhere along the line it appears to have lost the last ECC block of sectors.

 

The ??? is also worrying.

Link to comment
Share on other sites

This disc would be hard to replace since it has been discontinued, so I tried burning it again and all looks ok now and passed verification. But what I don't understand is why the verify would not pick up this problem?

 

Is there some bug with verify?

 

PLEXTOR DVDR PX-755A 1.08 (ATA)

Current Profile: DVD+R DL

 

Disc Information:

Status: Complete

Erasable: No

Sessions: 1

Sectors: 2,752,112

Size: 5,636,325,376 bytes

Time: 611:36:62 (MM:SS:FF)

 

TOC Information:

Session 1...

-> Track 01 (Mode 1, LBA: 0 - 2752111)

-> LeadOut (LBA: 2752112)

 

Physical Format Information (ADIP):

Disc ID: MKM-003-00

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,580,607

Last Physical Sector in Layer 0: 2,283,519

 

Physical Format Information (Last Recorded):

Disc ID: MKM-003-00

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 15,760,719

Last Physical Sector in Layer 0: 1,982,607

 

Layer Information:

Layer 0 Sectors: 1,786,000 (64.9%)

Layer 1 Sectors: 966,112 (35.1%)

Link to comment
Share on other sites

Well by not finishing, it kinda is picking up on the problem!

 

There's no check for track sizes between drive and image file, just the actual number of sessions/tracks and their data formats. After that it's just down to the byte level data comparison.

 

Obviously you have run into a situation that shouldn't ever occur and if I'm honest, ImgBurn could have handled it a little better rather than just 'waiting' to compare more data when the thread that reads the info from the drive had actually finished.

 

For that reason, I've done some tweaking today so that the track sizes are now compared and you'll get a warning if the device one is smaller than the image file one (can't really check the other way around because that can actually happen). Assuming you want to go ahead and compare it anyway, the program will pad out the track (as read from the drive) with empty sectors until they're the same size.

Link to comment
Share on other sites

Thanks Lightning! I somewhat understand what you did and thanks for the honesty.

I verify all my burns since I found out through your forum this is the proper way of doing burns. I always count on verify and I'm sure this was an oddity.

Link to comment
Share on other sites

It happened again tonight with another image:

 

Should I burn this disc again?

 

; //****************************************\\

; ImgBurn Version 2.4.0.0 - Log

; Tuesday, 11 March 2008, 01:42:48

; \\****************************************//

;

;

I 00:31:50 ImgBurn Version 2.4.0.0 started!

I 00:31:50 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)

I 00:31:50 Total Physical Memory: 3,143,404 KB - Available: 2,525,248 KB

I 00:31:51 Initialising SPTI...

I 00:31:51 Searching for SCSI / ATAPI devices...

I 00:31:51 Found 1 DVD-ROM and 2 DVD

Edited by Sliztzan
Link to comment
Share on other sites

Before burn...

I 00:32:29 Source File Sectors: 3,625,424 (MODE1/2048)

 

After burn...

TOC Information:

Session 1...

-> Track 01 (Mode ???, LBA: 0 - 3625407)

-> LeadOut (LBA: 3625408)

 

Do you have another drive you could use to see how that disc is read / initialised?

 

It's coming up 16 sectors short again in the plextor. This is NOT a good thing!

Link to comment
Share on other sites

Here is the information from an older Plextor drive #740

 

BTW, you told me you fixed it last week, but I never got the fix and don't know where to get it.

 

PLEXTOR DVDR PX-740A 1.02 (ATA)

Current Profile: DVD+R DL

 

Disc Information:

Status: Complete

Erasable: No

Sessions: 1

Sectors: 3,625,408

Size: 7,424,835,584 bytes

Time: 805:40:58 (MM:SS:FF)

 

TOC Information:

Session 1...

-> Track 01 (Mode 1, LBA: 0 - 3625407)

-> LeadOut (LBA: 3625408)

 

Physical Format Information (ADIP):

Disc ID: MKM-003-00

Book Type: DVD+R DL

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,580,607

Last Physical Sector in Layer 0: 2,283,519

 

Physical Format Information (Last Recorded):

Disc ID: MKM-003-00

Book Type: DVD-ROM

Part Version: 1

Disc Size: 120mm

Maximum Read Rate: Not Specified

Number of Layers: 2

Track Path: Opposite Track Path (OTP)

Linear Density: 0.293 um/bit

Track Density: 0.74 um/track

First Physical Sector of Data Area: 196,608

Last Physical Sector of Data Area: 16,288,383

Last Physical Sector in Layer 0: 2,155,423

 

Layer Information:

Layer 0 Sectors: 1,958,816 (54.03%)

Layer 1 Sectors: 1,666,592 (45.97%)

Edited by Sliztzan
Link to comment
Share on other sites

The warning for disc tracks being smaller than image tracks isn't in a version of ImgBurn that's out yet, it's in 2.4.1.0 - whenever I get to the stage where it's ready for release.

 

The real fix here is to use a different drive for burning. That plextor seems to keep losing the last 16 sectors for some reason.

Link to comment
Share on other sites

Doesn't happen everytime?? This is the second time it's happened in about 200 burns. Why would it only happen twice?

I hesitate burning DL on the older one because it doesn't have the capability to adjust laser position.

 

Edit:

This makes me consider getting a newer drive. I know that Plextor hasn't made any drives since the 760 and are outsourcing now. Would you be willing to recommend a replacement that was AS good or better than Plextor now? I haven't even looked into new drives for years.

Edited by Sliztzan
Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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