` Comment on an Icetips Article
Icetips - Templates, Tools & Utilities for Clarion Developers

Templates, Tools and Utilities
for Clarion Developers

Add a comment to an Icetips Article

Please add your comments to this article. Please note that you must provide both a name and a valid email address in order for us to publish your comment. Comments are moderated and are not visible until they have been approved. Spam is never approved!

Your Name:  
Email:  
Header text/Subject:  

Please enter your comment in the box below:

Back to article list   Search Articles     Add Comment     Printer friendly     Direct link  

Par2: Diagnosing TPS file corruption
1998-09-16 -- John Longarrow
 
Something quick and dirty to try. Make a file that is about 100 meg. Copy it to another location on the server. Run a file compare on the two. If you have any differences, you may have a bad controller for the Hard Drive. If you don't have a problem, copy the file to a local hard drive and do the same thing. If you get a difference now, you may have a bad NIC. If you don't have a problem, copy the file back from your local hard drive to the server. Try the File compare again. If you you have a difference, once more look into the NIC for a problem. This is a down and dirty way to check for very intermittent hardware problems. I ran across this a couple years ago when we were having data loss on a single server. Wound up being the hard drive controller. This was ofcourse AFTER we had a couple network trouble shooters come out and not find anything wrong...


Today is April 29, 2024, 4:53 am
This article has been viewed 35112 times.



Back to article list   Search Articles   Add Comment   Printer friendly

Login

User Name:

Password: