Phacin8 Posted April 19, 2010 Share Posted April 19, 2010 (edited) Hi all, just been reading through some of the posts on this forum, there seems to be a great support network here! Anyway, here goes with my issue, kinda curious I think: Got an old PC built for me, mainly for the purposes of burning dual layer disks and archiving my DVD collection. So I burn a 360 backup (from a known good source, with multiple reports of a successful burn) and the process all goes well until it fails closing the disc (never happened to me before on disc closing, so scratching my head a bit). This in itself not such a problem, burns go bad occasionally, that's life. However, since that burn failure, every time I try and burn this or another backup (again, known good sources), the burn will fail writing the lead in (sits there for over an hour, and actually locks the machine) or comes up instantly with power calibration errors. I'm using datawrite yellow disks (have had many successful burns with these disks on other hardware platforms) but the first thing I came across online was substandard media will always give you issues. So, despite a 90%+ success rate with the datawrite yellows, I went and forked out for some verbatim dual layers. I still have the same issue where I can't even get the burn started. At this stage I'm thinking either OS related, or hardware (burner) related. The first thing I do is try and update my drive firmware, which I did successfully, but didn't help my burning situation. At this point, I've still not narrowed down any further. OK so far, pretty run of the mill problem, seen many people suffer from it across many forums, any the only piece of advise I've seen which I've not tried, is to clean the drive/laser. What makes this strage (in my eyes) is that exactly the same happened on a completely different hardware setup. My main machine is a unibody macbook pro, which I boot camped and put xp and imgburn on. So I try the datawrite yellows again first, using a completely different backup (again from a known good source). Straight away I get the power calibration issue, so I switch to the verbatim discs. Instant improvement, disc starts burning, no problem, except, disc fails to close, and (as you may well guess) I can't start another burn, I just get power calibration issues, whether its datawrites or verbatims I use. I'm fairly sure the firmware is up to date, but can't be so sure on the Mac. Very curious how both hardware setups failed closing on their first burn, and now won't burn anything since. I'm fairly confident it's not hardware, as this has happened on 2 completely different set ups. I'm fairly confident it's not software, as both instances of windows were newly installed just for the purpose of trying out this burning process. Both OSs were xp sp3, running the latest version of image burn. I'm fairly confident it's not drive firmware, as I know one is up to date and still doesn't work, and the drives are completely different (one a slot loader, one a tray loader). I'm pretty confident it's not bad media because I'm using discs that I've had lots of previous success with, and when that failed I tried the seemingly most popular discs in verbatim. I'm also fairly confident that it's not the backups, they come from known good sources, and the two backups in question have had several reports of good burns. A last piece of info is that I've also tried different speeds (1x 2.4x and 4x) in all scenarios too, with no success. So that's a lots of fairly confidents, and really no idea as to whats going on. I've tried to cover most bases but truely I'm stumped now. It's just strange how both systems failed closing a disc on their first burn and won't burn anything since. I'm probably missing something terribly stupid or obvious. I can't believe both drives went bad at the same time, and I can't believe both got dirty at exactly the same time. It's more a possibility with the dirty lens, which is my next port of call. However, I'm greatful for any ideas. I've not posted any logs or specific specs up because of the complexity of my situation and the very fact that the sequence of events points to something ridiculous I'm (not) doing. Many many thanks if you've got this far down this long old post, and any suggestions are very greatly appreciated. *deep breath* Edited April 19, 2010 by Phacin8 Link to comment Share on other sites More sharing options...
mmalves Posted April 19, 2010 Share Posted April 19, 2010 The logs are useful in all situations so post yours. Link to comment Share on other sites More sharing options...
eSkRo Posted April 19, 2010 Share Posted April 19, 2010 Make sure you include a copy of the program's log in your post. No log = Link to comment Share on other sites More sharing options...
Phacin8 Posted April 20, 2010 Author Share Posted April 20, 2010 Make sure you include a copy of the program's log in your post. No log = Thanks for the update, here is the latest log of my attempt on my MacBook Pro using bootcamp: I 16:35:57 ImgBurn Version 2.5.1.0 started! I 16:35:57 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 3) I 16:35:57 Total Physical Memory: 1,089,000 KB - Available: 699,132 KB W 16:36:01 Drive Y:\ (FAT32) might not support single files > 4 GB in size. I 16:36:01 Initialising SPTI... I 16:36:01 Searching for SCSI / ATAPI devices... I 16:36:02 -> Drive 1 - Info: MATSHITA DVD-R UJ-868 KB19 (D:) (ATA) I 16:36:02 Found 1 DVD±RW! I 16:37:48 Operation Started! I 16:37:48 Source File: *** I 16:37:48 Source File Sectors: 3,827,520 (MODE1/2048) I 16:37:48 Source File Size: 7,838,760,960 bytes I 16:37:48 Source File Volume Identifier: DVD_ROM I 16:37:48 Source File Volume Set Identifier: ec67c000MS UDFBridge I 16:37:48 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM) I 16:37:48 Source File Implementation Identifier: Microsoft CDIMAGE UDF I 16:37:48 Source File File System(s): ISO9660, UDF (1.50) I 16:37:48 Destination Device: [1:0:0] MATSHITA DVD-R UJ-868 KB19 (D:) (ATA) I 16:37:48 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00) (Speeds: 2.4x, 4x) I 16:37:48 Destination Media Sectors: 4,173,824 I 16:37:48 Write Mode: DVD I 16:37:48 Write Type: DAO I 16:37:48 Write Speed: 4x I 16:37:48 Link Size: Auto I 16:37:48 Lock Volume: Yes I 16:37:48 Test Mode: No I 16:37:48 OPC: No I 16:37:48 BURN-Proof: Enabled I 16:37:48 Write Speed Successfully Set! - Effective: 5,540 KB/s (4x) I 16:37:48 Optimal L0 Data Zone Capacity: 1,913,760 I 16:37:48 Optimal L0 Data Zone Method: Copied From Original Disc W 16:38:48 Set L0 Data Zone Capacity Failed! - Reason: Power Calibration Area Error W 16:38:48 Retrying (1)... W 16:38:49 Retry Failed - Reason: Invalid Field in CDB W 16:38:49 Retrying (2)... W 16:38:52 Retry Failed - Reason: Invalid Field in CDB W 16:38:52 Retrying (3)... W 16:38:52 Retry Failed - Reason: Invalid Field in CDB W 16:38:52 Retrying (4)... W 16:38:53 Retry Failed - Reason: Invalid Field in CDB W 16:38:53 Retrying (5)... W 16:38:54 Retry Failed - Reason: Invalid Field in CDB W 16:38:54 Retrying (6)... W 16:38:54 Retry Failed - Reason: Invalid Field in CDB W 16:38:54 Retrying (7)... W 16:38:55 Retry Failed - Reason: Invalid Field in CDB W 16:38:55 Retrying (8)... W 16:38:55 Retry Failed - Reason: Invalid Field in CDB W 16:38:55 Retrying (9)... W 16:38:55 Retry Failed - Reason: Invalid Field in CDB W 16:38:55 Retrying (10)... W 16:38:56 Retry Failed - Reason: Invalid Field in CDB W 16:38:56 Retrying (11)... W 16:38:56 Retry Failed - Reason: Invalid Field in CDB W 16:38:56 Retrying (12)... W 16:38:57 Retry Failed - Reason: Invalid Field in CDB W 16:38:57 Retrying (13)... W 16:38:58 Retry Failed - Reason: Invalid Field in CDB W 16:38:58 Retrying (14)... W 16:38:58 Retry Failed - Reason: Invalid Field in CDB W 16:38:58 Retrying (15)... W 16:38:59 Retry Failed - Reason: Invalid Field in CDB W 16:38:59 Retrying (16)... W 16:38:59 Retry Failed - Reason: Invalid Field in CDB W 16:38:59 Retrying (17)... W 16:39:00 Retry Failed - Reason: Invalid Field in CDB W 16:39:00 Retrying (18)... W 16:39:00 Retry Failed - Reason: Invalid Field in CDB W 16:39:00 Retrying (19)... W 16:39:01 Retry Failed - Reason: Invalid Field in CDB W 16:39:01 Retrying (20)... W 16:39:01 Retry Failed - Reason: Invalid Field in CDB W 16:39:01 Retrying (21)... W 16:39:02 Retry Failed - Reason: Invalid Field in CDB W 16:39:02 Retrying (22)... W 16:39:02 Retry Failed - Reason: Invalid Field in CDB W 16:39:02 Retrying (23)... W 16:39:02 Retry Failed - Reason: Invalid Field in CDB W 16:39:02 Retrying (24)... W 16:39:03 Retry Failed - Reason: Invalid Field in CDB W 16:39:03 Retrying (25)... W 16:39:03 Retry Failed - Reason: Invalid Field in CDB W 16:39:03 Retrying (26)... W 16:39:03 Retry Failed - Reason: Invalid Field in CDB W 16:39:03 Retrying (27)... W 16:39:03 Retry Failed - Reason: Invalid Field in CDB W 16:39:03 Retrying (28)... W 16:39:04 Retry Failed - Reason: Invalid Field in CDB W 16:39:04 Retrying (29)... W 16:39:04 Retry Failed - Reason: Invalid Field in CDB W 16:39:04 Retrying (30)... W 16:39:04 Retry Failed - Reason: Invalid Field in CDB W 16:39:04 Retrying (31)... W 16:39:04 Retry Failed - Reason: Invalid Field in CDB W 16:39:04 Retrying (32)... W 16:39:04 Retry Failed - Reason: Invalid Field in CDB W 16:39:04 Retrying (33)... W 16:39:05 Retry Failed - Reason: Invalid Field in CDB W 16:39:05 Retrying (34)... W 16:39:05 Retry Failed - Reason: Invalid Field in CDB W 16:39:05 Retrying (35)... W 16:39:05 Retry Failed - Reason: Invalid Field in CDB W 16:39:05 Retrying (36)... W 16:39:05 Retry Failed - Reason: Invalid Field in CDB W 16:39:05 Retrying (37)... E 16:39:11 Set L0 Data Zone Capacity Failed! - Reason: Invalid Field in CDB E 16:39:11 Operation Failed! - Duration: 00:01:23 I 16:39:11 Average Write Rate: N/A - Maximum Write Rate: N/A Link to comment Share on other sites More sharing options...
Phacin8 Posted April 20, 2010 Author Share Posted April 20, 2010 Just a quick update in the interest in providing as much info as possible, also this afternoon I have set a backup trying to write on my original rig, and it is currently 1hr 36in, and the last message in the log is Writing LeadIn... Just to reiterate, I have two hardware rigs, both failed their first write, failing to close the disc. Ever since, neither set up will get past the Writing LeadIn stage, either hangs there, or comes straight up at the start of a burn with power calibration issues. Using nothing but Verbatim discs now, still no joy. Any help greatly appreciated. Link to comment Share on other sites More sharing options...
eSkRo Posted April 20, 2010 Share Posted April 20, 2010 (edited) If you receive the "Power calibration error"error message, the cause will be either poor media, poor power, or a defective recorder. Please try the following solutions: Update the firmware of your recorder. Try another brand media. Verbatim is best for Xbox360 games your backing up Try different power connectors, and for recorders, do not share power with other devices. It needs its own power connector. Try different configurations, have the recorder connected to the secondary IDE bus as master. Send the recorder in for service. Edited April 20, 2010 by eSkRo Link to comment Share on other sites More sharing options...
Phacin8 Posted April 20, 2010 Author Share Posted April 20, 2010 If you receive the "Power calibration error"error message, the cause will be either poor media, poor power, or a defective recorder. Please try the following solutions: Update the firmware of your recorder. Try another brand media. Try different power connectors, and for recorders, do not share power with other devices. It needs its own power connector. Try different configurations, have the recorder connected to the secondary IDE bus as master. Send the recorder in for service. Hi eSkRo, thank you for your sensible suggestions. As you will see form the first post, I have tried different media, both types I have had past success with. The recorder in the original rig was the secondary IDE master with another DVD recorder on the secondary slave. Common sense dictating that the drive might not be getting enough power, I pulled the power from the slave burner, so that it was the only device on that channel and power rail. Those are the only two IDE devices in my rig, therefore I have also tried swapping over to the primary IDE channel, with the same results. So, I come to the same conclusion as your good self, in that it's probably a burner issue. Not a problem, it's cheap enough to get another one these days, mught even opt for an external so I can plug in to my MBP from time to time... However, the reason for my post is down to the manner of failure, in exactly the same way, on two completely different hardware rigs, in that, the very first disc I tried burning on both rigs, failed on closing the disc, now neither rig will get any further than Writing LeadIn. If it was just the PC tower with this issue, I'd have already ordered a new burner by now, its just the way that two different hardware rigs failed in exactly the same manner after failing to close their very first burn that I can't get my head around. I mean, it's of course possible, but really, for both drives to go down in such a manner? I guess I'm just looking for suggestions to this curious issue because I just can't bring myself to believe that it's just coincidence that I have now two DL drives that won't burn DLs any more. I'm not for one second suggesting that ImgBurn has anything to do with this failure, I'm quite a techy person, and am genuinely inquisitive when stuff like this happens. Many thanks in advance for your help. Link to comment Share on other sites More sharing options...
eSkRo Posted April 20, 2010 Share Posted April 20, 2010 mught even opt for an external Dont buy Slim ones,,, their dirty cheap and you'll get mad again,,,, As you will see form the first post, I have tried different media, both types I have had past success with Maybe, but here's why --> http://forum.imgburn.com/index.php?showtopic=8000 Link to comment Share on other sites More sharing options...
Recommended Posts