toshik Posted March 21, 2010 Posted March 21, 2010 (edited) Here's what I've got: - Win7 Ultimate x64 - ImageBurn 2510 - AnyDVD 6630 - new external Pioneer BDR-205 BD DL burner on eSATA port - new HP Pavilion DV7 Quad laptop computer with full support of its internal BD player drive and nothing running in the background! I tried to burn the 41 GB DL disk onto Verbatim BD-R DL 50 GB disk. In addition to being marked on the disk, Windows report 50 Gb capacity of the empty disk in the drive. It went 7% through and got stock forever (well, for one hour) doing nothing... The log is below with 3 problematic lines in bold. I burned a 25 GB SL BD-R before with no problem. I think what's wrong is that for some reason ImagBurn thinks that BDR-205 is only SL BD burner! The reasons to assume this are: - I had no problem burning the SL BD 25 GB disk - the log says "Destination Media Sectors: 24,438,784", even though it had Verbatim BD-R 50GB disk in drive (it's now garbage!) - the info page in ImgBurn for some reason reports BDR-205 as only SL BD-R reader/writer - this is WRONG! According to all sources including Pioneer Web Page Read/Write support: BD-R, BD-R DL, BD-RE, BD-RE DL Also the media is marked 1-2x speed - maybe I need to burn at 1x (not at MAX)? Can't afford more coasters :-( Could we please get this all fixed? Here is the log: I 21:56:13 ImgBurn Version 2.5.1.0 started! I 21:56:13 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 21:56:13 Total Physical Memory: 4,184,956 KB - Available: 2,890,728 KB W 21:56:13 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 21:56:13 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 21:56:13 Initialising SPTI... I 21:56:13 Searching for SCSI / ATAPI devices... I 21:56:13 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (SATA) I 21:56:13 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.04 (F:) (SATA) I 21:56:13 -> Drive 3 - Info: WFQBCX 0XU7KH6RWX 1.03 (E:) (SCSI) I 21:56:13 Found 1 BD-ROM/HD DVD-ROM, 1 BD-ROM/DVD±RW and 1 BD-RE! I 21:56:42 Operation Started! I 21:56:42 Source File: C:\Temp\Blu-Ray\__.ISO I 21:56:42 Source File Sectors: 20,123,680 (MODE1/2048) I 21:56:42 Source File Size: 41,213,296,640 bytes I 21:56:42 Source File Volume Identifier: ___________________ I 21:56:42 Source File Volume Set Identifier: ______________________ I 21:56:42 Source File Application Identifier: ImgBurn v2.5.0.0 I 21:56:42 Source File Implementation Identifier: ImgBurn I 21:56:42 Source File File System(s): UDF (2.50) I 21:56:42 Destination Device: [3:0:0] PIONEER BD-RW BDR-205 1.04 (F:) (SATA) I 21:56:42 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) I 21:56:42 Destination Media Sectors: 24,438,784 I 21:56:42 Write Mode: BD I 21:56:42 Write Type: DAO I 21:56:42 Write Speed: MAX I 21:56:42 BD-R Verify Not Required: Yes I 21:56:42 Link Size: Auto I 21:56:42 Lock Volume: Yes I 21:56:42 Test Mode: No I 21:56:42 OPC: No I 21:56:42 BURN-Proof: Enabled I 21:56:42 Write Speed Successfully Set! - Effective: 8,990 KB/s (2x) I 21:56:42 Advanced Settings - Optimal Writing Speed: No I 21:56:43 Filling Buffer... (40 MB) I 21:56:44 Writing LeadIn... I 21:57:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 20123679) I 21:57:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 20123679) Edited March 23, 2010 by toshik
mmalves Posted March 21, 2010 Posted March 21, 2010 Was the drive still spinning/LED blinking when it stalled burning? Were you able to close ImgBurn or did it stay in memory? First thing I'd do is look for the latest drivers for your motherboard's chipset and/or SATA controllers (you can use SIW to identify them).
LIGHTNING UK! Posted March 21, 2010 Posted March 21, 2010 I 21:56:42 Destination Media Sectors: 24,438,784 That is correct for a DL disc. A sector is 2048 bytes. So Size = 24,438,784 * 2048 = 50,050,629,632 bytes, and that's where your 50GB comes from. the info page in ImgBurn for some reason reports BDR-205 as only SL BD-R reader/writer - this is WRONG! This is purely cosmetic and makes no difference within the program. I haven't found a flag in any of the drive feature/profile pages that says a drive can support BD-R DL, so that's why the box isn't checked. It's just there for completeness, I could just as easily remove it... in fact, I just have so as to avoid future confusion. Also the media is marked 1-2x speed - maybe I need to burn at 1x (not at MAX)?. . . I 21:56:42 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) The firmware in your drive only supports it at 2x. I have no control over that.
toshik Posted March 21, 2010 Author Posted March 21, 2010 (edited) Was the drive still spinning/LED blinking when it stalled burning? Were you able to close ImgBurn or did it stay in memory? First thing I'd do is look for the latest drivers for your motherboard's chipset and/or SATA controllers (you can use SIW to identify them). I'm not sure about drive spinning, LED was not blinking and I was unable to close/stop ImgBurn - it was not responding (well, I gave it 5-10 minutes). Then I had to shut the computer down. I installed the SIW - not sure what I'm looking for... Edited March 21, 2010 by toshik
LIGHTNING UK! Posted March 21, 2010 Posted March 21, 2010 Sounding more like a driver issue then. You say it's connected via eSATA - which controller is that eSATA port actually coming from? Intel / JMicron / NVIDIA / Something else?
toshik Posted March 21, 2010 Author Posted March 21, 2010 (edited) Sounding more like a driver issue then. You say it's connected via eSATA - which controller is that eSATA port actually coming from? Intel / JMicron / NVIDIA / Something else? Ok, what it says in the computer description: "Quick access to files via high-speed eSATA combo port, which also serves as a USB 2.0 port" If I'm not mustaken it's: Intel® 5 Series/3400 Series Chipset Family USB Enhanced Host Controller Edited March 21, 2010 by toshik
LIGHTNING UK! Posted March 21, 2010 Posted March 21, 2010 You'd be looking for an IDE/ATA/SATA/SCSI/RAID controller type entry rather than USB. I don't know and kind find enough info on the PC/chipset to figure out if it's part of Intel's stuff or if it's a 3rd party chipset that's controlling the eSATA port. It's always worth updating the Intel chipset and matrix drivers though. http://www.intel.com/support/chipsets/inf/ http://www.intel.com/support/chipsets/imsm/
toshik Posted March 21, 2010 Author Posted March 21, 2010 (edited) You'd be looking for an IDE/ATA/SATA/SCSI/RAID controller type entry rather than USB. It's the same Intel: Intel® 5 Series/3400 Series Chipset Family 6 Port SATA AHCI Controller I'm sorry but the Intel updates are dated are the same age or few months older than my laptop! :-( I had a virtual drive mounted by DAEMON Tools light - could it be the problem as well? I need a SOLUTION please! Edited March 22, 2010 by toshik
toshik Posted March 22, 2010 Author Posted March 22, 2010 (edited) Another coaster! Well, this time it went 49% and got stock! Then we've got at least an error: Something is very wrong! The program does not know where and how to switch the layers on DL BD video disk? I remember it was (a big) issue with DL DVDs - is it the same with DL BDs? The log: I 22:23:08 ImgBurn Version 2.5.1.0 started! I 22:23:08 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 22:23:08 Total Physical Memory: 4,184,956 KB - Available: 2,885,204 KB W 22:23:08 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 22:23:08 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 22:23:08 Initialising SPTI... I 22:23:08 Searching for SCSI / ATAPI devices... I 22:23:08 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 22:23:08 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 22:23:08 Found 1 BD-ROM/DVD±RW and 1 BD-RE! I 22:24:08 Operation Started! I 22:24:08 Source File: C:\Temp\Blu-Ray\__.ISO I 22:24:08 Source File Sectors: 19,773,344 (MODE1/2048) I 22:24:08 Source File Size: 40,495,808,512 bytes I 22:24:08 Source File Volume Identifier: _______________ I 22:24:08 Source File Volume Set Identifier: 3C72B525012DB733 I 22:24:08 Source File Application Identifier: ImgBurn v2.5.0.0 I 22:24:08 Source File Implementation Identifier: ImgBurn I 22:24:08 Source File File System(s): UDF (2.50) I 22:24:08 Destination Device: [0:2:0] PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 22:24:08 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) I 22:24:08 Destination Media Sectors: 24,438,784 I 22:24:08 Write Mode: BD I 22:24:08 Write Type: DAO I 22:24:08 Write Speed: 1x I 22:24:08 BD-R Verify Not Required: Yes I 22:24:08 Link Size: Auto I 22:24:08 Lock Volume: Yes I 22:24:08 Test Mode: No I 22:24:08 OPC: No I 22:24:08 BURN-Proof: Enabled W 22:24:08 Write Speed Miscompare! - Wanted: 4,496 KB/s (1x), Got: 8,990 KB/s (2x) I 22:24:08 Advanced Settings - Optimal Writing Speed: No I 22:24:09 Filling Buffer... (40 MB) I 22:24:10 Writing LeadIn... I 22:24:30 Writing Session 1 of 1... (1 Track, LBA: 0 - 19773343) I 22:24:30 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 19773343) W 23:06:11 Failed to Write Sectors 9763040 - 9763071 - Reason: Invalid Address For Write W 23:06:11 Retrying (1 of 20)... W 23:06:11 Retry Failed - Reason: Invalid Address For Write W 23:06:11 Retrying (2 of 20)... W 23:06:11 Retry Failed - Reason: Invalid Address For Write W 23:06:11 Retrying (3 of 20)... W 23:06:11 Retry Failed - Reason: Invalid Address For Write W 23:06:11 Retrying (4 of 20)... W 23:06:11 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (5 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (6 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (7 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (8 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (9 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (10 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (11 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (12 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (13 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (14 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (15 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (16 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (17 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (18 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (19 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:06:12 Retrying (20 of 20)... W 23:06:12 Retry Failed - Reason: Invalid Address For Write W 23:08:08 Retrying (21)... W 23:08:08 Retry Failed - Reason: Invalid Address For Write W 23:08:10 Retrying (22)... W 23:08:10 Retry Failed - Reason: Invalid Address For Write W 23:08:11 Retrying (23)... W 23:08:11 Retry Failed - Reason: Invalid Address For Write W 23:08:37 Retrying (24)... W 23:08:37 Retry Failed - Reason: Invalid Address For Write E 23:08:39 Failed to Write Sectors 9763040 - 9763071 - Reason: Invalid Address For Write E 23:08:39 Next Writable Address: 9763008 I 23:08:39 Synchronising Cache... I 23:08:43 Closing Track... I 23:08:45 Finalising Disc... E 23:09:12 Failed to Write Image! I 23:09:12 Exporting Graph Data... I 23:09:12 Graph Data File: C:\Users\Tony\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-205_1.04_SUNDAY-MARCH-21-2010_10-24_PM_VERBAT-IMb-00_1x.ibg I 23:09:12 Export Successfully Completed! E 23:09:12 Operation Failed! - Duration: 00:45:03 I 23:09:12 Average Write Rate: 7,373 KB/s (1.6x) - Maximum Write Rate: 9,038 KB/s (2.0x) Edited March 23, 2010 by toshik
mmalves Posted March 22, 2010 Posted March 22, 2010 They did away with the whole layer concept on the BluRay standard, it's all handled by the drive now. W 23:06:11 Failed to Write Sectors 9763040 - 9763071 - Reason: Invalid Address For Write Usually there's some kind of error before this message. Can you try that burner on another computer? Or try with another eSATA cable. It's also important to find out which chipset on your system is responsible for your eSATA port(s) and then getting the latest drivers for that chipset.
LIGHTNING UK! Posted March 22, 2010 Posted March 22, 2010 Yeah, don't assume that just because your laptop is new that it'll have the latest drivers on it. You should run the updates I posted links to earlier.
toshik Posted March 22, 2010 Author Posted March 22, 2010 (edited) Yeah, don't assume that just because your laptop is new that it'll have the latest drivers on it. You should run the updates I posted links to earlier. Yep I ran both of them before getting the second coaster. At this point the last resort left is to switch from eSATA to USB. What's bugging me is why did it write the BR SL 25Gb no problem? Edited March 22, 2010 by toshik
LIGHTNING UK! Posted March 22, 2010 Posted March 22, 2010 Hmm it seems my 'favourite' is now out of date for the Intel Matrix Driver. It's now known as Intel Rapid Storage and you can download the latest one from: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15251
toshik Posted March 22, 2010 Author Posted March 22, 2010 (edited) Hmm it seems my 'favourite' is now out of date for the Intel Matrix Driver. It's now known as Intel Rapid Storage and you can download the latest one from: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=15251 Successfully installed - thanks! Will keep my fingers crossed and will try to burn another one :-( Edited March 22, 2010 by toshik
LIGHTNING UK! Posted March 22, 2010 Posted March 22, 2010 I'd do some testing on BD-RE DL first I think
toshik Posted March 22, 2010 Author Posted March 22, 2010 (edited) I'd do some testing on BD-RE DL first I think Still no-go, this time 63%... I did not switch to USB, still on external cable eSATA. The program did not lock up like it did first time. I 12:07:25 ImgBurn Version 2.5.1.0 started! I 12:07:25 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 12:07:25 Total Physical Memory: 4,184,956 KB - Available: 2,784,252 KB W 12:07:25 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 12:07:25 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 12:07:25 Initialising SPTI... I 12:07:25 Searching for SCSI / ATAPI devices... I 12:07:25 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 12:07:25 Found 1 BD-ROM/DVD±RW! W 12:07:28 Device Arrival Detected! I 12:07:28 Searching for SCSI / ATAPI devices... I 12:07:28 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 12:07:38 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 12:07:38 Found 1 BD-ROM/DVD±RW and 1 BD-RE! I 12:08:11 Operation Started! I 12:08:11 Source File: C:\Temp\Blu-Ray\HL.ISO I 12:08:11 Source File Sectors: 19,773,344 (MODE1/2048) I 12:08:11 Source File Size: 40,495,808,512 bytes I 12:08:11 Source File Volume Identifier: HURT_LOCKER I 12:08:11 Source File Volume Set Identifier: 3C72B525012DB733 I 12:08:11 Source File Application Identifier: ImgBurn v2.5.0.0 I 12:08:11 Source File Implementation Identifier: ImgBurn I 12:08:11 Source File File System(s): UDF (2.50) I 12:08:11 Destination Device: [0:2:0] PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 12:08:11 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) I 12:08:11 Destination Media Sectors: 24,438,784 I 12:08:11 Write Mode: BD I 12:08:11 Write Type: DAO I 12:08:11 Write Speed: 1x I 12:08:11 BD-R Verify Not Required: Yes I 12:08:11 Link Size: Auto I 12:08:11 Lock Volume: Yes I 12:08:11 Test Mode: No I 12:08:11 OPC: No I 12:08:11 BURN-Proof: Enabled W 12:08:11 Write Speed Miscompare! - Wanted: 4,496 KB/s (1x), Got: 8,990 KB/s (2x) I 12:08:11 Advanced Settings - Optimal Writing Speed: No I 12:08:11 Filling Buffer... (40 MB) I 12:08:12 Writing LeadIn... I 12:08:33 Writing Session 1 of 1... (1 Track, LBA: 0 - 19773343) I 12:08:33 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 19773343) W 12:57:15 Failed to Write Sectors 12499424 - 12499455 - Reason: Write Error W 12:57:15 Retrying (1 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (2 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (3 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (4 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (5 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (6 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (7 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (8 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (9 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (10 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (11 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (12 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (13 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (14 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (15 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (16 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (17 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (18 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (19 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 12:57:20 Retrying (20 of 20)... W 12:57:20 Retry Failed - Reason: Invalid Address For Write W 13:00:21 Retrying (21)... W 13:00:21 Retry Failed - Reason: Invalid Address For Write W 13:00:23 Retrying (22)... W 13:00:23 Retry Failed - Reason: Invalid Address For Write W 13:00:24 Retrying (23)... W 13:00:24 Retry Failed - Reason: Invalid Address For Write W 13:07:01 Retrying (24)... W 13:07:01 Retry Failed - Reason: Invalid Address For Write E 13:07:02 Failed to Write Sectors 12499424 - 12499455 - Reason: Write Error E 13:07:02 Next Writable Address: 11852096 I 13:07:02 Synchronising Cache... I 13:07:06 Closing Track... I 13:07:09 Finalising Disc... E 13:07:25 Failed to Write Image! I 13:07:25 Exporting Graph Data... I 13:07:25 Graph Data File: C:\Users\Tony\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-205_1.04_MONDAY-MARCH-22-2010_12-08_PM_VERBAT-IMb-00_1x.ibg I 13:07:25 Export Successfully Completed! E 13:07:25 Operation Failed! - Duration: 00:59:14 I 13:07:25 Average Write Rate: 7,124 KB/s (1.6x) - Maximum Write Rate: 9,048 KB/s (2.0x) Edited March 22, 2010 by toshik
LIGHTNING UK! Posted March 22, 2010 Posted March 22, 2010 It's not the program that's locking up, it's your system. ImgBurn is just waiting for a reply to the I/O command it submitted! This time you got the proper error - oh and note that it's the first one, not what you see after a retry. W 12:57:15 Failed to Write Sectors 12499424 - 12499455 - Reason: Write Error So your drive reported a 'Write Error' when trying to write to some sectors somewhere around LBA 12499424. (I say 'somewhere' because the drive can delay the error report due to cache etc) Nobody but Pioneer can tell you why it reported that 'Write Error', it's down to drive internals, the firmware and the media. Maybe some people in the high def forum at cdfreaks would be able to offer you some advice for your particular drive - not a lot of BD burning goes on around here.
toshik Posted March 23, 2010 Author Posted March 23, 2010 (edited) Well, I did it again: tried to burn another one using USB instead of eSATA. Same crap - failed at 61%. So 5 BD DL-R disks are in the garbage! At this point it's safe to say that the Pioneer BDR-205 is not capable of burning the BR DL-R 50Gb using the ImageBurn or vice versa. I had never any problems with ImageBurn in the past plus Pioneer has been making one of the best burners and Verbatim disks by Mitsubishi are the best. Pioneer has been contacted. So obviously the problem is going over 25 Gb - as I mentioned before BR SL-R 25 GB burn no problem whatsoever. Let's face it: both 61% and 63% of total 41 Gb are right pass the 25 Gb landmark! In first case it's 63% of 40,496 = 25,599 Gb (reported by IB) In second case it's 61% of 41,214 = 25,264 Gb (reported by IB) So either the drive or the program don't know that they need to switch layers (drive and ImageBurn need to do some handshaking?) The first layer (25 Gb) is used up, but it keeps writing onto it, runs out of physical space on the disk and gets the error! The error says: Invalid Address for write - sure, no more addresses left on the first layer :-( I think it's obvious or am I the only one who noted this? I 19:12:11 ImgBurn Version 2.5.1.0 started! I 19:12:11 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 19:12:11 Total Physical Memory: 4,184,956 KB - Available: 2,806,204 KB W 19:12:11 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 19:12:11 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 19:12:11 Initialising SPTI... I 19:12:11 Searching for SCSI / ATAPI devices... I 19:12:11 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 19:12:11 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.04 (E:) (USB) I 19:12:11 Found 1 BD-ROM/DVD±RW and 1 BD-RE! I 19:12:55 Operation Started! I 19:12:55 Source File: C:\Temp\Blu-Ray\__.ISO I 19:12:55 Source File Sectors: 20,123,680 (MODE1/2048) I 19:12:55 Source File Size: 41,213,296,640 bytes I 19:12:55 Source File Volume Identifier: _____________________________ I 19:12:55 Source File Volume Set Identifier: 3C72B04801330E5F I 19:12:55 Source File Application Identifier: ImgBurn v2.5.0.0 I 19:12:55 Source File Implementation Identifier: ImgBurn I 19:12:55 Source File File System(s): UDF (2.50) I 19:12:55 Destination Device: [0:0:0] PIONEER BD-RW BDR-205 1.04 (E:) (USB) I 19:12:55 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) I 19:12:55 Destination Media Sectors: 24,438,784 I 19:12:55 Write Mode: BD I 19:12:55 Write Type: DAO I 19:12:55 Write Speed: 1x I 19:12:55 BD-R Verify Not Required: Yes I 19:12:55 Link Size: Auto I 19:12:55 Lock Volume: Yes I 19:12:55 Test Mode: No I 19:12:55 OPC: No I 19:12:55 BURN-Proof: Enabled W 19:12:55 Write Speed Miscompare! - Wanted: 4,496 KB/s (1x), Got: 8,990 KB/s (2x) I 19:12:55 Advanced Settings - Optimal Writing Speed: No I 19:12:55 Filling Buffer... (40 MB) I 19:12:56 Writing LeadIn... I 19:13:16 Writing Session 1 of 1... (1 Track, LBA: 0 - 20123679) I 19:13:16 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 20123679) W 20:00:43 Failed to Write Sectors 12335936 - 12335967 - Reason: Internal Target Failure W 20:00:43 Retrying (1 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (2 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (3 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (4 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (5 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (6 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (7 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (8 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (9 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (10 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (11 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (12 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (13 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (14 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (15 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (16 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (17 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (18 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (19 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write W 20:00:50 Retrying (20 of 20)... W 20:00:50 Retry Failed - Reason: Invalid Address For Write E 20:25:08 Failed to Write Sectors 12335936 - 12335967 - Reason: Internal Target Failure E 20:25:08 Next Writable Address: 12219392 I 20:25:08 Synchronising Cache... I 20:25:13 Closing Track... I 20:25:16 Finalising Disc... E 20:25:46 Failed to Write Image! I 20:25:46 Exporting Graph Data... I 20:25:46 Graph Data File: C:\Users\Tony\AppData\Roaming\ImgBurn\Graph Data Files\PIONEER_BD-RW_BDR-205_1.04_MONDAY-MARCH-22-2010_7-12_PM_VERBAT-IMb-00_1x.ibg I 20:25:46 Export Successfully Completed! E 20:25:46 Operation Failed! - Duration: 01:12:51 I 20:25:46 Average Write Rate: 5,721 KB/s (1.3x) - Maximum Write Rate: 9,038 KB/s (2.0x) Edited March 23, 2010 by toshik
LIGHTNING UK! Posted March 23, 2010 Posted March 23, 2010 Like I said before, the first error is the real one. W 20:00:43 Failed to Write Sectors 12335936 - 12335967 - Reason: Internal Target Failure Drives cache the data they're sent so a write error at a particular LBA could actually be from a problem the drive encountered at an LBA before that one. So basically, you're miles off when you say this: The first layer (25 Gb) is used up, but it keeps writing onto it, runs out of physical space on the disk and gets the error!The error says: Invalid Address for write - sure, no more addresses left on the first layer :-( I think it's obvious or am I the only one who noted this? The 2nd layer is harder for the drive to burn to, so it's more likely to fail at burning it. It makes no difference to the software because all it's doing is sending the drive a steady stream of data.
toshik Posted March 23, 2010 Author Posted March 23, 2010 (edited) I'm sorry but I don't know how the drive and program work. All I used was the common sense which told me that it gets stock shortly after burnung 25 GB (not before 25 GB, not after 30 or 35)! Pioneer suggested to send it in for repairs! Will get a replacent drive - I doubt it'd solve it. Edited March 23, 2010 by toshik
toshik Posted April 5, 2010 Author Posted April 5, 2010 (edited) Ok the replacement new Pioneer drive is in - with the same exact firmware. To play it safe I burned TDK BD-RE DL 50GB. Aside from "zeroing sectors" for almost two hours(!) it burned fine. I can't afford the 6th(!) Mitsubishi/Verbatim BD-R DL 50 GB coaster, do we have a test mode to try it without ruining the disk? Disc ID: VERBAT-IMb-00 Pioneer tech support is useless suggesting to update to the latest firmware :-) Edited April 6, 2010 by toshik
LIGHTNING UK! Posted April 5, 2010 Posted April 5, 2010 Nope, BD doesn't support 'Test Mode' I'm afraid.
toshik Posted April 5, 2010 Author Posted April 5, 2010 (edited) Well, I don't know whose fault it is - Pioneer or software - SOMEBODY's FOR SURE! And it does not work, this time at 39% However I'm the one who lost: 6 BR-R DL 50 GB disks, purchased the Pioneer BDR-205 drive + housing and spent all this time for nothing! I 15:52:02 ImgBurn Version 2.5.1.0 started! I 15:52:02 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 15:52:02 Total Physical Memory: 4,184,956 KB - Available: 2,906,796 KB W 15:52:02 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 15:52:02 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 15:52:02 Initialising SPTI... I 15:52:02 Searching for SCSI / ATAPI devices... I 15:52:02 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 15:52:02 Found 1 BD-ROM/DVD±RW! W 15:52:07 Device Arrival Detected! I 15:52:07 Searching for SCSI / ATAPI devices... I 15:52:08 -> Drive 1 - Info: hp BDDVDRW CT21L 1.02 (D:) (ATAPI) I 15:52:08 -> Drive 2 - Info: PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 15:52:08 Found 1 BD-ROM/DVD±RW and 1 BD-RE! I 15:54:13 Operation Started! I 15:54:13 Source File: C:\Temp\Blu-Ray\PW.ISO I 15:54:13 Source File Sectors: 20,123,680 (MODE1/2048) I 15:54:13 Source File Size: 41,213,296,640 bytes I 15:54:13 Source File Volume Identifier: PRETTY_WOMAN_DEU I 15:54:13 Source File Volume Set Identifier: 3C72B04801330E5F I 15:54:13 Source File Application Identifier: ImgBurn v2.5.0.0 I 15:54:13 Source File Implementation Identifier: ImgBurn I 15:54:13 Source File File System(s): UDF (2.50) I 15:54:13 Destination Device: [0:2:0] PIONEER BD-RW BDR-205 1.04 (E:) (ATAPI) I 15:54:13 Destination Media Type: BD-R (Disc ID: VERBAT-IMb-00) (Speeds: 2x) I 15:54:13 Destination Media Sectors: 24,438,784 I 15:54:13 Write Mode: BD I 15:54:13 Write Type: DAO I 15:54:13 Write Speed: 1x I 15:54:13 BD-R Verify Not Required: Yes I 15:54:13 Link Size: Auto I 15:54:13 Lock Volume: Yes I 15:54:13 Test Mode: No I 15:54:13 OPC: No I 15:54:13 BURN-Proof: Enabled W 15:54:13 Write Speed Miscompare! - Wanted: 4,496 KB/s (1x), Got: 8,990 KB/s (2x) I 15:54:13 Advanced Settings - Optimal Writing Speed: No I 15:54:14 Filling Buffer... (40 MB) I 15:54:15 Writing LeadIn... I 15:54:36 Writing Session 1 of 1... (1 Track, LBA: 0 - 20123679) I 15:54:36 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 20123679) W 16:24:48 Failed to Write Sectors 7893632 - 7893663 - Reason: Internal Target Failure W 16:24:48 Retrying (1 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (2 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (3 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (4 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (5 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (6 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (7 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (8 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (9 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (10 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (11 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (12 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (13 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (14 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (15 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (16 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (17 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (18 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (19 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:24:58 Retrying (20 of 20)... W 16:24:58 Retry Failed - Reason: Invalid Address For Write W 16:41:32 Retrying (21)... W 16:41:32 Retry Failed - Reason: Invalid Address For Write W 16:43:20 Retrying (22)... W 16:43:20 Retry Failed - Reason: Invalid Address For Write W 16:43:22 Retrying (23)... W 16:43:22 Retry Failed - Reason: Invalid Address For Write W 16:43:23 Retrying (24)... W 16:43:23 Retry Failed - Reason: Invalid Address For Write W 16:47:29 Retrying (25)... W 16:47:29 Retry Failed - Reason: Invalid Address For Write W 16:47:30 Retrying (26)... W 16:47:30 Retry Failed - Reason: Invalid Address For Write W 16:47:30 Retrying (27)... W 16:47:30 Retry Failed - Reason: Invalid Address For Write W 16:47:31 Retrying (28)... W 16:47:31 Retry Failed - Reason: Invalid Address For Write W 16:47:32 Retrying (29)... W 16:47:32 Retry Failed - Reason: Invalid Address For Write E 16:47:34 Failed to Write Sectors 7893632 - 7893663 - Reason: Internal Target Failure E 16:47:34 Next Writable Address: 0 I 16:47:34 Synchronising Cache... I 16:47:37 Closing Track... I 16:47:40 Finalising Disc... Edited April 6, 2010 by toshik
toshik Posted April 8, 2010 Author Posted April 8, 2010 (edited) Do you beleive in magic? I now certainly do! According to Pioneer the BDR-205 v1.04 supports those Verbatim disks, according to you the program works :-) The BDR-205 drive FW 1.04 does support the media you listed "VERBATIMb" although it will only burn at 2X. I'm not sure why it is not working for you. FYI, if you use Panasonic DL 4x media "MEI__T02" you can burn up to 10x. And if you use Panasonic DL 6x media (most likely you will need to buy online), it will burn up to 12x. Just letting you know in case speed is a factor for you. All other DL media will burn 8x (best case). Best Regards, Blu-ray Disc Support Desk Pioneer Electronics (USA) Inc. www.pioneerelectronics.com Edited April 8, 2010 by toshik
LIGHTNING UK! Posted April 8, 2010 Posted April 8, 2010 Well you know the program works because you burnt a BD-RE DL yourself didn't you? If it was going to mess up on a BD DL disc then it would have done so on one of those too (and it would be doing the same for everyone in the world). The error message your drive reported is also a very 'internal' sounding one - 'Internal Target Failure'. So yeah, something isn't right with it but if Pioneer say it should burn the Verbatims ok then I guess it should. Take a look at the cdfreaks forum and see if you can find anyone else that's burnt your exact media with the drive. Maybe it's an issue with where your BD-R DL's came from in the world? Perhaps they're not quite up to the standard of the ones Pioneer tested and built the firmware for. I guess all you can do now is try the other media they suggested. If it does the same thing then you should tell them that.
Recommended Posts