Jump to content

ImgBurn Support Forum uses cookies. Read the Privacy Policy for more info. To remove this message, please click the button to the right:    I accept the use of cookies

Photo

"Semaphore time period has expired".


Forum Rules

Read the Guides forum if you don't know how to do something. :readbook:
If you have a question or a problem, check the FAQ and use the Search to see if you can find the answer for yourself. :lightbulb:
If you're having trouble burning double layer media, read Here.
Still stuck? Create a new thread and describe your issue in detail.
Make sure you include a copy of the program's log in your post. No log = :chair:


  • Please log in to reply
5 replies to this topic

#1 PeterGiovani

PeterGiovani

    ISF Newbie

  • New Members
  • Pip
  • 2 posts
  • Location:USA

Posted 06 October 2017 - 01:57 PM

Have been using ImgBurn for years...No hardware changes...No software changes.

 

As of two days ago, neither of my 2 internal blue ray drives will complete a full burn.

 

About 50% through I receive "Semaphore time period has expired".

 

4x burn as I always have.

 

Same media as always - Verbatim br.

 

Data is from my D drive...Can bad sectors cause semaphore errors?


Edited by PeterGiovani, 06 October 2017 - 02:59 PM.


#2 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,303 posts
  • Gender:Male
  • Location:United Kingdom

Posted 06 October 2017 - 07:06 PM

I don't think I've ever seen that error from anything other than a drive connected via USB.

Can you post the log please?
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#3 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 06 October 2017 - 10:49 PM

Yeah, I was going to post the same thing when I read this post earlier today.

 

 

Normally, semaphore time out expiration errors are from USB external burners.  It's caused by a conflict between the USB bridge in the external enclosure and the controller on your PC's motherboard.  I don't think I've ever seen it on an internal SATA connected drive before, either.

 

 

I, too, was going to request the log, but I didn't post because I thought the log probably wouldn't help.  That it would just say the semaphore timeout period expired with no other pertinent data.  I was waiting for LUK to post to see about enabling Debug mode first before posting a log.  To post a log with the Debug mode enabled.



#4 PeterGiovani

PeterGiovani

    ISF Newbie

  • New Members
  • Pip
  • 2 posts
  • Location:USA

Posted 07 October 2017 - 07:41 PM

Here is what it turned out to be:

 

I was burning a folder full of video files. ImgBurn keep giving semaphore timeout error on one specific file. I removed that file, tried to burn, got the error on another file. So I decided that it couldn't be the files.

 

But, I ended up trying to move the entire folder from the original D drive (internal), to my P drive (external), and I received the same semaphore timeout error, on both of the files in question.

 

I deleted both files, and have been able to successfully use ImgBurn to complete the burn of the folder.

 

Not sure what was wrong with the files, but they were the issue.



#5 LIGHTNING UK!

LIGHTNING UK!

    Author of ImgBurn

  • Admin
  • PipPipPipPipPip
  • 29,303 posts
  • Gender:Male
  • Location:United Kingdom

Posted 07 October 2017 - 07:47 PM

So the error was from the reading side of things (reading the files from the hdd) rather than the burning part?

The log would have helped to pinpoint where the error was coming from, but I'm glad you've sorted it now anyway.
Please don't PM me with questions that should be posted in the forum. I won't reply - Especially if you have post count of 0!!!

Replies to posts belong in the forum where everyone can read them. Please don't PM them.

In fact, don't PM me at all unless it's something I've asked to be told about!

Before asking questions, search the forum to see if someone else already has.

Use the FAQ and Guides forums to your advantage. I don't want to have to tell you to read them!

#6 dbminter

dbminter

    ISF God

  • Beta Team Members
  • PipPipPipPipPip
  • 5,541 posts
  • Gender:Male

Posted 07 October 2017 - 09:10 PM

I still find it odd the issue occurred in the first place on an SATA connected device.  I've only ever seen semaphore timeout errors when trying to burn to USB drives.  And always with writes, not reads. 

 

 

Personally, I'm rather surprised the issue went away. 

 

 

Experience would dictate the problem may have been a bad sector on the HDD.  So, next time data is written to that area, you might experience the issue again.

 

 

However, the way I see it, as long you can find a solution that works, you go with it and be grateful.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users