ace741 Posted December 17, 2009 Posted December 17, 2009 I have a Lite-On DH-4B1S BD Writer. I have 3 25GB ISO's I've downloaded from newsgroups. When I try to burn them to a 25GB BD-R, ImgBurn tells me there doesn't appear to be enough space on the disc to burn this image. I've done research on the web, including the source site who posted the ISOs and no one is having this issue but me. I've tried 3 different Brand BD-Rs thinking some have more capacity than others, but so far been proven wrong. I've tried Verbatim, Maxell, and Memorex. My drive came with a TDK BD-RE and surprisingly the ISOs fit on the BD-RE. When I click on Verify disc in ImgBurn, here is the free space I get on the different discs Memorex BD-R - Free Space 24,220,008,448 bytes Verbatim BD-R - Free Space 24,220,008,448 bytes TDK BD-RE - Size 25,025,314,816 bytes Sample ISO size - 24,645,337,008 bytes From the research I've been doing, I was inclined to believe an ISO would fit properly on a BD-R before it would on a BD-RE. I've tried attaching my drive to another computer to see if it had something to do with mine and I get the same results. I realize the size discrepencies could be related to the defect management systems. For whatever reason, am I not getting the most capacity out of my BD-Rs ? Are there any settings I can change to get more capacity out of my BD-Rs? Any help would be great appreciated cause this problem is driving me nuts!
mmalves Posted December 17, 2009 Posted December 17, 2009 With ImgBurn in Write mode, could you please copy and paste here the disc information text from those blanks?
ace741 Posted December 17, 2009 Author Posted December 17, 2009 With ImgBurn in Write mode, could you please copy and paste here the disc information text from those blanks? Thanks for your reply. As requested.. I 15:07:56 ImgBurn Version 2.5.0.0 started! I 15:07:56 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 15:07:56 Total Physical Memory: 1,038,320 KB - Available: 569,208 KB I 15:07:56 Initialising SPTI... I 15:07:56 Searching for SCSI / ATAPI devices... I 15:07:56 Found 1 BD-RE! W 15:08:19 User accepted disc space warning and is attempting to overburn! I 15:08:20 Operation Started! I 15:08:20 Source File: C:\NoCountryForOldMenBD25.iso I 15:08:20 Source File Sectors: 12,033,856 (MODE1/2048) I 15:08:20 Source File Size: 24,645,337,088 bytes I 15:08:20 Source File Volume Identifier: NoCountryForOldMenBD25 I 15:08:20 Source File Volume Set Identifier: 3B8F935000B79ED7 I 15:08:20 Source File Application Identifier: ImgBurn v2.5.0.0 I 15:08:20 Source File Implementation Identifier: ImgBurn I 15:08:20 Source File File System(s): UDF (2.50) I 15:08:20 Destination Device: [1:0:0] ATAPI BD B DH4B1S 7P5B (D:) (ATA) I 15:08:20 Destination Media Type: BD-R (Disc ID: RITEK-BR2-00) (Speeds: 2x, 4x) I 15:08:20 Destination Media Sectors: 11,826,176 I 15:08:20 Write Mode: BD I 15:08:20 Write Type: DAO I 15:08:20 Write Speed: MAX I 15:08:20 BD-R Verify Not Required: Yes I 15:08:20 Link Size: Auto I 15:08:20 Lock Volume: Yes I 15:08:20 Test Mode: Yes I 15:08:20 OPC: No I 15:08:20 BURN-Proof: Enabled I 15:08:35 Filling Buffer... (40 MB) I 15:08:36 Writing LeadIn... I 15:08:43 Writing Session 1 of 1... (1 Track, LBA: 0 - 12033855) I 15:08:43 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 12033855) W 15:33:17 Failed to Write Sectors 11826176 - 11826207 - Reason: Logical Block Address out of Range W 15:33:17 Retrying (1 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (2 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (3 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (4 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (5 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (6 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (7 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (8 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (9 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (10 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (11 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (12 of 20)... W 15:33:17 Retry Failed - Reason: Logical Block Address out of Range W 15:33:17 Retrying (13 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (14 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (15 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (16 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (17 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (18 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (19 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:33:18 Retrying (20 of 20)... W 15:33:18 Retry Failed - Reason: Logical Block Address out of Range W 15:40:26 Retrying (21)... W 15:40:26 Retry Failed - Reason: Logical Block Address out of Range W 15:40:27 Retrying (22)... W 15:40:27 Retry Failed - Reason: Logical Block Address out of Range W 15:40:29 Retrying (23)... W 15:40:29 Retry Failed - Reason: Logical Block Address out of Range W 15:40:30 Retrying (24)... W 15:40:30 Retry Failed - Reason: Logical Block Address out of Range W 15:40:30 Retrying (25)... W 15:40:31 Retry Failed - Reason: Logical Block Address out of Range W 15:40:31 Retrying (26)... W 15:40:31 Retry Failed - Reason: Logical Block Address out of Range W 15:40:31 Retrying (27)... W 15:40:31 Retry Failed - Reason: Logical Block Address out of Range W 15:40:31 Retrying (28)... W 15:40:31 Retry Failed - Reason: Logical Block Address out of Range W 15:40:32 Retrying (29)... W 15:40:32 Retry Failed - Reason: Logical Block Address out of Range W 15:40:33 Retrying (30)... W 15:40:33 Retry Failed - Reason: Logical Block Address out of Range W 15:40:33 Retrying (31)... W 15:40:33 Retry Failed - Reason: Logical Block Address out of Range W 15:40:33 Retrying (32)... W 15:40:33 Retry Failed - Reason: Logical Block Address out of Range W 15:40:34 Retrying (33)... W 15:40:34 Retry Failed - Reason: Logical Block Address out of Range W 15:40:34 Retrying (34)... W 15:40:34 Retry Failed - Reason: Logical Block Address out of Range E 15:40:35 Failed to Write Sectors 11826176 - 11826207 - Reason: Logical Block Address out of Range I 15:40:35 Synchronising Cache... I 15:40:39 Closing Track... I 15:40:44 Finalising Disc... I 15:41:07 Cycling Tray after Test Write... E 15:41:12 Failed to Write Image! I 15:41:13 Exporting Graph Data... I 15:41:13 Graph Data File: C:\Users\Eheahkel\AppData\Roaming\ImgBurn\Graph Data Files\ATAPI_BD_B_DH4B1S_7P5B_THURSDAY-DECEMBER-17-2009_3-08_PM_RITEK-BR2-00_MAX.ibg I 15:41:13 Export Successfully Completed! E 15:41:13 Operation Failed! - Duration: 00:32:51 I 15:41:13 Average Write Rate: 12,376 KB/s (2.8x) - Maximum Write Rate: 18,011 KB/s (4.0x)
LIGHTNING UK! Posted December 17, 2009 Posted December 17, 2009 Disc information is in the panel on the right when you're on the main screen (the 'Write' mode screen that is).
ace741 Posted December 17, 2009 Author Posted December 17, 2009 Disc information is in the panel on the right when you're on the main screen (the 'Write' mode screen that is). Yes thanks. My question is shouldn't a BD-R have 25,025,314,816 bytes available of free space? Just like the BD-RE I have? I'm guessing most everyone else is getting 25,025,314,816 bytes of free space but me, and I have no idea why.
LIGHTNING UK! Posted December 17, 2009 Posted December 17, 2009 lol no, I meant that is what you need to be posting, not the info from the log file (although that's useful too). You do seem to be running a little low on free sectors (and hence free bytes) though, yes.
ace741 Posted December 18, 2009 Author Posted December 18, 2009 As requested.. ATAPI BD B DH4B1S 7P5B (RAID) Current Profile: BD-R Disc Information: Status: Empty Erasable: No Free Sectors: 11,826,176 Free Space: 24,220,008,448 bytes Free Time: 2628:04:26 (MM:SS:FF) Supported Write Speeds: 2x, 4x BD Disc Information: Disc ID: VERBAT-IMc-00 Disc Type: BD-R Performance (Write Speed): Descriptor 1... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 7,578 KB/s (1.7x) - WS: 8,991 KB/s (2x) Descriptor 2... -> B0: 0x00, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 7,578 KB/s (1.7x) - WS: 17,983 KB/s (4x) I have made some progress. I went out and bought an LG Bluray Burner (I intend to return cause I can't afford another burner right now), installed it, and on the same BD-R it shows the following.. HL-DT-ST BD-RE BH08LS20 2.00 (RAID) Current Profile: BD-R Disc Information: Status: Empty Erasable: No Free Sectors: 12,219,392 Free Space: 25,025,314,816 bytes Free Time: 2715:27:17 (MM:SS:FF) Supported Write Speeds: 2x, 4x, 6x, 8x BD Disc Information: Disc ID: VERBAT-IMc-00 Disc Type: BD-R Performance (Write Speed): Descriptor 1... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 14,881 KB/s (3.4x) - WS: 8,991 KB/s (2x) Descriptor 2... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 14,881 KB/s (3.4x) - WS: 17,982 KB/s (4x) Descriptor 3... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) -> RS: 14,881 KB/s (3.4x) - WS: 26,973 KB/s (6x) Descriptor 4... -> B0: 0x02, B1: 0x00, B2: 0x00, B3: 0x00 -> EL: 12219391 (0x00BA73FF) So it looks like its a problem with my Lite-On Burner. Any settings in ImgBurn I can tweak to perhaps fix this issue? Thanks again for your help!
LIGHTNING UK! Posted December 18, 2009 Posted December 18, 2009 No, this is a drive issue (or drive firmware to be exact).
ace741 Posted December 18, 2009 Author Posted December 18, 2009 This is last lite-on I will be buying. Thanks again for your help. Great job on the program BTW!
Recommended Posts