New Posts  All Forums:Forum Nav:

disk errors

post #1 of 8
12/27/02 at 1:22pm
Thread Starter 
Ok so I finally got the keyboard and mouse working now it's time to tackle this problem:
The driver detected a controller error on \Device\Harddisk0\DR0.
This error shows up quite a bit in my Event log. I'm hoping there's nothing wrong with the harddisk as I've run scandisk and it hasn't detected anything. I'm wondering if it's yet another driver issue with Win2k and SP3? If you've got any ideas folks I love to hear them.
Reply
Reply
post #2 of 8
12/27/02 at 9:05pm
I hate to say this, but whenever I see this in the event log, it usually means the hard drive is about gone. I see this all the time on the Thinkpads at work after the drives have around 16 months on them.

It could be something else, but if it is still under warranty, I would opt for an RMA.

Best of luck,
Martin Parrott
Reply
Reply
post #3 of 8
12/28/02 at 6:40pm
Thread Starter 
That's not what I want to here. I just RMA it for the touchpad which turned out to be a driver issue (they replaced the system board). The laptop is brand new (nov 02 manufactured stickers on it) I sure hope it's not the hard drive.
Reply
Reply
post #4 of 8
12/28/02 at 10:02pm
i tend to agree with martin. that message usually means bad things cometh.
Reply
Reply
post #5 of 8
12/28/02 at 11:16pm
I've been doing some searches on it trying to find info. The funny thing is every result I found was also with windows 2000.
Link1
Link2
Link3

I know it's not much to go on. My 1st thought in the situation would be a bad drive scandisk may not be detecting the bad sectors. I would try XP though. With the issues you've had, I would just give XP a try. I've only sold a handful of W2K with systems in the 5660 and 8886. If you would like to give another drive a try, gve Sager a call and tell them the problem. Let us know how it goes.
Reply
Reply
post #6 of 8
12/29/02 at 8:35pm
I do suspect Windows 2000 has something to do with this. All the problems we have seen are on systems with Win2K on them. However having said that, it usually means something hardware related is amiss. Win2K seems to be very sensitive to hardware glitches, errors, bad sectors, etc.

Here is one thing you can try. Get you a copy of Spinrite by Gibson research. Run Spinrite on the drive in extended mode and see if it finds any physical problems on the drive. If they are there, it should find them and remap them out of the way. I have saved quite a few systems with this program. The one drawback to this is it only operates on FAT filesystems. If you have your Win2K running on an NTFS partition, this won't work. If you don't mind reformatting, do a fresh load of your OS and format the drive so Spinrite can work on it. Once it passes, reload with NTFS. This may be too much work, but it is an alternative.

Hope this helps,
Martin Parrott
Reply
Reply
post #7 of 8
12/30/02 at 8:04pm
Thread Starter 
That thought had occured to me as I do have the hd 'ghosted'. I'll probably end up going to XP and since I'm getting DSL in January I'll pick up an updated distro of Linux. I'm not sure which one yet probably Suse or Mandrake. Oddly, the last two days have been 'eventless'.
Reply
Reply
post #8 of 8
12/31/02 at 5:04am
Well I hope it works out... I installed win2k on this 8886 and had no problems with it, just the boot manager, lol, which I fixed pretty easily. Let us know and best of luck!
Reply
Reply
New Posts  All Forums:Forum Nav:
  Return Home