Jump to content
Sign in to follow this  
rgrele

Problem Doing Full Capacity Format (WAS: ImgBurn Formatted BD50-RE into a BD25-RE)

Recommended Posts

Just FMI (for my information!), can you post the disc info from that newly formatted BD25 please?

 

Certainly.:

 

HL-DT-ST BD-RE GGW-H20L YL05 (ATA)

Current Profile: BD-RE

 

Disc Information:

Status: Complete

Erasable: Yes

Sessions: 1

Sectors: 12,219,392

Size: 25,025,314,816 bytes

Time: 2715:27:17 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 12219392)

 

BD Disc Information:

Disc ID: RITEK-BW1-01

Disc Type: BD-RE

 

Format Capacities:

DT: 0x02 - NB: 12219392 (0x00BA7400) - TDP: 0

FT: 0x00 - NB: 11826176 (0x00B47400) - TDP: 12288

FT: 0x30 - NB: 11826176 (0x00B47400) - TDP: 12288

FT: 0x30 - NB: 11564032 (0x00B07400) - TDP: 20480

FT: 0x30 - NB: 12088320 (0x00B87400) - TDP: 4096

FT: 0x31 - NB: 12219392 (0x00BA7400) - TDP: 2048

 

 

This is the info from the status box after it was formatted and then burned. It is a Memorex branded disc. I've already written to it once before (using the older version 2.4.2.0 with the preferred format capacity), so it's still fairly new. I still haven't had time to watch the disc, or do the rip test. Maybe later tonight. Also, I need to try full formatting one of the Sony BD50-RE's on the suspect burner.

 

If you also want to see the ImgBurn log info, I can post that later as well.

 

Updated 1:25am EST: The above disc was ripped successfully to my HD on another PC/burner. No errors.

 

So far, so good.

 

The suspect burner is currently doing a full erase/format (full capacity) on a previously burned (preferred formatted) Sony BD50-RE. I'll post the details (status box info, before and after) when it is complete.

Edited by rgrele

Share this post


Link to post
Share on other sites

O.K. I just successfully completed a full format/burn on the suspect burner with a SONY BD50-RE.

 

Here is the before and after status box info:

 

BEFORE:

 

HL-DT-ST BD-RE GGW-H20L YL05 (ATA)

Current Profile: BD-RE

 

Disc Information:

Status: Complete

Erasable: Yes

Sessions: 1

Sectors: 23,652,352

Size: 48,440,016,896 bytes

Time: 5256:06:52 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 23652352)

 

BD Disc Information:

Disc ID: MEI-T01-01

Disc Type: BD-RE

 

Format Capacities:

DT: 0x02 - NB: 23652352 (0x0168E800) - TDP: 24576

FT: 0x00 - NB: 23652352 (0x0168E800) - TDP: 24576

FT: 0x30 - NB: 23652352 (0x0168E800) - TDP: 24576

FT: 0x30 - NB: 23259136 (0x0162E800) - TDP: 36864

FT: 0x30 - NB: 24307712 (0x0172E800) - TDP: 4096

FT: 0x31 - NB: 24438784 (0x0174E800) - TDP: 2048

 

AFTER:

 

HL-DT-ST BD-RE GGW-H20L YL05 (ATA)

Current Profile: BD-RE

 

Disc Information:

Status: Complete

Erasable: Yes

Sessions: 1

Sectors: 24,438,784

Size: 50,050,629,632 bytes

Time: 5430:52:34 (MM:SS:FF)

 

TOC Information:

Session 1... (LBA: 0)

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

-> LeadOut (LBA: 24438784)

 

BD Disc Information:

Disc ID: MEI-T01-01

Disc Type: BD-RE

 

Format Capacities:

DT: 0x02 - NB: 24438784 (0x0174E800) - TDP: 0

FT: 0x00 - NB: 23652352 (0x0168E800) - TDP: 24576

FT: 0x30 - NB: 23652352 (0x0168E800) - TDP: 24576

FT: 0x30 - NB: 23259136 (0x0162E800) - TDP: 36864

FT: 0x30 - NB: 24307712 (0x0172E800) - TDP: 4096

FT: 0x31 - NB: 24438784 (0x0174E800) - TDP: 2048

 

 

And here is the ImgBurn log:

 

I 00:37:44 ImgBurn Version 2.4.3.0 started!

I 00:37:44 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 00:37:44 Total Physical Memory: 2,096,492 KB - Available: 1,666,064 KB

I 00:37:44 Initialising SPTI...

I 00:37:44 Searching for SCSI / ATAPI devices...

I 00:37:46 Found 1 DVD-ROM, 1 DVD

Share this post


Link to post
Share on other sites

Ah, the % will be present when ImgBurn is writing zeroes to the sectors.... but not when the drive is actually performing the format/erase and certifying the media (this is an internal process).

 

The whole thing will be much clearer in 2.4.4.0 :)

 

The thing with 2.4.3.0 is that when immediate I/O is disabled and the format command fails, you don't know about it.

 

By default 2.4.3.0 will attempt to format with full certification first, if that fails then it'll attempt to do it quickly without any certification.

 

So what might actually be happening for you is that the format command fails will full certification (as it does when immediate i/o is enabled - and this is what SHOULD be happening or there's a bug in the drives firmware!) and then the quick one succeeds - thus you end up with an erase operation that seems to have completed without error.

Share this post


Link to post
Share on other sites
Ah, the % will be present when ImgBurn is writing zeroes to the sectors.... but not when the drive is actually performing the format/erase and certifying the media (this is an internal process).

 

The whole thing will be much clearer in 2.4.4.0 :)

 

The thing with 2.4.3.0 is that when immediate I/O is disabled and the format command fails, you don't know about it.

 

By default 2.4.3.0 will attempt to format with full certification first, if that fails then it'll attempt to do it quickly without any certification.

 

So what might actually be happening for you is that the format command fails will full certification (as it does when immediate i/o is enabled - and this is what SHOULD be happening or there's a bug in the drives firmware!) and then the quick one succeeds - thus you end up with an erase operation that seems to have completed without error.

 

This must be what just happened with one of the lesser quality LG BD25-RE's (included with the burner.)

 

I used the full format command on a brand new one last night on the downstairs burner (the one that I assume is the better of the 2.) Anyway, It gave me the same format error warning as before, (the I/O box was left checked in this instance.) The format eventually completed, and the disc burned and verified successfully.

 

I assumed all was well. Then I played it back from the beginning. Within less than a minute, the audio started to exhibit glitches (drop outs.) The disc would continue to play, but it was obvious that there was something wrong (at least with this section of the disc.) I tried it on my PS3 just to be sure, and the drop outs were in the same place. This surprised me, as the disc supposedly passed the verification process.

 

So, as a test, I'm starting the process over with the same disc, except this time I'm trying a "preferred format" full erase mode instead of the full capacity format. I'm not sure if that will produce different results, but as I said in my first post, these errors only started to occur when I chose to erase my discs using the full capacity format mode.

 

Apparently, some discs do not react well when the full capacity format is used. :(

Share this post


Link to post
Share on other sites

Verify only tells you that it can be read in that drive, not that it'll work in anything else.

 

Every drive has different capabilities when it comes to reading and a computer BD drive is more likely to read BDRE media than a PS3 which is probably geared more towards reading pressed BDROM's.

 

The whole thing about leaving the spare areas enabled is that if a sector on the disc is found to be a bit dodgy, it can be mapped out of use. When you use the entire disc (no spare areas), that can't happen and your bad sector becomes 'available' for use again, even if it's not readable/writable.

Share this post


Link to post
Share on other sites
Verify only tells you that it can be read in that drive, not that it'll work in anything else.

 

Every drive has different capabilities when it comes to reading and a computer BD drive is more likely to read BDRE media than a PS3 which is probably geared more towards reading pressed BDROM's.

 

The whole thing about leaving the spare areas enabled is that if a sector on the disc is found to be a bit dodgy, it can be mapped out of use. When you use the entire disc (no spare areas), that can't happen and your bad sector becomes 'available' for use again, even if it's not readable/writable.

 

Well, it looks like the replacement LG branded BD25-RE is toast. This is the one mentioned above that had the drop outs at the beginning (but at least it burned somewhat successfully the first time around.) Used the new 2.4.4.0 ImgBurn and did a minimum capacity format (which failed.) Then tried to burn it anyway just for laughs.

 

The burn log:

 

;

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

; ImgBurn Version 2.4.4.0 - Log

; Saturday, 11 April 2009, 18:25:22

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

;

;

I 18:23:22 ImgBurn Version 2.4.4.0 started!

I 18:23:22 Microsoft Windows XP Media Center Edition (5.1, Build 2600 : Service Pack 3)

I 18:23:22 Total Physical Memory: 2,096,492 KB - Available: 1,647,792 KB

I 18:23:22 Initialising SPTI...

I 18:23:22 Searching for SCSI / ATAPI devices...

E 18:23:22 Failed to check for ImgBurn update!

I 18:23:22 Found 1 DVD-ROM, 1 DVD

Share this post


Link to post
Share on other sites

I've never seen any BD-RE DL from Verbatim and I don't think they mention them on their website. I'm sure they'll bring some out one day though. I've been doing this long enough now to have seen where all the failures come from and therefore what to avoid buying. That's why I stick with Verbatim. :)

 

Not that you really need telling now, but don't waste your time on the LG BD-RE. It's awful and fails in most people's drives! God knows why they supply them with their

Share this post


Link to post
Share on other sites

O_O

 

Man, I'd think that if people pay this much for a drive and media (what's the media, like $30 a disc?), it'd've been tested, refined, tuned, tested, refined, and re-tuned before it even made it to production. How is it possible to have this many problems? =\

 

*stays the hell away from HD formats*...

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.