itm Posted April 30, 2020 Share Posted April 30, 2020 I am using ImgBurn 2.5.8.0 on Windows 10, attempting to burn 4 .exe files in a folder to a 7GB DVD-R. A number of attempts have now failed with the error below. The files vary in size from 1.5GB to 1.9GB. Any idea why I am getting this error? I/O Error! Device: [0:0:0] HL-DT-ST BD-RE BH10LS30 1.00 (E:) (SATA) ScsiStatus: 0x02 Interpretation: Check Condition CDB: 53 00 00 00 00 00 30 DA 00 00 Interpretation: Reserve Track - Sectors: 3,201,536 Sense Area: 70 00 05 00 00 00 00 0A 53 00 00 0D 24 00 00 C0 00 05 SK Interpretation: Illegal Request ASC/ASCQ Interpretation: Invalid Field in CDB Link to comment Share on other sites More sharing options...
dbminter Posted April 30, 2020 Share Posted April 30, 2020 I have a possible idea, and it's a good one, but we need the entire failure log. Go into Help in the ImgBurn application and you'll see some option about the Log near the bottom of the Help menu. The folder containing the log opens so you can open the .LOG file. Copy and paste the entire section of the failed write/verify or both sections from the log into a post here. Or, you can attach the entire .LOG file to a post and I can just weed through it and see what I find. In the meantime, is this your first time using ImgBurn or have you successfully used it before to burn discs? I am guessing by your post count you're relatively new to the application, although that could just mean you've used it for a while and only just recently have had issues. If you're relatively unfamiliar with burning discs, this could go a ways to explaining what I think the problem is. Link to comment Share on other sites More sharing options...
itm Posted April 30, 2020 Author Share Posted April 30, 2020 This was the last entry from the log: I 18:30:40 Operation Started! I 18:30:40 Building Image Tree... I 18:30:46 Calculating Totals... I 18:30:46 Preparing Image... I 18:30:46 Contents: 4 Files, 1 Folder I 18:30:46 Content Type: Data I 18:30:46 Data Type: MODE1/2048 I 18:30:46 File System(s): UDF (1.02) I 18:30:46 Volume Label: Realtracks & Realdrums5 I 18:30:46 Size: 6,556,174,779 bytes I 18:30:46 Sectors: 3,201,259 I 18:30:46 Image Size: 6,556,745,728 bytes I 18:30:46 Image Sectors: 3,201,536 I 18:30:47 Operation Successfully Completed! - Duration: 00:00:07 W 18:30:49 User accepted disc space warning and is attempting to overburn! I 18:30:49 Operation Started! I 18:30:49 Source File: -==/\/[BUILD IMAGE]\/\==- I 18:30:49 Source File Sectors: 3,201,536 (MODE1/2048) I 18:30:49 Source File Size: 6,556,745,728 bytes I 18:30:49 Source File Volume Identifier: Realtracks & Realdrums5 I 18:30:49 Source File Volume Set Identifier: 509E93D40030D9F6 I 18:30:49 Source File Application Identifier: ImgBurn v2.5.8.0 I 18:30:49 Source File Implementation Identifier: ImgBurn I 18:30:49 Source File File System(s): UDF (1.02) I 18:30:49 Destination Device: [0:0:0] HL-DT-ST BD-RE BH10LS30 1.00 (E:) (SATA) I 18:30:49 Destination Media Type: DVD-RW (Disc ID: TDK502sakuM3) I 18:30:49 Destination Media Supported Write Speeds: 2x I 18:30:49 Destination Media Sectors: 2,298,496 I 18:30:49 Write Mode: DVD I 18:30:49 Write Type: DAO I 18:30:49 Write Speed: MAX I 18:30:49 Link Size: Auto I 18:30:49 Lock Volume: Yes I 18:30:49 Test Mode: No I 18:30:49 OPC: No I 18:30:49 BURN-Proof: Enabled I 18:30:49 Write Speed Successfully Set! - Effective: 2,770 KB/s (2x) E 18:31:00 Failed to Reserve Track! - Reason: Invalid Field in CDB E 18:31:02 Operation Failed! - Duration: 00:00:12 I 18:31:02 Average Write Rate: N/A - Maximum Write Rate: N/A I 18:31:25 Close Request Acknowledged I 18:31:25 Closing Down... I 18:31:26 Shutting down SPTI... I 18:31:26 ImgBurn closed! Link to comment Share on other sites More sharing options...
dbminter Posted April 30, 2020 Share Posted April 30, 2020 Interesting. It's not what I expected, but I think it's related. My guess is this: I 18:30:49 Destination Device: [0:0:0] HL-DT-ST BD-RE BH10LS30 1.00 (E:) (SATA) I 18:30:49 Destination Media Type: DVD-RW (Disc ID: TDK502sakuM3) What is probably the problem is your drive doesn't like that particular manufacture of DVD-RW brand. You might be able to fix this if there's a firmware update for your drive. In Write mode, right click on the target drive and choose the check for firmware update option, which should be at the bottom, I think. Update the firmware if there is one. These problems are caused by write strategy incompatibilities in the firmware of a drive and the kind of media being written to. Another thing to try is using a different rewritable disc. Try the Verbatim DataLife Plus brand you only find online. NOT the Life Series you find in brick and mortar stores. I've never used a TDK DVD-RW disc before. I do know they used to make a good DVD-R and their DVD+R DL were relatively error free from my experience. I use DVD+RW and haven't used any of my DVD-RW in a long time. The last thing to try is using a different burner. A different burner might have better luck with those discs than the one you currently have, the BH10LS30. I'm guessing from the HL-DT-ST part of the drive string name your BD burner is an LG. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 1, 2020 Share Posted May 1, 2020 You’re trying to burn too much to the disc. The program did warn you. Link to comment Share on other sites More sharing options...
itm Posted May 1, 2020 Author Share Posted May 1, 2020 OK so I followed dbminter's instructions to update the drive firmware, then rebooted. After the reboot everything was fine -thanks! I've been using the same DV-R/W media for 5+ years without any problems (am actually using discs from the same pack that I bought 5 years ago), so it didn't seem like a media compatibility issue. ??? Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 1, 2020 Share Posted May 1, 2020 That wasn't the issue. Quote I 18:30:46 Preparing Image... I 18:30:46 Contents: 4 Files, 1 Folder I 18:30:46 Content Type: Data I 18:30:46 Data Type: MODE1/2048 I 18:30:46 File System(s): UDF (1.02) I 18:30:46 Volume Label: Realtracks & Realdrums5 I 18:30:46 Size: 6,556,174,779 bytes I 18:30:46 Sectors: 3,201,259 I 18:30:46 Image Size: 6,556,745,728 bytes I 18:30:46 Image Sectors: 3,201,536 I 18:30:47 Operation Successfully Completed! - Duration: 00:00:07 W 18:30:49 User accepted disc space warning and is attempting to overburn! I 18:30:49 Operation Started! I 18:30:49 Source File: -==/\/[BUILD IMAGE]\/\==- I 18:30:49 Source File Sectors: 3,201,536 (MODE1/2048) I 18:30:49 Source File Size: 6,556,745,728 bytes I 18:30:49 Source File Volume Identifier: Realtracks & Realdrums5 I 18:30:49 Source File Volume Set Identifier: 509E93D40030D9F6 I 18:30:49 Source File Application Identifier: ImgBurn v2.5.8.0 I 18:30:49 Source File Implementation Identifier: ImgBurn I 18:30:49 Source File File System(s): UDF (1.02) I 18:30:49 Destination Device: [0:0:0] HL-DT-ST BD-RE BH10LS30 1.00 (E:) (SATA) I 18:30:49 Destination Media Type: DVD-RW (Disc ID: TDK502sakuM3) I 18:30:49 Destination Media Supported Write Speeds: 2x I 18:30:49 Destination Media Sectors: 2,298,496 That's why your drive errored out. You can't burn 6GiB of data to a 4.37GiB disc. Link to comment Share on other sites More sharing options...
dbminter Posted May 1, 2020 Share Posted May 1, 2020 Wow, I completely missed that! Yeah, even if you updated the firmware, you can't burn that image to a DVD-RW. Must have been a different image you got working that was small enough to fit on a DVD-RW. Overburning rarely works in my experience. Even if it's just a tiny amount. Link to comment Share on other sites More sharing options...
itm Posted May 1, 2020 Author Share Posted May 1, 2020 Sorry I think I must have uploaded the wrong section of the log. On one of my attempts to burn to the DVR I burned only a couple of the files, so that it would all fit onto the disc, but got that same error. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted May 1, 2020 Share Posted May 1, 2020 That log fitted with the screenshot in your original post. If you have another issue.... and you believe you aren't lacking in disc space, please post the log from that attempt at burning. We can only work with the info you provide Link to comment Share on other sites More sharing options...
dbminter Posted May 1, 2020 Share Posted May 1, 2020 Also, the posted log was to a DVD-RW but you indicate you got a burn working on a DVD-R. Burning to both kinds is different and involves different discs, so the DVD-R may have worked for a variety reasons unrelated to why the DVD-RW failed. Now, if you used this same DVD-RW that failed before for small files and worked later for small files after updating the firmware, then the firmware issue might have been the cause. Link to comment Share on other sites More sharing options...
itm Posted May 2, 2020 Author Share Posted May 2, 2020 To summarise...I was trying to write 4 files (large .exe files) to a 7GB DVD-R, from a half empty tub that I hadn't used for a few years. The first couple of burns failed, at which point I suspected that maybe the media had degraded while sat on the shelf (I had noticed some moisture on the discs which I needed to wipe off - I suspect this dated back to a leak in my study over a year ago). When the third burn failed I decided that I should try an alternative media, in case there was in fact a problem with the drive or software. So I tried burning the same files to a 4GB DVD-RW (forgetting that it had half the capacity of the DVD-R's). When I got the warning message about the capacity I tried again, but only burning two of the four files, so that they would fit on the disc. I got the same error that I had with the DVD-R's. At that point I posted my message here. Link to comment Share on other sites More sharing options...
Recommended Posts