Jump to content

Failed to Write Sectors - Logical Block Address out of Range


Recommended Posts

Posted

Greetings to all! I've toasted about 10 Bluray DVD's doing this project, trying every which way, 2X, 4X, 8X, and the error is pretty well the same. Please help.

 

The ISO file was created from one of my Bluray DVD collections as backup, using external LG BP06 Blu-ray writer and Philips BD-R, 25gb, 135HD, 1x – 6x. Now I have successfully created a few BluRay DVDs using exactly the same media, but with PowerDirector. The point is the hardware & media are probably not an issue.

 

 

 

Samsung (NP300V5A-S01CA)

Processor & speed

i3-2350M 2.3 GHz

Memory

6 GB DDR3 1.3mhz

CACHE

3 MB L3

Hard Drive

500 GB 5400 rpm

Bluetooth

3.0

CD-DVD Drive

Super multi DL R/W

Graphics

NVidia GeForce GT 520mx

Video Memory

1 gb

USB

3 USB 2.0

OS

Win 7 Home Prem

 

 

Here’s the log:

I 10:52:03 ImgBurn Version 2.5.7.0 started!

I 10:52:03 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7601 : Service Pack 1)

I 10:52:03 Total Physical Memory: 6,202,928 KB - Available: 3,698,580 KB

W 10:52:03 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled!

I 10:52:03 Initialising SPTI...

I 10:52:03 Searching for SCSI / ATAPI devices...

I 10:52:03 -> Drive 1 - Info: TSSTcorp CDDVDW SN-208BB SC00 (E:) (ATAPI)

I 10:52:03 -> Drive 2 - Info: HL-DT-ST BD-RE BP06LU10 HL03-07 (F:) (USB)

I 10:52:03 Found 1 DVD±RW/RAM and 1 BD-RE!

W 10:54:12 User accepted disc space warning and is attempting to overburn!

I 10:54:12 Operation Started!

I 10:54:12 Source File: D:\CASINO_ROYAL.ISO

I 10:54:12 Source File Sectors: 19,900,800 (MODE1/2048)

I 10:54:12 Source File Size: 40,756,838,400 bytes

I 10:54:12 Source File Volume Identifier: CASINO_ROYAL

I 10:54:12 Source File Volume Set Identifier: 8CAE09773B9F39A2_VOLUME_SET_ID

I 10:54:12 Source File Application Identifier: APPLICATION_ID

I 10:54:12 Source File Implementation Identifier: IMPLEMENTATION_ID

I 10:54:12 Source File File System(s): UDF (2.50)

I 10:54:12 Destination Device: [0:0:0] HL-DT-ST BD-RE BP06LU10 HL03 (F:) (USB)

I 10:54:12 Destination Media Type: BD-R (Disc ID: CMCMAG-BA5-000)

I 10:54:12 Destination Media Supported Write Speeds: 2x, 4x, 6x

I 10:54:12 Destination Media Sectors: 12,219,392

I 10:54:12 Write Mode: BD

I 10:54:12 Write Type: DAO

I 10:54:12 Write Speed: 4x

I 10:54:12 Hardware Defect Management Active: No

I 10:54:12 BD-R Verify Not Required: Yes

I 10:54:12 Link Size: Auto

I 10:54:12 Lock Volume: Yes

I 10:54:12 Test Mode: No

I 10:54:12 OPC: No

I 10:54:12 BURN-Proof: Enabled

I 10:54:12 Write Speed Successfully Set! - Effective: 17,982 KB/s (4x)

I 10:54:13 Filling Buffer... (80 MB)

I 10:54:14 Writing LeadIn...

I 10:54:35 Writing Session 1 of 1... (1 Track, LBA: 0 - 19900799)

I 10:54:35 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 19900799)

W 11:22:40 Failed to Write Sectors 12219392 - 12219423 - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (1 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (2 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (3 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (4 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (5 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (6 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (7 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (8 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (9 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (10 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (11 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (12 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (13 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (14 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (15 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (16 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (17 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (18 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (19 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

W 11:22:40 Retrying (20 of 20)...

W 11:22:40 Retry Failed - Reason: Logical Block Address out of Range

E 11:31:28 Failed to Write Sectors 12219392 - 12219423 - Reason: Logical Block Address out of Range

I 11:31:28 Synchronising Cache...

W 11:34:05 User opted to skip the 'Close Track/Session/Disc' functions.

E 11:34:05 Failed to Write Image!

I 11:34:05 Exporting Graph Data...

I 11:34:05 Graph Data File: C:\Users\Sidney\AppData\Roaming\ImgBurn\Graph Data Files\HL-DT-ST_BD-RE_BP06LU10_HL03_MONDAY-APRIL-30-2012_10-54_AM_CMCMAG-BA5-000_4x.ibg

I 11:34:05 Export Successfully Completed!

E 11:34:05 Operation Failed! - Duration: 00:39:53

I 11:34:05 Average Write Rate: 11,043 KB/s (2.5x) - Maximum Write Rate: 18,146 KB/s (4.0x)

 

Much appreciated.

Posted

When the program warns you something won't fit, don't ignore it :)

 

W 10:54:12 User accepted disc space warning and is attempting to overburn!

 

You'll need a double layer disc for that image.

Posted

Hi Lightning:

 

So I burn another DVD of the same ISO file, this time selected Truncate. The burning was successful, however, when play on a Bluray DVD player(Play Station 3), Only about 10 seconds of material is shown - the "Sony Picture" title clip. Then the screen turns black, although the play light on the Sony seems flashing. I wait for 3 minutes and give up. Unfortunately I close Imgburn before I saved the log file because it said the burning was successful. I must point out that I've watched BD movies on the PS3 for over a year without issues. What do you think?

Posted

It's like I said, you need a double layer disc for that image.

 

There's about 15GB of data too much for your single layer (25GB) discs.

 

You can't really expect a disc to work properly when over 1/3rd of it is missing.

Posted

So what is truncate and overburn in Imgburn for? Seems like it's a waste of time when it asks you to choose a solution instead of saying not enough disk space.

Posted
Seems like it's a waste of time when it asks you to choose a solution instead of saying not enough disk space.

 

If you actually read the first line in the window that pops up, that's exactly what it says!

 

So what is truncate and overburn in Imgburn for?

 

Overburn burns as much as it can from the image until the drive errors out (if it errors out) - so anything after that point will be missing from the disc.

 

Truncate burns as much of the image as will fit on the disc and then stops dead - so anything after that point will be missing from the disc.

 

You aren't the only person in the world and you're only looking at it from your point of view. It's designed to allow for every possible situation - for both newbies and experienced users. Just because you can't see a point to something doesn't mean someone else might not find it invaluable.

Posted

Well don't worry. I've uninstalled it anyways because there are many other softwares that are more user-friendly and their forums do not have condescending attitute. Have a good day.

Posted

The fact of the matter is, it tells you that what you're burning doesn't fit on the disc.

 

I told you the same thing in my original post and told you exactly what you needed to do - i.e. burn that image to a double layer disc (instead of the single layer one you were trying to use).

 

That should have been the end of the thread. Instead, you got it in your head to try truncating and then wondered why the disc still didn't work properly. If truncating was going to solve the problem I'd have said so in my initial reply.

 

So you basically came on here with prejudice and blame for your failures firmly placed upon ImgBurn, only to then be told (eventually in a condescending tone - you're welcome) that you are (or at least your lack of understanding and inability to listen to advice already provided is) the problem.

 

I wish you every success with whatever app you choose next.

×
×
  • Create New...

Important Information

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