ledaswan Posted August 22, 2012 Share Posted August 22, 2012 Hello, I replaced a motherboard and reinstalled everything, now ImgBurn/Sony BD-RW BWU-500S/Verbatim BD-R gives me invalid address for write. I successfully burned three DVD+R discs, without any problems. With the old motherboard, I burned 100+ of these same BD-R discs (~5% failure rate, which seemed high, but better than the 100% failure I get now). I tried creating an image first (successful) and burning that (unsuccessful). I tried lower write speed and using ASPI, instead of SPTI. I also tried a different job using source files on a different physical hard drive. I also udated ImgBurn v2.5.5.0 to ImgBurn v2.5.7.0. Same result for all these attempts. Looking at the old logs, the Sony drive used to be detected as an ATA device: ... 21:14:02 -> Drive 2 - Info: SONY BD RW BWU-500S 1.63 (S:) (ATA) Now it is detected as a SCSI device: ... 02:12:30 -> Drive 2 - Info: SONY BD RW BWU-500S 1.63 (S:) (SCSI) I searched the forum & most responses to this problem involve switching to different brand discs. These discs worked before. They are from the same batch, purchased together, so it seems ulikely they all suddenly went bad. Thanks for any help. One of the burn logs: ; //****************************************\\ ; ImgBurn Version 2.5.7.0 - Log ; Tuesday, 21 August 2012, 03:01:03 ; \\****************************************// ; ; I 02:12:29 ImgBurn Version 2.5.7.0 started! I 02:12:29 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 02:12:29 Total Physical Memory: 3,112,228 KB - Available: 2,555,956 KB W 02:12:29 Drive C:\ (FAT32) does not support single files > 4 GB in size. <snip... more drives> I 02:12:29 Initialising SPTI... I 02:12:29 Searching for SCSI / ATAPI devices... I 02:12:30 -> Drive 1 - Info: TSSTcorp CDDVDW SH-S222A SB02 (Q:) (ATA) I 02:12:30 -> Drive 2 - Info: SONY BD RW BWU-500S 1.63 (S:) (SCSI) I 02:12:30 Found 1 DVD±RW/RAM and 1 BD-RE! I 02:13:49 Operation Started! I 02:13:49 Building Image Tree... I 02:13:49 Checking Directory Depth... I 02:13:49 Calculating Totals... I 02:13:49 Preparing Image... I 02:13:49 Checking Path Length... I 02:13:49 Contents: 273 Files, 20 Folders I 02:13:49 Content Type: Data I 02:13:49 Data Type: MODE1/2048 I 02:13:49 File System(s): ISO9660, UDF (1.02) I 02:13:49 Volume Label: LRO_LOLA-1 I 02:13:49 Size: 21,674,104,275 bytes I 02:13:49 Sectors: 10,583,218 I 02:13:49 Image Size: 21,675,704,320 bytes I 02:13:49 Image Sectors: 10,583,840 I 02:13:52 Operation Successfully Completed! - Duration: 00:00:02 I 02:13:52 Operation Started! I 02:13:52 Source File: -==/\/[bUILD IMAGE]\/\==- I 02:13:52 Source File Sectors: 10,583,840 (MODE1/2048) I 02:13:52 Source File Size: 21,675,704,320 bytes I 02:13:52 Source File Volume Identifier: LRO_LOLA-1 I 02:13:52 Source File Volume Set Identifier: 411511B800A17F0D I 02:13:52 Source File Application Identifier: IMGBURN V2.5.7.0 - THE ULTIMATE IMAGE BURNER! I 02:13:52 Source File Implementation Identifier: ImgBurn I 02:13:52 Source File File System(s): ISO9660, UDF (1.02) I 02:13:52 Destination Device: [4:2:0] SONY BD RW BWU-500S 1.63 (S:) (SCSI) I 02:13:52 Destination Media Type: BD-R (Disc ID: VERBAT-IMe-000) I 02:13:52 Destination Media Supported Write Speeds: 4x, 6x I 02:13:52 Destination Media Sectors: 12,219,392 I 02:13:52 Write Mode: BD I 02:13:52 Write Type: DAO I 02:13:52 Write Speed: MAX I 02:13:52 Hardware Defect Management Active: No I 02:13:52 BD-R Verify Not Required: Yes I 02:13:52 Link Size: Auto I 02:13:52 Lock Volume: Yes I 02:13:52 Test Mode: No I 02:13:52 OPC: No I 02:13:52 BURN-Proof: Enabled I 02:13:53 Write Speed Successfully Set! - Effective: 26,970 KB/s (6x) I 02:14:27 Filling Buffer... (40 MB) I 02:14:28 Writing LeadIn... I 02:14:31 Writing Session 1 of 1... (1 Track, LBA: 0 - 10583839) I 02:14:31 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 10583839) W 02:14:37 Failed to Write Sectors 68544 - 68575 - Reason: The request could not be performed because of an I/O device error. W 02:14:37 Retrying (1 of 20)... W 02:14:41 Retry Failed - Reason: Invalid Address For Write W 02:14:41 Retrying (2 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (3 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (4 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (5 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (6 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (7 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (8 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (9 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (10 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (11 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (12 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (13 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (14 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (15 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (16 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (17 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (18 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (19 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write W 02:14:42 Retrying (20 of 20)... W 02:14:42 Retry Failed - Reason: Invalid Address For Write E 03:00:34 Failed to Write Sectors 68544 - 68575 - Reason: The request could not be performed because of an I/O device error. E 03:00:34 Next Writable Address: 0 I 03:00:34 Synchronising Cache... W 03:00:37 User opted to skip the 'Close Track/Session/Disc' functions. E 03:00:37 Failed to Write Image! I 03:00:37 Exporting Graph Data... I 03:00:37 Graph Data File: I:\Documents\ImgBurn\Graph Data Files\SONY_BD_RW_BWU-500S_1.63_TUESDAY-AUGUST-21-2012_2-13_AM_VERBAT-IMe-000_MAX.ibg I 03:00:37 Export Successfully Completed! E 03:00:37 Operation Failed! - Duration: 00:46:45 I 03:00:37 Average Write Rate: 49 KB/s (0.0x) - Maximum Write Rate: 22,921 KB/s (5.1x) I 03:00:57 Project Successfully Saved! I 03:00:57 File Name: I:\Documents\ImgBurn\Project Files\LRO_LOLA-1.ibb I 03:01:02 Close Request Acknowledged I 03:01:02 Closing Down... I 03:01:02 Shutting down SPTI... I 03:01:02 ImgBurn closed! ; ; Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 22, 2012 Share Posted August 22, 2012 It looks like you've attached your drive to a bad controller (one that isn't optical drive friendly). Hopefully your board has another one... attach the drive to that instead. Beyond that, we'd need to know more about your motherboard - i.e. which make/model it is so we can work out which chipsets are available on it. Link to comment Share on other sites More sharing options...
ledaswan Posted August 23, 2012 Author Share Posted August 23, 2012 Hi, thanks for your reply. Yes, that was the problem. I don't have enough SATA connectors, so I bought a Rosewill RC-212 Controller Card. The Bluray drive seemed to work fine reading and burning DVDs, until I got around to burning BD-R discs. I connected it to the motherboard and it burns now. It still seems to have some problems, though. After burning, I have to repeat the eject cycle several times before ImgBurn can verify the written files. Eventually, it works. The motherboard is a Biostar N68S3+, NVIDIA MCP68S chipset. Thanks again. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted August 23, 2012 Share Posted August 23, 2012 If you need to go the PCI card route, get a Silicon Image 3512 chipset based card and put the drive on that. I'm not a fan of any non Intel chipset controller really. Link to comment Share on other sites More sharing options...
Recommended Posts