Nodens Posted October 26, 2009 Share Posted October 26, 2009 Fails upon verification stage(disk can't be initialized at all) with Device Not Ready - Reason: Incompatible Medium Installed. Resulting disc is unusable (can't be initialized). This happens only with one specific image (tested with others) and only in Imgburn (last 2 versions tested). As testing-control, Ashampoo and Nero were used with DAO strategy, they both succeeded, resulting disc can be initialized and read properly. The image that fails is the beta of Fedora 12 x86_64 DVD and can be downloaded here: http://fedoraproject.org/get-prerelease Image checksums of the testing subject have been verified. No Upperfilters, Anydvd Lowerfilter but disabled. SPTD present v1.62. Tested 2 drives of the same model, latest firmware on both, same results. I will later test said image with a different drive (BenQ) and a couple of different media (depends on what I have at the lab). My guess is there is something strange with the image. I will try to investigate more if I find time. Log follows: ----------------------------------------- ; //****************************************\\ ; ImgBurn Version 2.5.0.0 - Log ; Δευτέρα, 26 Οκτώβριος 2009, 08:01:07 ; \\****************************************// ; ; I 07:27:28 ImgBurn Version 2.5.0.0 started! I 07:27:28 Microsoft Windows 7 Ultimate x64 Edition (6.1, Build 7600) I 07:27:28 Total Physical Memory: 8.387.116 KB - Available: 6.955.912 KB W 07:27:28 AnyDVD can interfere with ImgBurn's ability to verify accurately, please ensure it's disabled! W 07:27:28 SPTD can have a detrimental effect on drive performance. I 07:27:28 Initialising SPTI... I 07:27:28 Searching for SCSI / ATAPI devices... I 07:27:28 Found 2 DVD±RWs and 2 BD-ROM/HD DVD-ROMs! I 07:27:44 Operation Started! I 07:27:44 Source File: Z:\Azureus\Fedora-12-Beta-x86_64-DVD\Fedora-12-Beta-x86_64-DVD.iso I 07:27:44 Source File Sectors: 1.663.605 (MODE1/2048) I 07:27:44 Source File Size: 3.407.063.040 bytes I 07:27:44 Source File Volume Identifier: Fedora 12-Beta x I 07:27:44 Source File Application Identifier: GENISOIMAGE ISO 9660/HFS FILESYSTEM CREATOR © 1993 E.YOUNGDALE © 1997-2006 J.PEARSON/J.SCHILLING © 2006-2007 CDRKIT TEAM I 07:27:44 Source File Implementation Identifier: ISO MD5SUM = 3c6fe57ffb10b11a9f1e0c254cca2825;SKIPSECTORS = 15;RHLISOSTATUS=0;FRAGMENT SUMS = a6951ab38e35ccc7f52f8314d975d74aff8568652573f5a1751d5d858b21;FRAGMENT COUNT = 20;THIS IS NOT THE SAME AS RUNNING MD5SUM ON THIS ISO!! I 07:27:44 Source File File System(s): ISO9660 (Bootable); Joliet I 07:27:44 Destination Device: [1:0:0] ASUS DRW-1608P2 1.41 (D:) (ATA) I 07:27:44 Destination Media Type: DVD-R (Disc ID: OPTODISCR008) (Speeds: 4x; 6x; 8x) I 07:27:44 Destination Media Sectors: 2.297.888 I 07:27:44 Write Mode: DVD I 07:27:44 Write Type: DAO I 07:27:44 Write Speed: MAX I 07:27:44 Link Size: Auto I 07:27:44 Lock Volume: Yes I 07:27:44 Test Mode: No I 07:27:44 OPC: No I 07:27:44 BURN-Proof: Enabled I 07:27:45 Filling Buffer... (40 MB) I 07:27:46 Writing LeadIn... I 07:29:05 Writing Session 1 of 1... (1 Track, LBA: 0 - 1663604) I 07:29:05 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 1663604) I 07:39:26 Synchronising Cache... I 07:39:57 Exporting Graph Data... I 07:39:57 Graph Data File: C:\Users\nTT\AppData\Roaming\ImgBurn\Graph Data Files\ASUS_DRW-1608P2_1.41_ΔΕΥΤΈΡΑ-26-ΟΚΤΏΒΡΙΟς-2009_7-27_πμ_OPTODISCR008_MAX.ibg I 07:39:57 Export Successfully Completed! I 07:39:57 Operation Successfully Completed! - Duration: 00:12:13 I 07:39:57 Average Write Rate: 5.366 KB/s (3.9x) - Maximum Write Rate: 5.596 KB/s (4.0x) I 07:39:57 Cycling Tray before Verify... W 07:40:07 Waiting for device to become ready... W 07:40:49 Device Not Ready - Incompatible Medium Installed W 07:40:49 Retrying (1 of 3)... I 07:40:49 Cycling Tray before Verify... W 07:40:58 Waiting for device to become ready... W 07:41:51 Retry Failed - Reason: Incompatible Medium Installed W 07:41:51 Retrying (2 of 3)... I 07:41:51 Cycling Tray before Verify... W 07:42:02 Waiting for device to become ready... W 07:42:51 Retry Failed - Reason: Incompatible Medium Installed W 07:42:51 Retrying (3 of 3)... I 07:42:51 Cycling Tray before Verify... W 07:43:01 Waiting for device to become ready... W 07:43:56 Retry Failed - Reason: Incompatible Medium Installed E 07:44:00 Device Not Ready - Reason: Incompatible Medium Installed E 07:44:00 Operation Aborted! I 08:01:07 Close Request Acknowledged I 08:01:07 Closing Down... I 08:01:07 Shutting down SPTI... I 08:01:07 ImgBurn closed! Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 26, 2009 Share Posted October 26, 2009 This is a drive/firmware/media combo issue and nothing to do with the image or ImgBurn. If a drive can't initialise a disc it just burnt, *it* messed something up. ImgBurn has no actual control over what happens at burn time and I couldn't get it to make a coaster producing that error even if I tried. Link to comment Share on other sites More sharing options...
Nodens Posted October 26, 2009 Author Share Posted October 26, 2009 This is a drive/firmware/media combo issue and nothing to do with the image or ImgBurn. If a drive can't initialise a disc it just burnt, *it* messed something up. ImgBurn has no actual control over what happens at burn time and I couldn't get it to make a coaster producing that error even if I tried. Thanks for the fast reply. After further testing I'll have to agree with you. The reason I thought it was an ImgBurn issue with some non-standard/broken image (messed up TOC was something that came to mind) was because I had twin drives to test and because I thought Ashampoo/Nero discs were ok. Tested same media on BenQ drive with the same image, no errors. Went back to examine the disks that didn't fail with Ashampoo and Nero and, after careful examination, I noticed several bad sectors on both disks that surprisingly were not reported during verification by neither of these two applications. Further burns also exhibited random bad sector. While further burns with ImgBurn always resulted in a disc that could not be initialized. I have one question for you though. I do know that ImgBurn has no actual control of what happens at burn-time as it uses the SPTI layer etc,I have a fairly good understanding of how that works although it's far from my area of expertise. What I wanted to ask is if you have any idea on why the discs burned with ImgBurn always resulted to discs that could not be initialized while the ones burned with the other two applications resulted always in discs with random bad sectors. I find it somewhat peculiar. I've tested them all with DAO and if I'm not mistaken, Nero uses it's own ASPI layer which is really a SPTI wrapper (if I understand correctly) while Ashampoo uses SPTI directly much like Imgburn no? I'd like to know what you think as you are much more adept in this field. Thanks in advance, Nodens Link to comment Share on other sites More sharing options...
Recommended Posts