Jump to content
Sign in to follow this  
Nicotina09

Problem with [ I/O error ]

Recommended Posts

Hello how are you? well my problem is this. I try to burn a Playstation 2 game is dual layer. dispose of 10 DVD + R DL Verbatim brand because they recorded wrong .. I'm aware of putting the layerbreak and change the booktype to DVD-ROM, use new Pioneer and LG writers and do not understand what the problem .. when I start to record 97% and reach out [i / O error]. The truth is no longer what else to do the ISO is proven and is 100% right .. The writers have no problem .. I have a Pioneer 112D flashed to 112L and a LG GSA-41267B. Please help me: (.. I let images!

 

parte1zk.jpg

 

parte2o.jpg

 

parte3u.jpg

 

parte4e.jpg

 

 

Goodbye and hope you can help me:).

Share this post


Link to post
Share on other sites

Here's the log!

 

I 02:04:54 ImgBurn Version 2.5.5.0 started!

I 02:04:54 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3)

I 02:04:54 Total Physical Memory: 982.252 KB - Available: 593.908 KB

I 02:04:54 Initialising SPTI...

I 02:04:54 Searching for SCSI / ATAPI devices...

I 02:04:55 -> Drive 1 - Info: HL-DT-ST DVDRAM GSA-4167B DL12 (E:) (ATA)

I 02:04:55 Found 1 DVD±RW/RAM!

I 02:30:56 Operation Started!

I 02:30:56 Source File: D:\GOD OF WAR I en esmlpro\GOW1 by_gabymalo.iso

I 02:30:56 Source File Sectors: 3.915.344 (MODE1/2048)

I 02:30:56 Source File Size: 8.018.624.512 bytes

I 02:30:56 Source File Volume Identifier: GODOFWAR

I 02:30:56 Source File Volume Set Identifier: =056::23SCEI

I 02:30:56 Source File Application Identifier: PLAYSTATION

I 02:30:56 Source File Implementation Identifier: DVD-ROM GENERATOR

I 02:30:56 Source File File System(s): ISO9660, UDF (1.02)

I 02:30:56 Destination Device: [1:0:0] HL-DT-ST DVDRAM GSA-4167B DL12 (E:) (ATA)

I 02:30:56 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2,4x)

I 02:30:56 Destination Media Sectors: 4.173.824

I 02:30:56 Write Mode: DVD

I 02:30:56 Write Type: DAO

I 02:30:56 Write Speed: 2,4x

I 02:30:56 Link Size: Auto

I 02:30:56 Lock Volume: Yes

I 02:30:56 Test Mode: No

I 02:30:56 OPC: No

I 02:30:56 BURN-Proof: Enabled

I 02:30:56 Write Speed Successfully Set! - Effective: 3.324 KB/s (2,4x)

I 02:30:56 Book Type Setting: DVD-ROM

W 02:31:12 User specified layer break position is such that L0 < L1.

W 02:31:12 Image Size: 3.915.344

W 02:31:12 User Specified L0 Sectors: 1.902.128

W 02:31:12 Calculated L1 Sectors: 2.013.216

I 02:31:12 User Specified L0 Data Zone Capacity: 1.902.128

I 02:31:46 Set L0 Data Zone Capacity Succeeded!

I 02:31:56 Filling Buffer... (20 MB)

I 02:31:57 Writing LeadIn...

I 02:31:59 Writing Session 1 of 1... (1 Track, LBA: 0 - 3915343)

I 02:31:59 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3915343)

I 02:31:59 Writing Layer 0... (LBA: 0 - 1902127)

I 02:51:27 Writing Layer 1... (LBA: 1902128 - 3915343)

W 03:10:59 Failed to Write Sectors 3804240 - 3804271 - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (1 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (2 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (3 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (4 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (5 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (6 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (7 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (8 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (9 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (10 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (11 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (12 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (13 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (14 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (15 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (16 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (17 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (18 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (19 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

W 03:10:59 Retrying (20 of 20)...

W 03:10:59 Retry Failed - Reason: Logical Block Address out of Range

E 03:13:53 Failed to Write Sectors 3804240 - 3804271 - Reason: Logical Block Address out of Range

I 03:13:53 Synchronising Cache...

W 03:14:51 User opted to skip the 'Close Track/Session/Disc' functions.

E 03:14:51 Failed to Write Image!

I 03:14:52 Exporting Graph Data...

I 03:14:52 Graph Data File: C:\Documents and Settings\Sakuragi\Datos de programa\ImgBurn\Graph Data Files\HL-DT-ST_DVDRAM_GSA-4167B_DL12_MARTES-01-DE-FEBRERO-DE-2011_02-30_a.m._MKM-003-00_2,4x.ibg

I 03:14:52 Export Successfully Completed!

E 03:14:52 Operation Failed! - Duration: 00:43:55

I 03:14:52 Average Write Rate: 3.027 KB/s (2.2x) - Maximum Write Rate: 3.360 KB/s (2.4x)

I 03:20:42 Close Request Acknowledged

I 03:20:42 Closing Down...

I 03:20:42 Shutting down SPTI...

I 03:20:42 ImgBurn closed!

Share this post


Link to post
Share on other sites
W 02:31:12 User specified layer break position is such that L0

W 02:31:12 Image Size: 3.915.344

W 02:31:12 User Specified L0 Sectors: 1.902.128

W 02:31:12 Calculated L1 Sectors: 2.013.216

 

That is never going to work.

Share this post


Link to post
Share on other sites

But the game is supposed to go on a double layer disc .. 8Gbs weighs

 

I 2:30:56 Source File Sectors: 3,915,344 (MODE1/2048)

I 2:30:56 Source File Size: 8,018,624,512 bytes

Share this post


Link to post
Share on other sites

Let me rephrase that... it's never going to work with the layer break position set to where you've got it.

 

It's just not possible to burn more on the 2nd layer than the 1st.

Share this post


Link to post
Share on other sites

What happens in the Playstation 2 games the layer break is important because it is a unique value for each game .. In the XBOX games is different because the layer break is the same for all these games.

Share this post


Link to post
Share on other sites

That's great but I'm not sure how it's relevant?!

 

Whatever you want / need to set it to doesn't change the fact that you can't burn more on the 2nd layer than on the 1st.

 

It's just not physically possible.

Share this post


Link to post
Share on other sites

But if I put to calculate the layer break is not going to match up .. I already did .. and the game goes on the Playstation 2, but it's like that in a moment stop reading.

Share this post


Link to post
Share on other sites

I never said anything about using a different layer break, I just said it wouldn't work.

 

You cannot burn that image with the LB where you say it needs to be. As such, I suggest you just give up trying.

Share this post


Link to post
Share on other sites

A month ago or so I'm looking for information on this problem and I see people who put the layer break value and have no problem in completing the recording .. I do not understand is the problem of [i / O ERROR] sorry to be pushy but it works .. I must be doing something wrong and it's not ..

Share this post


Link to post
Share on other sites

You aren't doing anything wrong (beyond what I've already pointed out), it's just not possible.

 

Whoever said they'd burnt that same image with that same layer break position is lying to you.

Share this post


Link to post
Share on other sites

I do not understand the logical reason for what you are doing wrong .. is like having a DVD9 2 DVD5 .. certain data have to be in the DVD1 and certain facts have to be in the DVD2 .. in this case is the same ..

Share this post


Link to post
Share on other sites

Sorry but will not be a problem with that OTP or PTP? I want to clarify one thing .. what I write is a Playstation 2 game with nothing ripped. So it is a DVD9

Share this post


Link to post
Share on other sites

Original / pressed DVD-ROM discs can indeed be OTP or PTP. The DVD+R DL or DVD-R DL you buy will always be OTP.

 

PTP can have L1 larger than L0 but OTP cannot.

 

Sooo.... that image simply cannot be replicated excactly (i.e. with the LB in the correct place) onto DVD+R DL or DVD-R DL.

Share this post


Link to post
Share on other sites

No, you have to give up trying!

 

No matter what you do, you absolutely cannot burn that image with the layer break in that position. Period. End of story.

Share this post


Link to post
Share on other sites

I'm sure some would be fine, that one just isn't - or at least not if you want the LB in the original/correct position.

Share this post


Link to post
Share on other sites

I make one last question .. I have another game for Playstation 2 that the Layer Break so serious.

 

Sectors: 4,093,488

 

L0 Sectors: 2,080,912 [50.83%]

L1 Sectors: 2,012,576 [49.17%]

 

This is correct for burning?

Share this post


Link to post
Share on other sites

That should be fine because L0 is larger than L1.

 

L0 must always be larger than or equal to the size of L1.

 

If it's not, it'll just fail.

Share this post


Link to post
Share on other sites

Now that I think .. there is some way to record first L1 and then the L0?

 

L0: 1,902,128

 

L1: 2,013,216

Edited by Nicotina09

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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