Jump to content

Recommended Posts

Posted

Hey guys, thanks for giving me a few seconds of your time to help me figure out this benign issue that i haven't had to deal with ever before. I have gone through 7 verbatim discs just to burn 1 backup iso. So that is the biggest frustrating factor considering verbs are not cheap! Here is my log, i get to about %30 and it gives me this error.

 

 

 

 

I 12:58:33 ImgBurn Version 2.5.7.0 started!

I 12:58:33 Microsoft Windows 7 Ultimate Edition (6.1, Build 7601 : Service Pack 1)

I 12:58:33 Total Physical Memory: 2,095,160 KB - Available: 1,206,448 KB

I 12:58:33 Initialising SPTI...

I 12:58:33 Searching for SCSI / ATAPI devices...

I 12:58:38 -> Drive 1 - Info: LITEON CD-ROM LTN486S YUS6 (D:) (ATA)

I 12:58:38 -> Drive 2 - Info: HP DVD Writer 1270t CH23 (E:) (RAID)

I 12:58:38 Found 1 CD-ROM and 1 DVD±RW/RAM!

I 12:59:57 Operation Started!

I 12:59:57 Source File: C:\Users\Richard\Desktop\360 isos\SH775477-754.dvd

I 12:59:57 Source File Sectors: 3,827,488 (MODE1/2048)

I 12:59:57 Source File Size: 7,838,695,424 bytes

I 12:59:58 Source File Volume Identifier: 13599

I 12:59:58 Source File Volume Set Identifier: ceee8000MS UDFBridge

I 12:59:58 Source File Application Identifier: CDIMAGE 2.45 (12/06/2000 TM)

I 12:59:58 Source File Implementation Identifier: Microsoft CDIMAGE UDF

I 12:59:58 Source File File System(s): ISO9660, UDF (1.50)

I 12:59:58 Destination Device: [2:0:0] HP DVD Writer 1270t CH23 (E:) (RAID)

I 12:59:58 Destination Media Type: DVD+R DL (Disc ID: MKM-003-00)

I 12:59:58 Destination Media Supported Write Speeds: 4x, 6x, 8x

I 12:59:58 Destination Media Sectors: 4,173,824

I 12:59:58 Write Mode: DVD

I 12:59:58 Write Type: DAO

I 12:59:58 Write Speed: 8x

I 12:59:58 DVD+R DL Reserve Track: No

I 12:59:58 Link Size: Auto

I 12:59:59 Lock Volume: Yes

I 12:59:59 Test Mode: No

I 12:59:59 OPC: No

I 12:59:59 BURN-Proof: Enabled

I 12:59:59 Write Speed Successfully Set! - Effective: 11,080 KB/s (8x)

I 12:59:59 User Specified L0 Data Zone Capacity: 1,913,760

I 13:00:41 Set L0 Data Zone Capacity Succeeded!

I 13:00:42 Filling Buffer... (80 MB)

I 13:00:44 Writing LeadIn...

I 13:00:46 Writing Session 1 of 1... (1 Track, LBA: 0 - 3827487)

I 13:00:46 Writing Track 1 of 1... (MODE1/2048, LBA: 0 - 3827487)

I 13:00:46 Writing Layer 0... (LBA: 0 - 1913759)

W 13:04:22 Failed to Write Sectors 586656 - 586687 - Reason: Logical Unit Communication Time-Out

W 13:04:22 Retrying (1 of 20)...

W 13:04:26 Retry Failed - Reason: Invalid Address For Write

W 13:04:26 Retrying (2 of 20)...

W 13:04:26 Retry Failed - Reason: Invalid Address For Write

W 13:04:26 Retrying (3 of 20)...

W 13:04:26 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (4 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (5 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (6 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (7 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (8 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (9 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (10 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (11 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (12 of 20)...

W 13:04:27 Retry Failed - Reason: Invalid Address For Write

W 13:04:27 Retrying (13 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (14 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (15 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (16 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (17 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (18 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (19 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:04:28 Retrying (20 of 20)...

W 13:04:28 Retry Failed - Reason: Invalid Address For Write

W 13:21:47 Retrying (21)...

W 13:21:48 Retry Failed - Reason: Invalid Address For Write

W 13:21:49 Retrying (22)...

W 13:21:49 Retry Failed - Reason: Invalid Address For Write

W 13:21:50 Retrying (23)...

W 13:21:50 Retry Failed - Reason: Invalid Address For Write

W 13:21:51 Retrying (24)...

W 13:21:51 Retry Failed - Reason: Invalid Address For Write

W 13:21:51 Retrying (25)...

W 13:21:52 Retry Failed - Reason: Invalid Address For Write

W 13:21:52 Retrying (26)...

W 13:21:52 Retry Failed - Reason: Invalid Address For Write

W 13:21:54 Retrying (27)...

W 13:21:54 Retry Failed - Reason: Invalid Address For Write

Posted

I'd probably start by burning at 4x instead of 8x.

 

I see the drive is on a controller in RAID mode. What controller is that drive attached to? or what chipset does your motherboard use? You could right click the drive selection box and click the 'Family Tree' option to get all the info I need. Just do that, close the prompt and then copy + paste the info from the log window.

 

It might be worth crossflashing that drive to the real LiteOn that it is - there will probably be a newer firmware for it than your current HP model.

Posted (edited)

Will do, i appreciate the information. allow me to follow your steps and i will get right back with you!

Edited by DBroncos24
Posted

I believe this is what you requested, i have trouble seeing that the raid controller as the problem considering i have had multiple successes before. But i am open to anything, Im sure you are much more knowledgeable in this specific area than i am!

 

 

I 13:50:35 Family Tree:

I 13:50:35 -> ACPI x86-based PC

I 13:50:35 -> Microsoft ACPI-Compliant System

I 13:50:35 -> PCI bus

I 13:50:35 -> Intel® 82801 PCI Bridge - 244E (VEN_8086&DEV_244E - Intel - pci)

I 13:50:35 -> VIA VT6421 RAID Controller (VEN_1106&DEV_3249 - VIA - vsmraid)

I 13:50:35 -> CD-ROM Drive (HP DVD Writer 1270t SCSI CdRom Device) (Bus Number 0, Target Id 0, LUN 0)

Posted

Okay im currently attempting to burn at 4x but although im not getting the same error, it states its writing sectors but the time the ETA is "unknown" and the completion percentage is at zero. Any ideas about this?

Posted

I didn't say the controller was an issue, I just wanted to know more about it :)

 

That said, I certainly wouldn't keep the drive on the VIA card if you have any choice in the matter. If you have any SATA ports spare, the Intel controller is the better option.

 

So as it stands, when you burn at 8x you get communcation time out issues and at 4x the drive just flat out doesn't do anything - correct? This is where I'd certainly just double check it behaves the same way on another controller. If it does, think about cleaning it with a cleaning disc. After that, you can think about trying another spindle of discs, crossflashing to a real LiteOn and investing in a new drive.

Posted

The VIA controller is used for the strict use of the SATA ports on account of my computer not having any on the Motherboard. And yes that's absolutely correct, on all other speeds i get action from the drive but then seems to time out, and at 4x i get nothing from it at all, the ETA goes to unknown. I sadly do not have another controller to attempt this on and i wish i had a cleaning disc. but i can attempt to crossflash to a new lite-on firmware. If you could help me with what version of the firmware i need to use i would be very great-full.

Posted

The guys/gals at the MyCE forum are more into that stuff than I am.

 

http://club.myce.com/f44/

 

At a guess though, I'd say an 'iHASx24 B' firmware would be right.

 

I've been doing a bit of reading and there seems to be a few HP 1270 models. Yours is the 't' version! Other versions have been linked to 'iHASx24 A' and 'iHASx24 Y' models, so it makes sense for yours to be the newer 'iHASx24 B' version.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.