synthea Posted January 23, 2011 Share Posted January 23, 2011 I have a LaCie 8x blu Ray Drive. I have successfully used BD Rebuilder to shrink media to fit on 25 gb discs and burned them with imgburn at least 50xs previously. Suddenly I started getting the error message below (followed by log information). After losing 8 blu ray disks (from 2 different brands that both were batting 100% good previously), I tried to copy files that I had burned successfully a few days earlier - as I knew they were good files. I then tried the BD Burner on another computer - only to get the same results. The first computer has Win 7 ultimate, 64 bit, with the NEWEST version of imgburn -- and the 2nd one has Win 7, home, 64 bit with 2.5.4.0 imgburn. Since I eliminated the possibility of bad disks or bad files, the problem has to either be imgburn or my blu ray drive. My drive has a 3 year warrenty and I've only been using it about 8 months, so I need to see if someone can tell me if it could be something else before I decide the burner is bad. I did order a cleaner for the drive, but won't get it for several days, and I'm too antsy to wait - just in case there is some adjustment I can make on my computer to make it work. Thank you. Shari(synthea) ERROR MESSAGE I/O Error! Device: [0:0:0] PIONEER BD-RW BDR-203 1.10 (F:)(USB) ScsiStatus:0x02 Interpretaton: Check Condition CDB:AA 00 00 18 52 40 00 00 00 20 40 00 Interpretation:Write(12) - Sectors:1593920 - 1593951 Sense Area: 70 00 03 00 00 00 00 0E 00 00 00 00 73 03 00 00 00 00 Interpretation:Power Calibration Area Error LOG BELOW: I 17:56:08 ImgBurn Version 2.5.4.0 started! I 17:56:08 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 17:56:08 Total Physical Memory: 6,192,320 KB - Available: 3,814,196 KB W 17:56:08 Drive Z:\ (FAT) might not support single files > 4 GB in size. W 17:56:08 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 17:56:08 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 17:56:08 Initialising SPTI... I 17:56:08 Searching for SCSI / ATAPI devices... I 17:56:08 -> Drive 1 - Info: Optiarc DVD RW AD-7561S AH03 (E:) (ATAPI) I 17:56:08 Found 1 DVD±RW/RAM! W 19:29:49 Device Arrival Detected! I 19:29:49 Searching for SCSI / ATAPI devices... I 19:29:50 -> Drive 1 - Info: Optiarc DVD RW AD-7561S AH03 (E:) (ATAPI) I 19:29:50 -> Drive 2 - Info: PIONEER BD-RW BDR-203 1.10 (F:) (USB) I 19:29:50 Found 1 DVD±RW/RAM and 1 BD-RE! I 19:34:51 Operation Started! I 19:34:51 Building Image Tree... I 19:34:53 Calculating Totals... I 19:34:53 Preparing Image... I 19:34:54 Contents: 1,232 Files, 38 Folders I 19:34:54 Content Type: BD Video I 19:34:54 Data Type: MODE1/2048 I 19:34:54 File System(s): UDF (2.50) I 19:34:54 Volume Label: SCOTT_VS_WORLD I 19:34:54 Size: 24,278,261,594 bytes I 19:34:54 Sectors: 11,855,366 I 19:34:54 Image Size: 24,286,068,736 bytes I 19:34:54 Image Sectors: 11,858,432 I 19:34:55 Operation Successfully Completed! - Duration: 00:00:04 I 19:34:55 Operation Started! I 19:34:55 Source File: -==/\/[bUILD IMAGE]\/\==- I 19:34:55 Source File Sectors: 11,858,432 (MODE1/2048) I 19:34:55 Source File Size: 24,286,068,736 bytes I 19:34:55 Source File Volume Identifier: SCOTT_VS_WORLD I 19:34:55 Source File Volume Set Identifier: 3E369C5900B4EC86 I 19:34:55 Source File Application Identifier: ImgBurn v2.5.4.0 I 19:34:55 Source File Implementation Identifier: ImgBurn I 19:34:55 Source File File System(s): UDF (2.50) I 19:34:55 Destination Device: [0:0:0] PIONEER BD-RW BDR-203 1.10 (F:) (USB) I 19:34:55 Destination Media Type: BD-R (Disc ID: PHILIP-R04-000) (Speeds: 2x, 4x, 6x, 8x) I 19:34:55 Destination Media Sectors: 12,219,392 I 19:34:55 Write Mode: BD I 19:34:55 Write Type: DAO I 19:34:55 Write Speed: MAX I 19:34:55 BD-R Verify Not Required: Yes I 19:34:55 Link Size: Auto I 19:34:55 Lock Volume: Yes I 19:34:55 Test Mode: No I 19:34:55 OPC: No I 19:34:55 BURN-Proof: Enabled I 19:34:56 Write Speed Successfully Set! - Effective: 35,960 KB/s (8x) I 19:34:56 Advanced Settings - Optimal Writing Speed: No I 19:34:56 Filling Buffer... (40 MB) I 19:35:06 Writing LeadIn... I 19:35:32 Writing Session 1 of 1... (1 Track, LBA: 0 - 11858431) I 19:35:32 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11858431) I 19:35:35 M2TS File: \BDMV\STREAM\00000.m2ts I 19:35:35 Reset CPI flag in 333888 packets (00: 0, 01: 0, 10: 0, 11: 333888, Total: 333888, Bad Sync: 0) I 19:35:39 M2TS File: \BDMV\STREAM\00001.m2ts I 19:35:39 Reset CPI flag in 162976 packets (00: 0, 01: 0, 10: 0, 11: 162976, Total: 162976, Bad Sync: 0) I 19:35:54 M2TS File: \BDMV\STREAM\00002.m2ts I 19:35:54 Reset CPI flag in 711552 packets (00: 0, 01: 0, 10: 0, 11: 711552, Total: 711552, Bad Sync: 0) I 19:35:54 M2TS File: \BDMV\STREAM\00003.m2ts I 19:35:54 Reset CPI flag in 6336 packets (00: 0, 01: 0, 10: 0, 11: 6336, Total: 6336, Bad Sync: 0) I 19:35:54 M2TS File: \BDMV\STREAM\00004.m2ts I 19:35:54 Reset CPI flag in 6752 packets (00: 0, 01: 0, 10: 0, 11: 6752, Total: 6752, Bad Sync: 0) I 19:35:54 M2TS File: \BDMV\STREAM\00005.m2ts I 19:35:54 Reset CPI flag in 6816 packets (00: 0, 01: 0, 10: 0, 11: 6816, Total: 6816, Bad Sync: 0) W 19:41:41 Failed to Write Sectors 1593920 - 1593951 - Reason: Power Calibration Area Error W 19:41:41 Retrying (1 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (2 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (3 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (4 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (5 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (6 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (7 of 20)... W 19:41:41 Retry Failed - Reason: Invalid Address For Write W 19:41:41 Retrying (8 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (9 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (10 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (11 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (12 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (13 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (14 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (15 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (16 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (17 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (18 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (19 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write W 19:41:42 Retrying (20 of 20)... W 19:41:42 Retry Failed - Reason: Invalid Address For Write E 20:23:50 Failed to Write Sectors 1593920 - 1593951 - Reason: Power Calibration Area Error E 20:23:50 Next Writable Address: 0 I 20:23:50 Synchronising Cache... Link to comment Share on other sites More sharing options...
ianymaty Posted January 23, 2011 Share Posted January 23, 2011 There is a newer firmware for your drive, you should try with http://www.firmwarehq.com/Pioneer/BDR-203/files.html Try all available speeds rather than default MAX Also your ImgBurn is outdated. Link to comment Share on other sites More sharing options...
synthea Posted January 23, 2011 Author Share Posted January 23, 2011 (edited) 1. I have now gotten the same message on a BRAND NEW BLUE RAY DRIVE. It seems pretty unlikely that BOTH would need firmware updates. Also, the firmware you reference (IF it is really for my LACIE MANAGED pioneer drive, is dated Oct 2010. I burned without problems until Jan 14th, 2011. 2. MAX speed is NOT the DEFAULT. Look at your current IMGBURN. AWS is the Default (I assume that means "automatic write speed" and I have always used it without problems. 3. If you read my post closely you will see that I TRIED BURNING on 2 separate computers. ONE of those computers DOES HAVE THE NEWEST IMGBURN 2.5.5. The problem started on that computer. I just didn't send the log from that one cause I was using the other one when I gave up and decided to ask for help. so I am not living in the past. SOMETHING ELSE IS AT FAULT. Could it be a new windows 7 update? HELP. HELP HELP. PLEASE PLEASE PLEASE! I DIDN'T TOUCH A THING. JUST ONE DAY ABOUT A WEEK AGO IT ALL STOPPED BURNING OUT OF THE BLUE - AND I STARTED GETTING THE INTERPRETATION ERRORS. IT HAPPENED ON TWO SEPARATE COMPUTERS WITH IMGBURN (ONE USING 2.5.5 & ONE USING 2.5.4). NOW IT DID THE SAME THING ON A BRAND NEW BLU RAY BURNER. I've lost so many blu-ray disks now, it's really getting expensive. NOTE The only thing that changed between bad burns and good ones on BOTH COMPUTERS was I added a HP printer/scanner/fax with network (wireless) printing. HOWEVER, thinking that might be the problem, I DID A "SYSTEM RESTORE" ON ONE of the COMPUTERs TO ONE DAY PRIOR to the installation. The problem still HAPPENS. Is it possible that "system restore" would ignore some change from the installation that could still effect my imgburn? Thank you thank you thank you for HELPING ME. I'M SO DESPERATE NOW. Shari. synthea@aol.com . NEWEST ERROR MSG & LOG I/O Error! Device: [0:0:0] PIONEER BD-RW BDR-203 1.10 (F:)(USB) ScsiStatus:0x02 Interpretaton: Check Condition CDB:AA 00 00 2C 3E 80 00 00 00 20 40 00 Interpretation:Write(12) - Sectors:2899584 - 2899615 Sense Area: 70 00 03 00 00 00 00 0A 00 00 00 B4 0C 00 00 00 00 00 Interpretation:Power Calibration Area Error I 12:03:12 ImgBurn Version 2.5.4.0 started! I 12:03:12 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 12:03:12 Total Physical Memory: 8,289,472 KB - Available: 6,478,820 KB W 12:03:12 Drive Z:\ (FAT) might not support single files > 4 GB in size. W 12:03:12 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 12:03:12 Duplex Secure's SPTD driver can have a detrimental effect on drive performance. I 12:03:12 Initialising SPTI... I 12:03:12 Searching for SCSI / ATAPI devices... I 12:03:12 -> Drive 1 - Info: Optiarc DVD RW AD-7561S AH03 (E:) (ATAPI) I 12:03:12 -> Drive 2 - Info: HL-DT-ST BD-RE BH10LS30 1.00 (F:) (USB) I 12:03:12 Found 1 DVD±RW/RAM and 1 BD-RE! I 12:04:37 Operation Started! I 12:04:37 Building Image Tree... I 12:04:41 Calculating Totals... I 12:04:41 Preparing Image... I 12:04:41 Contents: 345 Files, 22 Folders I 12:04:41 Content Type: BD Video I 12:04:41 Data Type: MODE1/2048 I 12:04:41 File System(s): UDF (2.50) I 12:04:41 Volume Label: ALPHA_OMEGA I 12:04:41 Size: 23,591,532,395 bytes I 12:04:41 Sectors: 11,519,500 I 12:04:41 Image Size: 23,594,401,792 bytes I 12:04:41 Image Sectors: 11,520,704 I 12:04:43 Operation Successfully Completed! - Duration: 00:00:05 I 12:04:43 Operation Started! I 12:04:43 Source File: -==/\/[bUILD IMAGE]\/\==- I 12:04:43 Source File Sectors: 11,520,704 (MODE1/2048) I 12:04:43 Source File Size: 23,594,401,792 bytes I 12:04:43 Source File Volume Identifier: ALPHA_OMEGA I 12:04:43 Source File Volume Set Identifier: 3E37609200AFC8EC I 12:04:43 Source File Application Identifier: ImgBurn v2.5.4.0 I 12:04:43 Source File Implementation Identifier: ImgBurn I 12:04:43 Source File File System(s): UDF (2.50) I 12:04:43 Destination Device: [0:0:0] HL-DT-ST BD-RE BH10LS30 1.00 (F:) (USB) I 12:04:43 Destination Media Type: BD-R (Disc ID: PHILIP-R04-000) (Speeds: 2x, 4x, 6x, 8x) I 12:04:43 Destination Media Sectors: 12,219,392 I 12:04:43 Write Mode: BD I 12:04:43 Write Type: DAO I 12:04:43 Write Speed: MAX I 12:04:43 BD-R Verify Not Required: Yes I 12:04:43 Link Size: Auto I 12:04:43 Lock Volume: Yes I 12:04:43 Test Mode: No I 12:04:43 OPC: No I 12:04:43 BURN-Proof: Enabled I 12:04:43 Write Speed Successfully Set! - Effective: 35,964 KB/s (8x) I 12:05:32 Filling Buffer... (40 MB) I 12:05:35 Writing LeadIn... I 12:05:36 M2TS File: \BDMV\STREAM\00000.m2ts I 12:05:36 Reset CPI flag in 246816 packets (00: 0, 01: 0, 10: 0, 11: 246816, Total: 246816, Bad Sync: 0) I 12:05:36 Writing Session 1 of 1... (1 Track, LBA: 0 - 11520703) I 12:05:36 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 11520703) W 12:10:27 Failed to Write Sectors 2899584 - 2899615 - Reason: Write Error W 12:10:27 Retrying (1 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (2 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (3 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (4 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (5 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (6 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (7 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (8 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (9 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write W 12:10:27 Retrying (10 of 20)... W 12:10:27 Retry Failed - Reason: Invalid Address For Write Edited January 25, 2011 by synthea Link to comment Share on other sites More sharing options...
synthea Posted January 25, 2011 Author Share Posted January 25, 2011 Just to let anyone know who might view this. Problem has been solved. Bad media was at fault! It was just unbelievably unfortunate that I happened to have a STRING of bad blu-ray disks from a spool of 25 (The first 7 disks from that spool were good - the remaining 18 disks were ALL BAD). Unbelievably, another disk from an old spool I tried was also bad - leading me to believe for a long time that bad disks were NOT the problem. ] Today, in final desperation (and after eliminating every other possible problem - including purchasing a new blu ray player and trying a disk cleaner) I opened a brand new spool of blu-ray disks and the very 1st disk burned just fine. I made NO FIRMWARE UPDATES and NO other CHANGES to my computer or blu-ray player. Also, NO CHANGES or speed settings were needed or adjusted on my IMGBURN. Lesson learned: Even though it seems unlikely, It's possible to get a large number of bad disks on a spool - even when using a trusted brand purchased from a trusted source. First time I've ever had that many bad disks on ANY SPOOL containing ANY KIND of DISK. shari synthea@aol.com Link to comment Share on other sites More sharing options...
Recommended Posts