Thaepicasian Posted October 3, 2012 Posted October 3, 2012 (edited) Lately, I've been trying to burn xbox 360 backups, but every single time I try, Imgburn shows a scsistatus 0x02 error at around 50%. I would post the error text, but I would not like to waste a perfectly good DL disc is not necessary (Unless there is a way to check that without wasting another disc...?). I've already searched through many Imgburn forums concerning this issue, yet I still could not find my answer. I am not very experienced with this program, so if my question is stupid, I apologize. Is there any solution? Can anyone please explain this problem to me? Family tree: ACPI x64-based PC Microsoft ACPI-Compliant System PCI bus Intel® 5 Series 6 Port SATA AHCI Controller (Ven_8086&DEV_3B2F - Intel - iaStorA - v7.0.0.1013 Cd_Rom Drive (TSSTcorp DVD+-RW TS-L633C SCSI CdRom Device) (Bus Number 1, Target Id 0, LUN 0) Disc: Verbatim DVD+R DL 2.4x Here is the log: I 19:30:51 ImgBurn Version 2.5.7.0 started! I 19:30:51 Microsoft Windows 7 Home Premium x64 Edition (6.1, Build 7600) I 19:30:51 Total Physical Memory: 3,985,944 KB - Available: 2,423,428 KB I 19:30:51 Initialising SPTI... I 19:30:51 Searching for SCSI / ATAPI devices... I 19:30:51 -> Drive 1 - Info: TSSTcorp DVD+-RW TS-L633C DW50 (D:) (SATA) I 19:30:51 Found 1 DVD±RW/RAM! I 19:41:03 Operation Started! I 19:41:03 Source File: C:\Users\Dylan\Desktop\Games\Xbox 360 Games\Resident Evil 5\R-45447-999-63-2.dvd I 19:41:03 Source File Sectors: 3,825,924 (MODE1/2048) I 19:41:03 Source File Size: 7,835,492,352 bytes I 19:41:03 Source File Volume Identifier: XGD2DVD_NTSC I 19:41:03 Source File Volume Set Identifier: 34672923 I 19:41:03 Source File Implementation Identifier: Sonic Scenarist 3.1 I 19:41:03 Source File File System(s): ISO9660, UDF (1.02) I 19:41:03 Destination Device: [0:0:0] TSSTcorp DVD+-RW TS-L633C DW50 (D:) (SATA) I 19:41:03 Destination Media Type: DVD+R DL (Disc ID: MKM-001-00) I 19:41:03 Destination Media Supported Write Speeds: 2.4x I 19:41:03 Destination Media Sectors: 4,173,824 I 19:41:03 Write Mode: DVD I 19:41:03 Write Type: DAO I 19:41:03 Write Speed: MAX I 19:41:03 DVD+R DL Reserve Track: No I 19:41:03 Link Size: Auto I 19:41:03 Lock Volume: Yes I 19:41:03 Test Mode: No I 19:41:03 OPC: No I 19:41:03 BURN-Proof: Enabled W 19:41:03 Write Speed Miscompare! - MODE SENSE: 2,770 KB/s (2x), GET PERFORMANCE: 3,324 KB/s (2.4x) I 19:41:03 Write Speed Successfully Set! - Effective: 3,324 KB/s (2.4x) I 19:41:03 Book Type Setting: DVD-ROM I 19:41:03 Optimal L0 Data Zone Capacity: 1,913,760 I 19:41:03 Optimal L0 Data Zone Method: Copied From Original Disc I 19:54:28 Set L0 Data Zone Capacity Succeeded! I 19:54:29 Filling Buffer... (80 MB) I 19:54:30 Writing LeadIn... I 19:54:32 Writing Session 1 of 1... (1 Track, LBA: 0 - 3825923) I 19:54:32 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3825923) I 19:54:32 Writing Layer 0... (LBA: 0 - 1913759) W 20:15:39 Failed to Write Sectors 1803616 - 1803647 - Reason: Write Error W 20:15:39 Retrying (1 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (2 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (3 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (4 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (5 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (6 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (7 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (8 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (9 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (10 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (11 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (12 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (13 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (14 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (15 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (16 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (17 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (18 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (19 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:39 Retrying (20 of 20)... W 20:15:39 Retry Failed - Reason: Invalid Address For Write W 20:15:47 Retrying (21)... W 20:15:47 Retry Failed - Reason: Invalid Address For Write W 20:15:47 Retrying (22)... W 20:15:47 Retry Failed - Reason: Invalid Address For Write W 20:15:47 Retrying (23)... W 20:15:47 Retry Failed - Reason: Invalid Address For Write W 20:15:47 Retrying (24)... W 20:15:47 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (25)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (26)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (27)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (28)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (29)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:48 Retrying (30)... W 20:15:48 Retry Failed - Reason: Invalid Address For Write W 20:15:49 Retrying (31)... W 20:15:49 Retry Failed - Reason: Invalid Address For Write W 20:15:49 Retrying (32)... W 20:15:49 Retry Failed - Reason: Invalid Address For Write W 20:15:49 Retrying (33)... W 20:15:49 Retry Failed - Reason: Invalid Address For Write W 20:15:50 Retrying (34)... W 20:15:50 Retry Failed - Reason: Invalid Address For Write W 20:15:50 Retrying (35)... W 20:15:50 Retry Failed - Reason: Invalid Address For Write W 20:15:50 Retrying (36)... W 20:15:50 Retry Failed - Reason: Invalid Address For Write W 20:15:51 Retrying (37)... W 20:15:51 Retry Failed - Reason: Invalid Address For Write W 20:15:51 Retrying (38)... W 20:15:51 Retry Failed - Reason: Invalid Address For Write W 20:15:51 Retrying (39)... W 20:15:51 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (40)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (41)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (42)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (43)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (44)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:52 Retrying (45)... W 20:15:52 Retry Failed - Reason: Invalid Address For Write W 20:15:53 Retrying (46)... W 20:15:53 Retry Failed - Reason: Invalid Address For Write W 20:15:53 Retrying (47)... W 20:15:53 Retry Failed - Reason: Invalid Address For Write E 20:20:14 Failed to Write Sectors 1803616 - 1803647 - Reason: Write Error E 20:20:14 Next Writable Address: 1802944 I 20:20:15 Synchronising Cache... W 20:20:17 User opted to skip the 'Close Track/Session/Disc' functions. E 20:20:17 Failed to Write Image! I 20:20:17 Exporting Graph Data... I 20:20:17 Graph Data File: C:\Users\Dylan\AppData\Roaming\ImgBurn\Graph Data Files\TSSTcorp_DVD+-RW_TS-L633C_DW50_OCTOBER-02-12_7-41_PM_MKM-001-00_MAX.ibg I 20:20:17 Export Successfully Completed! E 20:20:17 Operation Failed! - Duration: 00:39:14 I 20:20:17 Average Write Rate: 2,339 KB/s (1.7x) - Maximum Write Rate: 3,430 KB/s (2.5x) Edited October 3, 2012 by Thaepicasian
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 (edited) PS: I am willing to give any extra info that you may need to identify the problem. Edited October 3, 2012 by Thaepicasian
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 Your drive is having trouble writing to the discs and is reporting a 'Write Error' when it attempts to do so. Try another spindle of discs. Try cleaning the drive with a cleaning disc. If all else fails, use/buy another drive.
Adrianvdh Posted October 3, 2012 Posted October 3, 2012 Try writing the XGD2 title at 2.4x or 4x speed
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 The only option this person has is 2.4x and obviously as that's the only option, they're already using it. Please don't comment unless you actually know what you're talking about, you'll only confuse people.
Adrianvdh Posted October 3, 2012 Posted October 3, 2012 (edited) Dont tase me Bro! I do alot of XGD2 and XGD3 backup. But i know what im talking about Edited October 3, 2012 by Adrianvdh
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 I'll get a medal in the post to you asap.
Adrianvdh Posted October 3, 2012 Posted October 3, 2012 (edited) Thanks... Announcement :: Medal of Honor !! Edited October 3, 2012 by Adrianvdh
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Try writing the XGD2 title at 2.4x or 4x speed Thank you for the suggestion, but alas, I do not have that choice. Your drive is having trouble writing to the discs and is reporting a 'Write Error' when it attempts to do so. Try another spindle of discs. Try cleaning the drive with a cleaning disc. If all else fails, use/buy another drive. I will try cleaning my drive and burn again (If it fails, I will post again with the error dialogue). My budget is small, so I would like to keep purchasing other items as a last resort. I would like to clarify something though. Every time I tried, the burn would stop dead at exactly 47%. This thought is based off my extremely limited knowledge, but I don't believe problems such as an unclean drive would be so exact. Are there any technical problems that I must address? If anyone has any other solutions while I attempt burning the disc again, I would be grateful if you took the time to suggest it. Thanks.
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 When you're talking about writing to over 4 million sectors, 47% actually covers quite a range If you don't have other supplies (media) to test with, it's very hard to rule stuff out.
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Would burning 8gb of songs to a disc be a reasonable test? Would that help determine the problem? Frankly, this is the first time I've tried burning DL discs...
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 It's not what you're burning that's the problem here, so changing that doesn't make any difference. You need to test with different discs (that's what I meant by supplies/media). Some other Verbatim 2.4x MKM-001-00's would do... or even some Verbatim 8x MKM-003-00's. The ones made in Singapore seem to be the best - check the label on the tub.
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 (edited) Although I never checked before, it seems I do have the ones made in Singapore. Also, I'm sorry that I'm giving info bit by bit, but my CD Drive isn't the newest firmware according to the site that Imgburn connects to. When I try to update though, the updater says that it can't find the F/W, which I think is firmware, but I'm really not sure. Would that be a problem? Sorry, my bad. It says that it can't find the suitable drive for the F/W. Edited October 3, 2012 by Thaepicasian
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Another thing! I just realized this now, but when I burn, I use a program called "GameBooster" while burning to speed up my computer. Basically, it shuts down unnecessary services/processes for gaming, but it works fine for general use too. Do you think that could be the problem?
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 You can't just go by the dates of the firmware on Firmware HQ... at least not if you've got a slimline drive in a laptop. Different manufacturers have different firmware version naming schemes. Yours is DW50, so the next would probably be DW60 or something - whereas the newest one listed on Firmware HQ is totally different. No, GameBooster isn't the problem.
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Will updating the firmware help at all?
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 Well, it might have, but there aren't any available for your drive. That was the first thing I checked once I'd looked at the log in your initial post. You aren't the first person I've helped you know
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Aha, oops! Okay, so I've cleaning it (To the best of my ability), and now I'm going to start burning again. Any other steps if that fails?
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 You were meant to use a cleaning disc... then your 'ability' doesn't come into it Any other steps if that fails? Only what I said in post #3
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 *Sigh* Another fail. This time though, I got the error text! Device: [0:0:0] TSSTcorp DVD+-RW TS-L633C Dw50 (D:) (SATA) ScsiStatus: 0x02 Interpretation: Check Condition CDB: 2A 00 00 1B85 60 00 00 20 00 Interpretation: Write (10) - Sectors: 1803616 - 1803647 Sense Area: 71 00 03 00 00 00 00 0A 00 00 00 00 0C 00 00 00 00 00 SK InterpretationL Medium Error ASC/ASCQ Interpretation: Write Error I would also like to note that when 47% came around, it stopped burning and make a weird clicking noise. Then, when the error came up, my computers fan went into overdrive. I'm not entirely sure if that's normal.
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 That's *exactly* the same LBA it failed at last time (well, in your first log). Unless the whole spindle/batch has a defect in that position, it's probably your drive that's at fault.
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 Ah well, I tried without purchasing other supplies. Guess I have no choice. Thanks for the help (Even with my stupidity!)!
Thaepicasian Posted October 3, 2012 Author Posted October 3, 2012 One last thing, is there any external disc drives that you would recommend for this situation?
LIGHTNING UK! Posted October 3, 2012 Posted October 3, 2012 I don't really follow the external drive market, sorry. If I had to buy one, I wouldn't! Instead, I'd get a generic 5.25" USB 2.0/eSATA (or just USB 3.0) enclosure and stick a standard half height drive in it.
Recommended Posts