Jump to content

Recommended Posts

Posted

hello,

 

i've got a .iso file and i want to burn it to dvd

but if im trying to do it i get an error :Unable to recover TOC

here is my log:

I 19:58:42 Operation Started!

I 19:58:42 Source File: D:\Users\Alex\Documents\Vuze Downloads\Avatar (2009) Retail (PAL) (DVD5) 2Lions-Team\Movie\AVATAR.ISO

I 19:58:42 Source File Sectors: 2.267.488 (MODE1/2048)

I 19:58:42 Source File Size: 4.643.815.424 bytes

I 19:58:42 Source File Volume Identifier: NEWTON

I 19:58:42 Source File Volume Set Identifier: 3C9092790022995F

I 19:58:42 Source File Application Identifier: IMGBURN V2.5.1.0 - THE ULTIMATE IMAGE BURNER!

I 19:58:42 Source File Implementation Identifier: ImgBurn

I 19:58:42 Source File File System(s): ISO9660; UDF (1.02)

I 19:58:42 Destination Device: [0:0:0] MATSHATA BD-CMB UJ%120 1.00 (E:) (ATA)

I 19:58:42 Destination Media Type: DVD+R (Disc ID: TDK-003-00) (Speeds: 2,4x; 4x; 6x; 8x)

I 19:58:42 Destination Media Sectors: 2.295.104

I 19:58:42 Write Mode: DVD

I 19:58:42 Write Type: DAO

I 19:58:42 Write Speed: 2,4x

I 19:58:42 DVD+R Reserve Track: No

I 19:58:42 Link Size: Auto

I 19:58:42 Lock Volume: Yes

I 19:58:42 Test Mode: No

I 19:58:42 OPC: No

I 19:58:42 BURN-Proof: Enabled

I 19:58:42 Write Speed Successfully Set! - Effective: 3.324 KB/s (2,4x)

I 19:58:42 Filling Buffer... (40 MB)

I 19:58:43 Writing LeadIn...

W 19:58:51 Failed to Write Sectors 3712 - 3743 - Reason: Unknown (ASC: 0x09, ASCQ: 0x90)

W 19:58:51 Retrying (1 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (2 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (3 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (4 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (5 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (6 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (7 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (8 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (9 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (10 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (11 of 20)...

W 19:58:51 Retry Failed - Reason: Unable to Recover TOC

W 19:58:51 Retrying (12 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (13 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (14 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (15 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (16 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (17 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (18 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (19 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

W 19:58:52 Retrying (20 of 20)...

W 19:58:52 Retry Failed - Reason: Unable to Recover TOC

E 19:58:55 Failed to Write Sectors 3712 - 3743 - Reason: Unknown (ASC: 0x09, ASCQ: 0x90)

I 19:58:55 Synchronising Cache...

W 20:00:38 User opted to skip the 'Close Track/Session/Disc' functions.

E 20:00:39 Failed to Write Image!

E 20:00:39 Operation Failed! - Duration: 00:01:56

I 20:00:39 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)

E 20:00:49 User attempted to burn an image file in 'Build' mode.

I 20:00:49 Calculating Totals...

E 20:00:49 No files or folders were added to the image!

Posted

Try burning at 4x, 6x or 8x. Try with Verbatim or Taiyo Yuden blanks. Try cleaning the drive with a cleaning disc.

Posted

Try burning at 4x, 6x or 8x. Try with Verbatim or Taiyo Yuden blanks. Try cleaning the drive with a cleaning disc.

 

 

 

I have tried everything you said but it doesn't work

Posted
I 19:58:42 Destination Device: [0:0:0] MATSHATA BD-CMB UJ%120 1.00 (E:) (ATA)

 

You have a drive that's not even show corectly his name. It should be "MATSHITA BD-CMB UJ-120". Probably a firmware problem.

 

As i think it is in a laptop drive, try a firmware update on producer site. And you should follow what mmalves said

Posted
I 19:58:42 Destination Device: [0:0:0] MATSHATA BD-CMB UJ%120 1.00 (E:) (ATA)

 

You have a drive that's not even show corectly his name. It should be "MATSHITA BD-CMB UJ-120". Probably a firmware problem.

 

As i think it is in a laptop drive, try a firmware update on producer site. And you should follow what mmalves said

 

thanks for reply

but I've tried everything

but maybe you got something on this whatch:MATSHITA BD-CMB UJ-120 1.00 (ATA)

Current Profile: DVD+R

 

Disc Information:

Status: Empty

State of Last Session: Empty

Erasable: No

Free Sectors: 2.295.104

Free Space: 4.700.372.992 bytes

Free Time: 510:03:29 (MM:SS:FF)

Next Writable Address: 0

Supported Write Speeds: 2,4x; 4x; 6x; 8x

 

there stands:Eresable:NO

 

maybe it's the problem?

Posted

There is no problem. It is a DVD+R and it is not eresable. Maybe you got fooled by the logo http://www.dvdrw.com

 

MATSHITA have a reputation on not offering almost any firmware update support. Some say it is written in their name: MatSHITa

 

If you don't find any update on laptop producer site, maybe you can start looking for an external drive.

Posted

There is no problem. It is a DVD+R and it is not eresable. Maybe you got fooled by the logo http://www.dvdrw.com

 

MATSHITA have a reputation on not offering almost any firmware update support. Some say it is written in their name: MatSHITa

 

If you don't find any update on laptop producer site, maybe you can start looking for an external drive.

[/quote

 

 

ok but i got this problem since i've got windows 7 on my pc

first i had windows vista and everything did work

and now i don't

Posted

You can search the forum for similar errors and see for yourself that is drive related no matter what OS. Blame the manufacturer.

 

As far as I read other posts with similar problem nothing seems to fix this kind of error.

 

Keep in mind that things broke after a wile, nothing is eternal. So, in the end you may stuck on searching solutions that are virtualy none.

×
×
  • Create New...

Important Information

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