Solved

Error 832 - I/O Error 121 - semaphore timeout

Posted on 2002-05-24
8
1,103 Views
Last Modified: 2013-12-28
What does this error tell you?
Server: Msg 823, Level 24, State 1, Line 3
I/O error 121(The semaphore timeout period has expired.) detected during read of BUF pointer = 0x14235a40, page ptr = 0x15602000, pageid = (0x3:0xb88), dbid = 4, status = 0x801, file = ...
This occurred after I screwed up by adding a SCSI device with the same SCSI ID as I was already using. However, the disk check did not find any errors. Obviously I'm looking for an answer other than "restore from backup".
0
Comment
Question by:pkohlmil
  • 3
  • 3
8 Comments
 
LVL 63

Expert Comment

by:SysExpert
ID: 7034946
The error simply means that there was a SCSI error.
Did it go away when you corrected the SCSI ID ?

That kind of error can cause unpredictable results with 2 drives, since you can  not be sure what is written properly.

I would try reading the drive in another machine with SCSI.

I hope this helps !
0
 
LVL 2

Author Comment

by:pkohlmil
ID: 7039768
Correcting the SCSI ID did allow the machine to boot up and no disk errors were detected but the problem noted here occured after the machine was successfully rebooted.
0
 
LVL 63

Accepted Solution

by:
SysExpert earned 200 total points
ID: 7040417
1) It could be a hardware error on the Controller or the drive.

2) It could be a termination problem on the SCSI line.

3) I would also set the SCSI controller to default value after writing down the values you have in use now.

4) can you run SCSI diagnostics and/or other harware diagnostics ?

I hope this helps !
0
Being driven mad by email signature updates?

Having to make a change to your users’ email signatures, yet again? Feel like your head is going to explode? Rely on an Exclaimer email signature management solution to make the process simple!

 
LVL 2

Author Comment

by:pkohlmil
ID: 7040648
Here is some additional information. The file in question is a SQL Server data file. However, when I turn off SQL Server and simply try to copy the file, I get this error.
"The file path is too deep." Now I file path too "long" I could understand even though the path in this case is less than 50 characters. Is it possible that this file lost its EOF marker and I just need to fix that (and how would I do that)?
0
 
LVL 63

Expert Comment

by:SysExpert
ID: 7040757
I would be extremely careful here, since any changes you make could prevent later data recovery.

If this data is critical, contact ontrack.com and send the stuff to their labs to be recovered.

It costs $$$, but it may be your best chance in the long run.

Do you have any backups ?

Is this RAID or a single drive ?

I hope this helps !
0
 
LVL 23

Expert Comment

by:Tim Holman
ID: 7058896
To get round "File path is too deep", you could use the SUBST command to shorten it.

eg

subst g: c:\winnt\system32\drivers\etc

The only semaphore errors I've seen are down to either bad hardware or bad drivers.  I suggest checking to see if there are any later SCSI drivers available for your device.
0
 
LVL 2

Author Comment

by:pkohlmil
ID: 7060026
So far, nothing has worked. I don't have the option of sending the disk to ontrack.com. They don't respond to e-mails regarding my particular problem. They have an eval copy of their software which at one time did detect a suspicious "lost file" that might have contained my missing data. I then bought the product (because the eval version doesn't let you save the file) and that product did not find the lost file. Going back to the eval version doesn't find it anymore. Also, this product bombs repeatedly when attempting a rescan. One good thing about this product. It was able to make a copy of a file that the O.S. could not (path too deep) and this copy doesn't have that problem anymore. This does not have anything to do with the file path and I don't understand the message.

I submitted a problem report with Microsoft and they were not able to help but they still want me to say that they did a good job. I'm going to try ontrack.com some more and then punt.
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Remoteing in to my computer ? 4 53
How to open a .vcf file 11 54
Windows 2012 STD Updates Issue 15 28
copying evtx files while system is running 2 14
This is an article about Leadership and accepting and adapting to new challenges. It focuses mostly on upgrading to Windows 10.
If you get continual lockouts after changing your Active Directory password, there are several possible reasons.  Two of the most common are using other devices to access your email and stored passwords in the credential manager of windows.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
In this video, we discuss why the need for additional vertical screen space has become more important in recent years, namely, due to the transition in the marketplace of 4x3 computer screens to 16x9 and 16x10 screens (so-called widescreen format). …

863 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now