Jump to content
Sign in to follow this  
flyinonice4

Failure to Write Sectors 32-63 With Queue

Recommended Posts

So recently I downloaded ImgBurn because a ton of people recommended it. I understand why. It is amazing. However, Ive kinda noticed a small bug type issue. First off I will say I'm using Verbatim white inkjet printable 16x dvd-r media so it shouldn't be a problem with my media. Next im using a plextor 716uf dvd drive with 1.09 firmware which a lot of people have and have had success with including me in the past. I am using ImgBurn 1.3 for my burning. If I do burning one iso at a time (IE no queue) then I have no problems at all. If I do do a queue though and I let it do an "AutoOK" then I usually come up with a log that say

"I 14:39:15 Operation Started!

I 14:39:15 Source File: C:\sio\AMPIE.ISO

I 14:39:15 Source File Sectors: 2,286,032 (MODE1/2048)

I 14:39:15 Source File Size: 4,681,793,536 bytes

I 14:39:15 Source File Volume Identifier: AMPIE

I 14:39:15 Source File Implementation Identifier: DVD Shrink

I 14:39:15 Source File UDF Revision: 1.02

I 14:39:15 Destination Device: [0:0:0] PLEXTOR DVDR PX-716A 1.09 (I:) (USB)

I 14:39:16 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 4x, 6x, 8x, 12x, 16x)

I 14:39:16 Destination Media Sectors: 2,298,496

I 14:39:16 Write Mode: DVD

I 14:39:16 Write Type: DAO

I 14:39:16 Write Speed: 8x

I 14:39:16 Link Size: Auto

I 14:39:16 Test Mode: No

I 14:39:16 BURN-Proof: Enabled

I 14:39:16 Filling Buffer...

I 14:39:16 Writing LeadIn...

W 14:39:33 Failed to Write Sectors 32 - 63 - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (1 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (2 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (3 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (4 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (5 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (6 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (7 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (8 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (9 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (10 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (11 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (12 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (13 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:33 Retrying (14 of 20)...

W 14:39:33 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (15 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (16 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (17 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (18 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (19 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

W 14:39:34 Retrying (20 of 20)...

W 14:39:34 Retry Failed - Logical Unit is in process of becoming ready

E 14:46:49 Failed to Write Sectors 32 - 63 - Logical Unit is in process of becoming ready

I 14:46:49 Synchronising Cache...

E 14:46:50 Failed to Write Image!

E 14:46:52 Operation Failed! - Duration: 00:07:34

I 14:46:52 Average Write Rate: 0 KB/s (0.0x) - Maximum Write Rate: 0 KB/s (0.0x)"

I thought I would point this out and see what can be done. Thanks.

Share this post


Link to post
Share on other sites

The drive must have been 'ready' at some point or it wouldn't have moved onto the next image.

 

For some reason, your drive is becoming 'not ready' - and that's not a good thing, it should not happen.

 

Once you exhaust the 20 retries (as above), wait 30 seconds and then hit retry manually. Does it continue? If not, what error do you get then?

 

We've done hundreds of queue burns and I've yet to see this problem.

Share this post


Link to post
Share on other sites

LUK;

 

That seems something like an error I would get using DVDD. It would happen one time in about every 25-30 burns. It only happened on DVD-R media. Here is part of the log;

 

I 15:32:45 Write Mode: DVD

I 15:32:45 Write Speed: 4x

I 15:32:45 Test Mode: No

I 15:32:45 BURN-Proof: Enabled

W 15:32:45 [0:0:0] SONY DVD RW DRU-710A BY03 (F:) (ATA) - Selected Write Speed: 5,540 KB/s (4x)

W 15:32:45 [0:0:0] SONY DVD RW DRU-710A BY03 (F:) (ATA) - Actual Write Speed: 4,432 KB/s (3.3x)

I 15:32:45 Filling Buffer...

I 15:32:46 Writing LeadIn...

E 15:38:16 Failed to Write Sectors 32 - 63 - The request could not be performed because of an I/O device error.

 

If I aborted after the error happened and then started the burn again it would work without any problems. I've kept track of the discs on which the error happened and so far none of them have had any problems with playback.

Share this post


Link to post
Share on other sites

That message is from something deeper in the I/O subsystem.

 

It's not a drive error message (so to speak), it's coming from the DeviceIoControl API call.

 

Once submitted, all of this I/O stuff is out of my control.

Share this post


Link to post
Share on other sites

ok it happened again and this is what i get

I 16:01:19 Operation Started!

I 16:01:19 Source File: C:\sio\ultraviolet.ISO

I 16:01:19 Source File Sectors: 2,285,894 (MODE1/2048)

I 16:01:19 Source File Size: 4,681,510,912 bytes

I 16:01:19 Source File Volume Identifier: DVD

I 16:01:19 Source File Implementation Identifier: DVD Shrink

I 16:01:19 Source File UDF Revision: 1.02

I 16:01:19 Destination Device: [0:0:0] PLEXTOR DVDR PX-716A 1.09 (I:) (USB)

I 16:01:19 Destination Media Type: DVD-R (Disc ID: MCC 03RG20) (Speeds: 4x, 6x, 8x, 12x, 16x)

I 16:01:19 Destination Media Sectors: 2,298,496

I 16:01:19 Write Mode: DVD

I 16:01:19 Write Type: DAO

I 16:01:19 Write Speed: 8x

I 16:01:19 Link Size: Auto

I 16:01:20 Test Mode: No

I 16:01:20 BURN-Proof: Enabled

I 16:01:20 Filling Buffer...

I 16:01:20 Writing LeadIn...

W 16:01:34 Failed to Write Sectors 32 - 63 - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (1 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (2 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (3 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (4 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (5 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (6 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (7 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (8 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (9 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (10 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (11 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (12 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (13 of 20)...

W 16:01:34 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:34 Retrying (14 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (15 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (16 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (17 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (18 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (19 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:01:35 Retrying (20 of 20)...

W 16:01:35 Retry Failed - Logical Unit is in process of becoming ready

W 16:02:11 Retrying (21)...

W 16:02:11 Retry Failed - Invalid Address For Write

Share this post


Link to post
Share on other sites

No idea then I'm afraid.

 

The drive is not supposed to become 'un-ready' during a burn like that.

 

It's not a generic Plextor thing as mine certainly doesn't do it.

Share this post


Link to post
Share on other sites

Hmm ok. I wonder what the problem is then? If I dont use the queue then I have no problem at all, thats why I thought it was a bug. Do you think its a problem with my drive by any chance?

Share this post


Link to post
Share on other sites

It's a problem with something but I don't know what exactly.

 

It's odd that it accepted the first write command (sectors 0 - 31) and then seems to reset itself - meaning it's not ready again. Very weird!

Share this post


Link to post
Share on other sites

whats weird too is that I am still able to use that same disc to write the image file on again. I thought since it had written the sectors 0-31 that I wouldnt be able to use it because it would show up as written on, but it shows up as empty and I can use it. Im thankful for it, but it seems weird to me. Maybe its not actually writing those sectors? I dont know whats going on.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

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