Jump to content
Sign in to follow this  
ryan

The semaphore timeout period has expired

Recommended Posts

I 09:22:16 ImgBurn Version 2.0.0.0 started!
I 09:22:16 Microsoft Windows XP Tablet PC Edition (5.1, Build 2600 : Service Pack 2)
I 09:22:16 Initialising SPTI...
I 09:22:16 Searching for SCSI / ATAPI devices...
I 09:22:19 Found 1 DVD-ROM, 1 DVD-ROM/CD-RW and 1 DVD?RW/RAM!
I 09:23:30 Operation Started!
I 09:23:30 Device: [0:0:0] HL-DT-ST DVDRAM GSA-4081B E104 (G:) (USB)
I 09:23:30 Media Type: DVD-RW (Disc ID: MCC 01RW11n9) (Speeds: 1x, 2x)
I 09:23:30 Quick Erase: Yes
I 09:23:30 Erasing Disc...
I 09:24:27 Operation Successfully Completed! - Duration: 00:00:57
I 09:24:38 Operation Started!
I 09:24:38 Corrected conflicting settings for DVD Video disc.
I 09:24:38 Building Image Tree...
I 09:24:38 Checking Directory Depth...
I 09:24:38 Calculating Totals...
I 09:24:38 Preparing Image...
I 09:24:38 Checking Path Length...
I 09:24:38 Image Size: 4,695,609,344 bytes
I 09:24:38 Image Sectors: 2,292,778
I 09:24:41 Operation Successfully Completed! - Duration: 00:00:02
I 09:24:41 Operation Started!
I 09:24:41 Source File: -==/\/[BUILD IMAGE]\/\==-
I 09:24:41 Source File Sectors: 2,292,778 (MODE1/2048)
I 09:24:41 Source File Size: 4,695,609,344 bytes
I 09:24:41 Source File Volume Identifier: THE_UNTOUCHABLES
I 09:24:41 Source File Application Identifier: IMGBURN - THE ULTIMATE IMAGE BURNER! (C) 2006 LIGHTNING UK!
I 09:24:41 Source File Implementation Identifier: ImgBurn
I 09:24:41 Source File File System(s): ISO9660, UDF (1.02)
I 09:24:41 Destination Device: [0:0:0] HL-DT-ST DVDRAM GSA-4081B E104 (G:) (USB)
I 09:24:41 Destination Media Type: DVD-RW (Disc ID: MCC 01RW11n9) (Speeds: 1x, 2x)
I 09:24:41 Destination Media Sectors: 2,298,496
I 09:24:41 Write Mode: DVD
I 09:24:41 Write Type: DAO
I 09:24:41 Write Speed: MAX
I 09:24:41 Link Size: Auto
I 09:24:41 Test Mode: No
I 09:24:41 BURN-Proof: Enabled
I 09:24:41 Filling Buffer...
I 09:24:42 Writing LeadIn...
W 09:24:43 Failed to Write Sectors 0 - 31 - The semaphore timeout period has expired.
W 09:24:43 Retrying (1 of 20)...
W 09:24:43 Retry Failed - Power On, Reset, or Bus Device Reset Occurred
W 09:24:43 Retrying (2 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (3 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (4 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (5 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (6 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (7 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (8 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (9 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (10 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (11 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (12 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (13 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (14 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (15 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (16 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (17 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (18 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (19 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
W 09:24:43 Retrying (20 of 20)...
W 09:24:43 Retry Failed - Cannot Write Medium - Incompatible Format
E 09:24:52 Failed to Write Sectors 0 - 31 - The semaphore timeout period has expired.
I 09:24:52 Synchronising Cache...
E 09:24:53 Failed to Write Image!
E 09:24:53 Operation Failed! - Duration: 00:00:11
I 09:24:53 Average Write Rate: N/A - Maximum Write Rate: N/A

 

Here's the log file. I was able to burn fine the other day, but for some reason this morning I get this error when burning. Tried on two DVD-Rs, same error, then tested on a DVD-RW and same error as well. Does this mean the drive's shot? It reads files fine. :/

Share this post


Link to post
Share on other sites

Before we start with the difficult stuff, humour me and do a full format instead of a quick format. Going by the media ID, a full format should take around 30 minutes.

Share this post


Link to post
Share on other sites
We?ll be here. Come to think of it, we?re always here. :)

 

It's nice to know that. :) That is what puts ImgBurn lightyears ahead of Nero or any other burning software- a better product and the community is just great!

 

I've finished doing a full erase. Should I attempt another burn?

Share this post


Link to post
Share on other sites

Know this was Shamus's thread but yea go ahead ryan, burn again. Exactly the same settings as you did the first time when the original error occurred. Good Luck......... :thumbup::)

Share this post


Link to post
Share on other sites

Hmph, I'm puzzled. :wacko: The DVD-RW is burning error-free (at least so far). I'll have to test a DVD-R afterwards. Any reason why it would be different this time just because I did a full erase?

Share this post


Link to post
Share on other sites

ryan, a full erase completely erases the disc, a quick erase, I believe, just replaces the current info on the disc with 0's.( zeros ) . Another thing perhaps is that the RW disc wasn't properly formatted before the inital burn you did, a full erase solves this. Glad its working out for you though...... :thumbup::) Keep us posted.

Share this post


Link to post
Share on other sites

The semaphore timeout period expires because something in the USB chain overrides the timeout period I specify in the program. This is not supposed to happen but it's actually very common with usb drives / enclosures. :(

 

Basically if the drive takes too long to do anything it just gives up and resets

Share this post


Link to post
Share on other sites

Just burned a DVD-R sucessfully, and the semaphore error no longer occurs, so thanks Shamus_McFartfinger, kevdriver, and LIGHTNING UK! for the help! :thumbup:

Share this post


Link to post
Share on other sites

Seriously, don't be surprised if you see it again sometime!

 

On the old forum we had a 40 page thread on semaphore timeout errors.

 

There's an even longer one over at the afterdawn forums.

Share this post


Link to post
Share on other sites

Agreed. I remember DB fighting with his USB enclose for ages in the old forum. It might not be a bad idea to pull a HD out of your PC and mount that into the USB enclosure thingy and connect the DVD drive to an IDE cable.

Share this post


Link to post
Share on other sites

Depending on who makes the enclosure (or rather the chipset it uses), you may be able to update the firmware on it.

 

Prolific chipsets are quite common and there are firmware updates for those - I have a couple of them myself.

Share this post


Link to post
Share on other sites

And be prepared as LIGHTNING_UK said to witness this again, especially if the enclosure your using has the Ali M5621 A1 chipset.

 

This revision cannot be flashed.

 

The 3 or 4 sumvision usb2 enclosures i have that use prolific chipset do not suffer from semaphore timeout.

Share this post


Link to post
Share on other sites
We?ll be here. Come to think of it, we?re always here. :)
Can't get ridda you, you drunken sod!

 

'oweryagoin Shamus?

 

Regards

Share this post


Link to post
Share on other sites
:D :D :D

Share this post


Link to post
Share on other sites

Actually, it wasn't that I was fighting with it. ;) I was preforming all kinds of tests since I had one that was exhibiting the trait. So, I had become the guinea pig among the beta testers. :D Of my own choice, but, I wanted to see if there was a way around it. There wasn't. :lol: Especially if it was an ALI bridge of that series before, like Revision 5, where they added the ability to update the firmware of it. FINALLY. :rolleyes: BUT, since there were, apparently, hundreds of thousands of these faulty, unsold chips in a warehouse, ALI got rid of them on the cheap, and dozens of manufacturers were using them to save a buck. To Hell with the user. IOMega was one. In 3 external optical drives of theirs, I encountered ALI bridges in the enclosures. I wouldn't be surprised if there was in the USB HD's.

 

 

I think I will examine that one USB HD enclosure here in a bit, just for my and everyone's edification on the bridge in it. Since the drive is readily accessible right now, and the enclosure WAS easy to remove... AFTER I pried off the idiotic washer type piece of shit thing they had over the STRIPPED screw... :rolleyes: So, one of the screws does not hold the drive in place. But, 3 out of 4 is fine. :thumbup:

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.