disk controller error

I have an SBS 2000 server - ASUS P5K-EPU -  with a Raptor 300 gig drive as the main server drive. In addition I have a Maxtor IDE drive as well for quick backups - all the working data and programs are on the Raptor.  

I have been recentely getting Disk Controller errors in Event Viewer as follows:

The driver detected a controller error on \device\hardisk1\hdr1 - event ID 11

It is almost always preceded by a lot of MrxSmb errors -
The redirector failed to determine the connection type
Event ID 3019

Everything seems to be working fine but it does have me a bit worried.

Any ideas of what is causing this and what I can do to resolve.  Possibly just a harmless error message?

Who is Participating?
lineonecorpConnect With a Mentor Author Commented:
I have found the source of the problem and it is an important one for anybody using Velociraptors.  Apparently with the 300 gig Veliciraptor drives there are two models  - GLS and HLS.  GLS are not meant to be used in servers!  There is some obscure timing component that on the GLS takes too long so that RAIDs and server OS end up with these disk controller errors. For some reason Western Digital decided to create two models that are almost identical in price of which one works in every environment and the other doesn't.
peace_countryConnect With a Mentor Commented:
The common casuses of this error all seam to revovle around network shares, most notably those network shares that are mapped locally, or mapped multiple times to the same share on the same PC that's not hosting  the shares.

Possibility 1. It's likely that if this is a terminal server, you will see more of these if you do not have seperate terminal server profiles and logon scripts to privide shares based on the SUBST command instead of NET USE,
Possibility 2.  If for some reason someone has decided to manually map a shared folder something other than the intended drive letter and thusly has a duplicate
Possibility 3  Sometimes if a drive is manually mapped to a drive letter that is also attempting to be mapped by a NET USE command and it's failing to map the drive via script because the letter is in use.

if any of the above exist you could try altering logon scripts, have one specifically for terminal services and either provide shortcuts to local locations, or build SUBST commands to attempt to replicate drive mappings.  And for remote computers I would suggest adding 'NET USE f: /delete' all the way thru z: to ensure your intended mappings take place.  The logon script takes longer to run, but you can then always gurrantee your users wind up with mappings that are intended.
lineonecorpAuthor Commented:
Thanks for the tips.  I'll keep them in mind but my main concern - the disk controller error - is now gone. What I did was Ghost the Raptor drives to ordinary IDE drives - software mirrored - and I no longer have the disk error message.  I find it hard to believe that 3 brand new Raptors would all be defective in some way. And I equally find it difficult to believe that the onboard SATA has gone wonky - note that I did change SATA cables in tyring to troubleshoot.  I guess it could be a matter of some SATA configuration - I have a SATA DVD drive in the system and maybe there's some kind of order of drives issue/conflict. Or it could be there is some kind of problem because of the size of the Raptors - we did have to do a registry entry to get the system tor recognize drives over 128 gig - but the system ran fine for a month without a problem after initial install and the registry entry.  Or there is a driver problem.

Any thoughts on any of my 'thoughts'?
lineonecorpAuthor Commented:
Typo in my last comment.  It should be GLFS and HLFS. HLFS works in servers/RAID - GLFS does not.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.