Tobim6 Posted Thursday at 03:10 PM Posted Thursday at 03:10 PM Hello I made an image of this cd-rw now im trying to write it back but im getting error ImgBurn.log
dbminter Posted Thursday at 03:32 PM Posted Thursday at 03:32 PM You're using the Mitsubishi good media, so it's not that, for a change. My only guess at this point is that your burner doesn't like that particular brand of media. Or the drive may have reached the end of its life or is defective. It's possible a firmware update for that drive might have fixed the incompatibility issue. In Write mode, right click on the drive letter for the target device and choose the last option in the drop down context menu that appears. Should say something like Check for firmware update.
Tobim6 Posted Thursday at 03:50 PM Author Posted Thursday at 03:50 PM I have another Verbatim CD-RW (the one thats not working is also Verbatim) and it writes perfectly fine. It is a 97m34s23f. My drive is updated to the latest firmware.
dbminter Posted Thursday at 03:56 PM Posted Thursday at 03:56 PM That seems to indicate it's most likely a compatibility issue. Your drive likes the 97m34s23f CD-RW but doesn't like the Mitsubishi CD-RW. Not much you can do if you're dead set on using the Mitsubishi CD-RW except try a different make, model, and manufacturer of burner drive. It's also possible the Mitsubishi disc came defective from the factory or its reached the end of its write cycle life.
dbminter Posted Thursday at 04:11 PM Posted Thursday at 04:11 PM But, they are two different beasts. Ultra Speed CD-RW are manufactured differently from standard CD-RW. So, even though Mitsubishi made both, they are not the same. And, for whatever reason, your drive is probably not liking one and liking the other. A firmware update would need to be made to fix that, but no one fixes firmware anymore. Firmware updates are only released for Ultra HD BD's anymore and those are only to shore up encryption vulnerabilities to prevent copying Ultra HD BD. NOT to address any performance issues. It also makes sense the standard CD-RW is working but the Ultra Speed one is not. The 2nd writes faster and therefore needs different firmware instructions to accommodate that. As you increase speeds in media, you get compatibility error increases, particularly as a drive gets older. BTW, can you still get those DataLife Plus Ultra Speed Verbatim CD-RW anymore? If you know of where I can get them, I'd be interested to know. I can only find some straggling Memorex Ultra Speed CD-RW on eBay. They're pretty good quality as far as I can tell, particularly for Memorex, which usually uses CMC crap, but apparently farmed out to Mitsubishi for their Ultra Speed CD-RW. At least, I've had no issues with the Memorex Ultra Speed CD-RW. Thanks!
Tobim6 Posted Thursday at 04:11 PM Author Posted Thursday at 04:11 PM Actually I just tried writing the image to the "good" cd-rw and it does the same. Does this mean its a bad image? Can I somehow dismiss this error and continue?
Tobim6 Posted Thursday at 04:13 PM Author Posted Thursday at 04:13 PM 1 minute ago, dbminter said: BTW, can you still get those DataLife Plus Ultra Speed Verbatim CD-RW anymore? If you know of where I can get them, I'd be interested to know. Unfortunately this is just an old disc I have. I don't know where to get them.
dbminter Posted Thursday at 04:36 PM Posted Thursday at 04:36 PM Generally, "bad" images don't result in bad burns. Meaning, there's very little data in a disc image that can result in a failed burn. Failed burns are the result of media issues, incompatibility between drive and media, or a dying/dead/defective drive. But, if you're curious and want to test it, you can create a new image in ImgBurn with some dummy data and then write that new image to these same CD-RW in the same drive. I would be willing to bet you'd probably get the same failure results, though. I was pretty sure you couldn't find those DataLife Plus Ultra Speed CD-RW anymore. I was just curious if you bought them new. Then, maybe I could, too. I don't think anyone manufactures Ultra Speed CD-RW anymore. Like how no one manufactures 8x DVD+RW anymore.
Tobim6 Posted Saturday at 11:00 PM Author Posted Saturday at 11:00 PM Hello I made an ISO with dummy data filling the entire disc and it burned all good
Tobim6 Posted Saturday at 11:04 PM Author Posted Saturday at 11:04 PM This is the image that fails burning. It seems like the error is at the LeadOut? What does it mean? What causes it?
dbminter Posted Saturday at 11:29 PM Posted Saturday at 11:29 PM Could be the multiple Sessions in the image file. I thought ImgBurn was unable to burn images with multiple Sessions. But, that may have been at some point in the past and that is a limitation that no longer applies.
dbminter Posted Saturday at 11:32 PM Posted Saturday at 11:32 PM If you've got a cloud account and want to up this image set to it and let me download it, I'll attempt to burn it on a CD-RW and see what happens on my end.
Tobim6 Posted yesterday at 11:33 AM Author Posted yesterday at 11:33 AM Only if you dont view my photos
dbminter Posted yesterday at 11:45 AM Posted yesterday at 11:45 AM Well, all you have to do is create a folder for that image file(s) and just give me access to that folder. In Google Drive and Microsoft One Drive, you have to give permissions to files and folders for others to view them. And if you create a subfolder somewhere there, you have to grant me permission to view that folder. And only files and subfolders in that folder you grant me permission to view can be viewed/downloaded by anyone else. Don't know how it is for DropBox or any other cloud solutions, though.
Tobim6 Posted yesterday at 11:58 AM Author Posted yesterday at 11:58 AM But theres my photos in the image
dbminter Posted yesterday at 12:07 PM Posted yesterday at 12:07 PM Oh, I'm sorry! I was under the impression this was an Audio CD. Unfortunately, I got my wires crossed with another post where someone had downloaded some Audio CD images that were causing write errors attempting to burn them. Yeah, I would be wary to give me access to something like that.
Tobim6 Posted yesterday at 12:16 PM Author Posted yesterday at 12:16 PM If you dont look at photos i can send it to you
dbminter Posted yesterday at 12:28 PM Posted yesterday at 12:28 PM I won't, but there's no guarantee there wont be unsecured cross talk and someone else can get access to your image. So, you're best off not posting a link in a reply here, but to send me a private message with the link to it.
dbminter Posted yesterday at 01:57 PM Posted yesterday at 01:57 PM I think @LIGHTNING UK! may have to chime in on this. I got a next writable address invalid message while attempting to write Session 1. Does ImgBurn support multiple Sessions? I seem to recall at one point in the past that it did not support multiple Sessions. Here's what I got attempting to write the image to a DVD+RW: --------------------------- ImgBurn --------------------------- Next Writable Address is Invalid! LBA: 83375 / 18:33:50 NWA: 0 / 00:02:00 --------------------------- OK --------------------------- As another test, I attempted to burn this image to a DVD+RW as I said above and got a message saying the Image track format was MODE1/2352 but the Image track format for DVD is MODE1/2048. I'm no expert but an odd format value of 2352 seems to just be wrong to me. I have to wonder if the image is incorrect somehow. --------------------------- ImgBurn --------------------------- Your image doesn't appear to be of the correct format for burning onto a DVD. Session 1, Track 1 Image track format: MODE1/2352 DVD track format: MODE1/2048 Would you like the program to convert the data to the correct format 'on-the-fly' as it is written? Note: The actual image file is not changed. --------------------------- Yes No --------------------------- I 08:52:31 Source File Sectors: 237,275 (MODE1/2352) I 08:52:31 Source File Size: 558,070,800 bytes I 08:52:31 Source File File System(s): ISO9660, Joliet I 08:52:31 Write Mode: DVD I 08:52:31 Write Type: DAO I 08:52:31 Write Speed: MAX I 08:52:31 Link Size: Auto I 08:52:31 Lock Volume: Yes I 08:52:31 Test Mode: No I 08:52:31 OPC: No I 08:52:31 BURN-Proof: Enabled I 08:52:34 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x) I 08:52:34 Filling Buffer... (40 MiB) I 08:52:34 Writing LeadIn... I 08:52:40 Writing Session 1 of 4... (1 Track, LBA: 0 - 83374) I 08:52:40 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 83374) I 08:53:00 Synchronising Cache... I 08:53:03 Closing Session... E 08:53:04 Next Writable Address is Invalid! E 08:53:04 LBA: 83375 / 18:33:50 E 08:53:04 NWA: 0 / 00:02:00 E 08:54:46 Failed to Write Image! E 08:54:49 Operation Failed! - Duration: 00:02:14
LIGHTNING UK! Posted yesterday at 06:17 PM Posted yesterday at 06:17 PM That sort of image can only be burnt to a cd. it looks like a data disc you’ve kept adding data too. put the disc in the drive and use Build mode to make a clean image from it. mount hat new image in a virtual drive program to check its all ok and then burn to a new disc.
dbminter Posted yesterday at 06:21 PM Posted yesterday at 06:21 PM The image can partially be burnt to DVD+RW. ImgBurn says it will do some conversions on the fly, but I'll retry on a CD-RW. I spoke with the OP via private message and they already tried Virtual CloneDrive per my suggestion. It's only displaying partial data, most likely from only one Session, either Session 1 or 4.
dbminter Posted yesterday at 06:42 PM Posted yesterday at 06:42 PM I just burned that image to a Memorex 24x Ultra High Speed Mitsubishi CD-RW without any errors. However, there were Verify miscompares: I 13:34:24 Operation Started! I 13:34:24 Source File Sectors: 237,275 (MODE1/2352) I 13:34:24 Source File Size: 558,070,800 bytes I 13:34:24 Source File File System(s): ISO9660, Joliet I 13:34:24 Destination Device: [0:0:0] ASUS BW-16D1HT 3.11 (R:) (USB 3.0) I 13:34:24 Destination Media Type: CD-RW (Disc ID: 97m34s24f, Mitsubishi Chemical Corp.) I 13:34:24 Destination Media Supported Write Speeds: 16x, 24x I 13:34:24 Destination Media Sectors: 359,847 I 13:34:24 Write Mode: CD I 13:34:24 Write Type: SAO I 13:34:24 Write Speed: MAX I 13:34:24 Lock Volume: Yes I 13:34:24 Test Mode: No I 13:34:24 OPC: No I 13:34:24 BURN-Proof: Enabled I 13:34:24 Write Speed Successfully Set! - Effective: 4,234 KB/s (24x) I 13:34:24 Filling Buffer... (40 MiB) I 13:34:24 Writing LeadIn... I 13:34:41 Writing Session 1 of 4... (1 Track, LBA: 0 - 83374) I 13:34:41 Writing Track 1 of 1... (MODE1/2352, LBA: 0 - 83374) I 13:35:49 Synchronising Cache... I 13:36:01 Filling Buffer... (40 MiB) I 13:36:01 Writing LeadIn... I 13:36:06 Writing Session 2 of 4... (1 Track, LBA: 94775 - 117377) I 13:36:06 Writing Track 1 of 1... (MODE1/2352, LBA: 94775 - 117377) I 13:36:18 Synchronising Cache... I 13:36:25 Filling Buffer... (40 MiB) I 13:36:25 Writing LeadIn... I 13:36:29 Writing Session 3 of 4... (1 Track, LBA: 124278 - 230074) I 13:36:29 Writing Track 1 of 1... (MODE1/2352, LBA: 124278 - 230074) I 13:37:27 Synchronising Cache... I 13:37:33 Filling Buffer... (40 MiB) I 13:37:33 Writing LeadIn... I 13:37:33 Writing Session 4 of 4... (1 Track, LBA: 236975 - 237274) I 13:37:34 Writing Track 1 of 1... (MODE2/FORM1/2352, LBA: 236975 - 237274) I 13:37:34 Synchronising Cache... I 13:37:45 Operation Successfully Completed! - Duration: 00:03:20 I 13:37:45 Average Write Rate: 3,162 KiB/s (18.4x) - Maximum Write Rate: 4,200 KiB/s (24.4x) I 13:37:45 Cycling Tray before Verify... W 13:37:58 Waiting for device to become ready... I 13:38:09 Device Ready! I 13:38:10 Operation Started! I 13:38:10 Source Device: [0:0:0] ASUS BW-16D1HT 3.11 (R:) (USB 3.0) I 13:38:11 Source Media Type: CD-RW (Disc ID: 97m34s24f, Mitsubishi Chemical Corp.) I 13:38:11 Source Media Supported Read Speeds: 4x, 8x, 10x, 16x, 24x, 32x, 40x I 13:38:11 Source Media Supported Write Speeds: 16x, 24x I 13:38:11 Source Media Sectors: 237,275 I 13:38:11 Source Media Size: 485,939,200 bytes I 13:38:11 Image File Sectors: 237,275 (MODE1/2352) I 13:38:11 Image File Size: 558,070,800 bytes I 13:38:11 Image File Volume Identifier: NEW I 13:38:11 Image File Volume Set Identifier: NEW I 13:38:11 Image File File System(s): ISO9660, Joliet I 13:38:11 Read Speed (Data/Audio): MAX / MAX I 13:38:13 Read Speed - Effective: 40x I 13:38:13 Verifying Session 1 of 4... (1 Track, LBA: 0 - 83374) I 13:38:13 Verifying Track 1 of 1... (MODE1/2352, LBA: 0 - 83374) W 13:39:26 Miscompare at LBA: 83373, Offset: 2064 W 13:39:26 Device: 0xAC W 13:39:26 Image File: 0x00 W 13:39:26 Total Errors in Sector: 52 W 13:39:26 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:26 Verifying Sectors... W 13:39:27 Miscompare at LBA: 83374, Offset: 2064 W 13:39:27 Device: 0x3D W 13:39:27 Image File: 0x00 W 13:39:27 Total Errors in Sector: 52 W 13:39:27 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:27 Verifying Sectors... I 13:39:27 Verifying Session 2 of 4... (1 Track, LBA: 94775 - 117377) I 13:39:27 Verifying Track 1 of 1... (MODE1/2352, LBA: 94775 - 117377) W 13:39:48 Miscompare at LBA: 117376, Offset: 2064 W 13:39:48 Device: 0x8D W 13:39:48 Image File: 0x00 W 13:39:48 Total Errors in Sector: 52 W 13:39:48 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:48 Verifying Sectors... W 13:39:48 Miscompare at LBA: 117377, Offset: 2064 W 13:39:48 Device: 0x3E W 13:39:48 Image File: 0x00 W 13:39:48 Total Errors in Sector: 52 W 13:39:48 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:39:48 Verifying Sectors... I 13:39:48 Verifying Session 3 of 4... (1 Track, LBA: 124278 - 230074) I 13:39:48 Verifying Track 1 of 1... (MODE1/2352, LBA: 124278 - 230074) W 13:40:34 Miscompare at LBA: 230073, Offset: 2064 W 13:40:34 Device: 0xF3 W 13:40:34 Image File: 0x00 W 13:40:34 Total Errors in Sector: 52 W 13:40:34 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:40:37 Verifying Sectors... W 13:40:38 Miscompare at LBA: 230074, Offset: 2064 W 13:40:38 Device: 0x62 W 13:40:38 Image File: 0x00 W 13:40:38 Total Errors in Sector: 52 W 13:40:38 Note: The drive probably corrected the EDC Area because it's wrong in the image file. I 13:40:38 Verifying Sectors... I 13:40:38 Verifying Session 4 of 4... (1 Track, LBA: 236975 - 237274) I 13:40:38 Verifying Track 1 of 1... (MODE2/FORM1/2352, LBA: 236975 - 237274) I 13:40:43 Operation Successfully Completed! - Duration: 00:02:27 I 13:40:43 Average Verify Rate: 3,758 KiB/s (21.8x) - Maximum Verify Rate: 11,969 KiB/s (69.5x)
Tobim6 Posted 3 hours ago Author Posted 3 hours ago So sad that this thread is incomplete because you can do only 5 replies per day
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now