Jump to content

Problems with BD-r writing


monks19

Recommended Posts

Hi. I'm having some troubles with a BD-r writhing I'm trying to do, but unwortunately, I always get errors like this:

 

I 20:46:39 ImgBurn Version 2.5.8.0 started!
I 20:46:39 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 20:46:39 Total Physical Memory: 16 718 684 KiB  -  Available: 8 060 888 KiB
I 20:46:39 Initialising SPTI...
I 20:46:39 Searching for SCSI / ATAPI devices...
I 20:46:40 -> Drive 1 - Info: ATAPI iHAS424   B GL18 (F:) (SATA)
I 20:46:40 -> Drive 2 - Info: ATAPI iHBS112   2 CL0K (G:) (SATA)
I 20:46:40 -> Drive 3 - Info: DVDFab Virtual Drive 1.1 (I:) (SCSI)
I 20:46:40 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (R:) (SCSI)
I 20:46:40 -> Drive 5 - Info: DVDFab Virtual Drive 1.1 (Q:) (SCSI)
I 20:46:40 Found 1 DVD±RW/RAM, 3 BD-ROM/HD DVD-ROMs and 1 BD-RE!
I 20:46:52 Operation Started!
I 20:46:52 Building Image Tree...
W 20:46:52 Removed Filtered File: \DVDFab.miniso
I 20:46:52 Calculating Totals...
I 20:46:52 Preparing Image...
I 20:46:52 Contents: 54 Files, 15 Folders
I 20:46:52 Content Type: BD Video
I 20:46:53 Data Type: MODE1/2048
I 20:46:53 File System(s): UDF (2.50)
I 20:46:53 Volume Label: [Not Configured]
I 20:46:53 Size: 23 482 230 488 bytes
I 20:46:53 Sectors: 11 465 968
I 20:46:53 Image Size: 23 483 449 344 bytes
I 20:46:53 Image Sectors: 11 466 528
I 20:46:53 Operation Successfully Completed! - Duration: 00:00:00
I 20:50:33 Close Request Acknowledged
I 20:50:33 Closing Down...
I 20:50:33 Shutting down SPTI...
I 20:50:33 ImgBurn closed!
I 20:37:26 ImgBurn Version 2.5.8.0 started!
I 20:37:26 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7601 : Service Pack 1)
I 20:37:26 Total Physical Memory: 16 718 684 KiB  -  Available: 9 362 128 KiB
I 20:37:26 Initialising SPTI...
I 20:37:26 Searching for SCSI / ATAPI devices...
I 20:37:26 -> Drive 1 - Info: ATAPI iHAS424   B GL18 (F:) (SATA)
I 20:37:26 -> Drive 2 - Info: ATAPI iHBS112   2 CL0K (G:) (SATA)
I 20:37:26 -> Drive 3 - Info: DVDFab Virtual Drive 1.1 (I:) (SCSI)
I 20:37:26 -> Drive 4 - Info: DVDFab Virtual Drive 1.1 (R:) (SCSI)
I 20:37:27 -> Drive 5 - Info: DVDFab Virtual Drive 1.1 (Q:) (SCSI)
I 20:37:27 Found 1 DVD±RW/RAM, 3 BD-ROM/HD DVD-ROMs and 1 BD-RE!
I 20:38:48 Operation Started!
I 20:38:48 Building Image Tree...
W 20:38:48 Removed Filtered File: \DVDFab.miniso
I 20:38:48 Calculating Totals...
I 20:38:48 Preparing Image...
I 20:38:48 Contents: 54 Files, 15 Folders
I 20:38:48 Content Type: BD Video
I 20:38:48 Data Type: MODE1/2048
I 20:38:48 File System(s): UDF (2.50)
I 20:38:48 Volume Label: [Not Configured]
I 20:38:48 Size: 23 482 230 488 bytes
I 20:38:48 Sectors: 11 465 968
I 20:38:48 Image Size: 23 483 449 344 bytes
I 20:38:48 Image Sectors: 11 466 528
I 20:38:48 Operation Successfully Completed! - Duration: 00:00:00
I 20:40:29 Operation Started!
I 20:40:29 Building Image Tree...
W 20:40:29 Removed Filtered File: \DVDFab.miniso
E 20:40:57 User did not specify a volume label.
E 20:40:57 Operation Aborted! - Duration: 00:00:27
I 20:41:01 Operation Started!
I 20:41:01 Building Image Tree...
W 20:41:01 Removed Filtered File: \DVDFab.miniso
I 20:41:10 Calculating Totals...
I 20:41:10 Preparing Image...
I 20:41:10 Contents: 54 Files, 15 Folders
I 20:41:10 Content Type: BD Video
I 20:41:10 Data Type: MODE1/2048
I 20:41:10 File System(s): UDF (2.50)
I 20:41:10 Volume Label: [Not Configured]
I 20:41:10 Size: 23 482 230 488 bytes
I 20:41:10 Sectors: 11 465 968
I 20:41:10 Image Size: 23 483 449 344 bytes
I 20:41:10 Image Sectors: 11 466 528
E 20:41:14 Operation Aborted! - Duration: 00:00:12
I 20:41:15 Operation Started!
I 20:41:15 Building Image Tree...
W 20:41:15 Removed Filtered File: \DVDFab.miniso
I 20:41:20 Calculating Totals...
I 20:41:20 Preparing Image...
I 20:41:20 Contents: 54 Files, 15 Folders
I 20:41:20 Content Type: BD Video
I 20:41:20 Data Type: MODE1/2048
I 20:41:20 File System(s): UDF (2.50)
I 20:41:20 Volume Label: [Not Configured]
I 20:41:21 Size: 23 482 230 488 bytes
I 20:41:21 Sectors: 11 465 968
I 20:41:21 Image Size: 23 483 449 344 bytes
I 20:41:21 Image Sectors: 11 466 528
E 20:41:41 Operation Aborted! - Duration: 00:00:26
I 20:41:43 Operation Started!
I 20:41:43 Building Image Tree...
W 20:41:43 Removed Filtered File: \DVDFab.miniso
I 20:41:53 Calculating Totals...
I 20:41:53 Preparing Image...
I 20:41:53 Contents: 54 Files, 15 Folders
I 20:41:53 Content Type: BD Video
I 20:41:53 Data Type: MODE1/2048
I 20:41:53 File System(s): UDF (2.50)
I 20:41:53 Volume Label: PRESTIGE BR 01A
I 20:41:53 Size: 23 482 230 488 bytes
I 20:41:53 Sectors: 11 465 968
I 20:41:53 Image Size: 23 483 449 344 bytes
I 20:41:53 Image Sectors: 11 466 528
I 20:41:57 Operation Successfully Completed! - Duration: 00:00:14
I 20:41:57 Operation Started!
I 20:41:57 Source File: -==/\/[bUILD IMAGE]\/\==-
I 20:41:57 Source File Sectors: 11 466 528 (MODE1/2048)
I 20:41:57 Source File Size: 23 483 449 344 bytes
I 20:41:57 Source File Volume Identifier: PRESTIGE BR 01A
I 20:41:57 Source File Volume Set Identifier: 4B1CA53500AEF690
I 20:41:57 Source File Application Identifier: ImgBurn v2.5.8.0
I 20:41:57 Source File Implementation Identifier: ImgBurn
I 20:41:57 Source File File System(s): UDF (2.50)
I 20:41:57 Destination Device: [0:0:0] ATAPI iHBS112   2 CL0K (G:) (SATA)
I 20:41:57 Destination Media Type: BD-R (Disc ID: MILLEN-MR1-000)
I 20:41:57 Destination Media Supported Write Speeds: 2x
I 20:41:57 Destination Media Sectors: 12 219 392
I 20:41:57 Write Mode: BD
I 20:41:57 Write Type: DAO
I 20:41:57 Write Speed: MAX
I 20:41:57 Hardware Defect Management Active: No
I 20:41:57 BD-R Verify Not Required: Yes
I 20:41:57 Link Size: Auto
I 20:41:57 Lock Volume: Yes
I 20:41:57 Test Mode: No
I 20:41:57 OPC: No
I 20:41:57 BURN-Proof: Enabled
I 20:41:59 Write Speed Successfully Set! - Effective: 8 990 KB/s (2x)
I 20:41:59 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 20:41:59 CD/DVD Life Record Count: 79 - CD/DVD Record Count: 64
I 20:41:59 BD Life Record Count: 9 - BD Record Count: 7
I 20:42:18 Filling Buffer... (80 MiB)
I 20:42:19 Writing LeadIn...
W 20:42:37 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write
W 20:42:37 Retrying (1 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (2 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (3 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (4 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (5 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (6 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (7 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (8 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (9 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (10 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (11 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (12 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (13 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (14 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (15 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (16 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (17 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (18 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (19 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
W 20:42:37 Retrying (20 of 20)...
W 20:42:37 Retry Failed - Reason: Invalid Address For Write
E 20:43:58 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write
E 20:43:58 Next Writable Address: 0
I 20:43:58 Synchronising Cache...
W 20:44:37 User opted to skip the 'Close Track/Session/Disc' functions.
E 20:44:37 Failed to Write Image!
E 20:44:37 Operation Failed! - Duration: 00:02:39
I 20:44:37 Average Write Rate: 0 KiB/s (0.0x) - Maximum Write Rate: 0 KiB/s (0.0x)
I 20:46:36 Close Request Acknowledged
I 20:46:36 Closing Down...
I 20:46:36 Shutting down SPTI...
I 20:46:36 ImgBurn closed!
 

I tried a few times with other softwares, but no success. I don't know if its either the disc or the burner that's causing this.

 

Can anybody please help me ?

 

Thanks to answer

Link to comment
Share on other sites

Yes, I was going to suggest the same thing.  That drive probably didn't support M-Disc.  A similar post happened a few weeks/months ago and that seemed to be the problem.

 

 

BTW, what does this entry in that log mean: W 20:46:52 Removed Filtered File: \DVDFab.miniso

 

 

What's a filtered file and why would it be removed?

 

 

I don't think I've ever seen such a log entry ever before.

Link to comment
Share on other sites

Yes, I was going to suggest the same thing.  That drive probably didn't support M-Disc.  A similar post happened a few weeks/months ago and that seemed to be the problem.

 

 

BTW, what does this entry in that log mean: W 20:46:52 Removed Filtered File: \DVDFab.miniso

 

 

What's a filtered file and why would it be removed?

 

 

I don't think I've ever seen such a log entry ever before.

 

What are M-Discs and which discs should I use in order to work this mess, please ?

 

Mini-iso are image files emulators done by DVDFab when you convert iso file to files only format or rip a disc (BD & DVD) to PC in file format.

Link to comment
Share on other sites

M-Disc are a special "flavor" of discs.  For DVD's, they're a variant of the DVD+R format.  If you have a DVD player/drive that supports DVD+R, and most modern ones should, you will have no compatibility problems with M-Disc.

 

 

M-Disc is a special kind of disc designed for long term archival purposes.  It's basically the difference between writing in ink on paper and chiseling words into stone tablets.  The stone tablets won't decay as quickly as the ink on paper.  It's basically the laser burning pits into "stone."  For non M-Disc DVD, there's organic dye, which decays much quicker than an M-Disc would.

 

 

The drawback is your burner must support M-Disc, as you've encountered.  Pioneer's 2209 BD and LG's WH series drives do.

 

 

Basically, if it doesn't say M-Disc on the package, that's what you're after, unless your burner supports M-Disc.  M-Disc also cost more, but they do last much longer so the price can be worth the trade off. 

 

 

Any DVD-/+R/DL media will "do," however, there are a lot of cheap manufacturers out there, like CMC.  And Memorex will farm out to them.  As will Verbatim IF you buy the Life series sold online and in brick and mortar stores.  What you'll want to get are Verbatim DataLife Plus series DVD-R/DVD+R/DVD-R DL/DVD+R DL, depending on the size you need, compatibility (For instance, DVD+R DL is more compatible with DVD players than DVD-R DL.), and what you're willing to pay for the quality you get.  However, you can generally only find those online like where I get them at Amazon.com.

 

 

Now, some drives simply don't like certain kinds of manufacturers' media.  So, it really is a bit of trial and error before you find what works best for you.  I just recommend the best quality stuff out there because most people generally don't have problems with Verbatim MKM (DataLife Plus) series media.

 

 

I was relatively sure the miniISO file was some kind of emulation file, but why is ImgBurn excluding it?  What if you really NEED to backup that file?

Link to comment
Share on other sites

Thanks. I'll go get that disc now and see if I can get a new burner soon. The pioneer one is more interesting than the LG (not reliable based on past experiences).

 

Incidently, do you know any database on BD writers that can handle m-discs (aside the two you mentioned) ? I can't find any that seems reliable.

 

Thanks to answer

Edited by monks19
Link to comment
Share on other sites

There's no need to get a new burner unless you really want to use those M-Discs.  It's probably cheaper just to get new discs.  But, if you want to use M-Disc, by all means get an M-Disc capable burner.

 

 

I actually have both a Pioneer 2209 and an LG one.  The last released firmware for the 2209 borked writing to Ritek 8x DVD+RW's.  They always fail Verify.  The 2nd to most recent firmware doesn't do this.  Plus, the last 2209 I got was borked right out of the box.  Wouldn't write BD-R properly.  Had to go back.  And there's the Eject button problem with Pioneer's.  After about 7 months, the Eject button won't work the first time you press it 1 in 10 times.  Eject commands issued by ImgBurn manually won't work either.  If you press the button/issue the command a 2nd time, it works.  And ImgBurn's automatic eject command after an operation seems to always work, though.

 

 

The only reason I still have an LG is because it does write to 8x Ritek DVD+RW properly.  However, it has its own set of pretty lengthy problems.  LG's are terrible reading drives.  And the LG DL BD drives don't properly write to BD-RE DL, even quality media.  They will usually fail Verifies or the data is not written correctly to them, resulting in corruption.  Plus, the writing BD-RE SL as a giant floppy in Windows Explorer only caps out at 1x instead of the maximum 2x that the 2209 and my ASUS USB will achieve.

Link to comment
Share on other sites

Hi guys. After last time results, I've bought a set of 5 verbatim BD-r discs. The same problem seems to keep going:

 

I 18:17:41 Operation Started!
I 18:17:41 Source File: P:\SDM 02\Prestige 2017\Montage\PRESTIGE BR 01.iso
I 18:17:41 Source File Sectors: 11 467 072 (MODE1/2048)
I 18:17:41 Source File Size: 23 484 563 456 bytes
I 18:17:41 Source File Volume Identifier: VOLUME_01
I 18:17:41 Source File Volume Set Identifier: AAAABBBBCCCCDDDDEEEEFFFF
I 18:17:41 Source File Application Identifier: Disque Blu-ray Vegas
I 18:17:41 Source File Implementation Identifier: 0
I 18:17:41 Source File File System(s): UDF (2.50)
I 18:17:41 Destination Device: [2:0:0] ATAPI iHBS112   2 CL0K (G:) (SATA)
I 18:17:41 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000)
I 18:17:41 Destination Media Supported Write Speeds: 4x; 6x
I 18:17:41 Destination Media Sectors: 12 219 392
I 18:17:41 Write Mode: BD
I 18:17:41 Write Type: DAO
I 18:17:41 Write Speed: MAX
I 18:17:41 Hardware Defect Management Active: No
I 18:17:41 BD-R Verify Not Required: Yes
I 18:17:41 Link Size: Auto
I 18:17:41 Lock Volume: Yes
I 18:17:41 Test Mode: No
I 18:17:41 OPC: No
I 18:17:41 BURN-Proof: Enabled
I 18:17:43 Write Speed Successfully Set! - Effective: 26 970 KB/s (6x)
I 18:17:43 Advanced Settings - Force HT: No, Online HT: No, OverSpeed: No, SmartBurn: Yes
I 18:17:43 CD/DVD Life Record Count: 95 - CD/DVD Record Count: 64
I 18:17:43 BD Life Record Count: 11 - BD Record Count: 9
I 18:18:13 Filling Buffer... (80 MiB)
I 18:18:15 Writing LeadIn...
W 18:18:55 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write
W 18:18:55 Retrying (1 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (2 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (3 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (4 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (5 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (6 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (7 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (8 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (9 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (10 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (11 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (12 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (13 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (14 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (15 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (16 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (17 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (18 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (19 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
W 18:18:56 Retrying (20 of 20)...
W 18:18:56 Retry Failed - Reason: Invalid Address For Write
E 18:19:10 Failed to Write Sectors 2816 - 2847 - Reason: Invalid Address For Write
E 18:19:10 Next Writable Address: 0
I 18:19:10 Synchronising Cache...
W 18:19:32 Synchronise Cache Failed! - Reason: Timeout on Logical Unit
E 18:19:37 Synchronise Cache Failed! - Reason: Timeout on Logical Unit
W 18:19:41 User opted to skip the 'Close Track/Session/Disc' functions.
E 18:19:41 Failed to Write Image!
E 18:19:43 Operation Failed! - Duration: 00:01:59
I 18:19:43 Average Write Rate: 0 KiB/s (0.0x) - Maximum Write Rate: 0 KiB/s (0.0x)
I 18:19:56 Close Request Acknowledged
I 18:19:56 Closing Down...
I 18:19:56 Shutting down SPTI...
I 18:19:56 ImgBurn closed!
 

 

Any idea on how to make this finaly work ?

 

Thanks to answer

Edited by monks19
Link to comment
Share on other sites

Could be because, as near as I can tell, your drive is a LiteOn Blu-Ray burner.  I had a LiteOn as my first BD burner and it died after 3 months.  And LiteOn, I don't think, makes burners of any kind anymore.  So, their BD seemed to be junk to begin with.  Just my opinion.  I wouldn't know more unless you tried the latest Pioneer or LG BD drive, which I use.  Though I recommend starting with the Pioneer 2209 before the 209 or the LG series burners.  I know more about the 2209 than the LG burners, which I only use for one purpose.  I've never used a Pioneer 209.  However, the 2209 supports the M-Disc discs you had so you can use them with that.

Link to comment
Share on other sites

I believe I had the same drive also in 2012.  It stopped writing BD-RE after 3 months.  The real killer was 3 DVD+R DL VIDEO_TS I burned with it.  2 of the discs had random pauses added to playback that weren't layer breaks.  However, this was a common problem that plagued LiteOn DVD burners.  It would randomly add pauses to the beginning of some video playback that weren't layer breaks.  It was more random on the DVD burners, but 2 out of 3 DVD+R DL's on the BD burner from LiteOn did this.  This swore me off of LiteOn drives altogether, even DVD burners as the DVD problem was present for years.  Now, it's a moot point as LiteOn stopped making BD drives shortly after I got one from them and now apparently no longer makes any optical burners.

Link to comment
Share on other sites

Maybe an updated firmware would solve the issue?

 

http://www.firmwarehq.com/Lite-On/iHBS112%2B2/files.html

 

You could also try burning at 4x instead of MAX.

 

The error your drive is returning shouldn't really be the first error you get. I might expect 'invalid address for write' after another issue (maybe a 'write error'), but it isn't normally the first and only error. Weird.

Link to comment
Share on other sites

×
×
  • Create New...

Important Information

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