Koozali.org: home of the SME Server
Legacy Forums => General Discussion (Legacy) => Topic started by: Quade on December 12, 1999, 01:45:46 AM
-
Hey All,
I have been using eSmith for several months now, and I like it because of it's low maintanence and ease to setup.
However, I've noticed after being up for about 3 weeks, I start getting error messages when I'm actually in front of the server (I can't telnet in by this point).
The errors appear where the normal blue screen should be, and seems to cycle through the same series of messages.
They go something like this:
hda: status error: status=0x00 { }
hda: drive not ready for command
(those lines repeat about 10-20 times)
ide0: reset: master: error (0x00?)
hda: status error: status=0x00 { }
hda: drive not ready for command
(those lines repeat about 5-10 times)
end_request: I/O error, dev 03:06 hda, sector 2 (or a different sector number)
hda: status error: status=0x00 { }
hda: drive not ready for command
(those lines repeat about 5-10 times)
EXT2-fs error(device ide0(3,6)): unable to send inode block
There are other things that repeat in there too, but it moves to quick for me to catch...something about a hole in a directory?
I just replaced the hard drive because I kept getting these error messages on a previous hdd. I've also run diags on the system using microscope, and found nothing wroing. all the hardware I have is supported by eSmith.
This happens about every 3 weeks, and the only way I can get the machine working again is to hit the reset button. :( I still have Internet access for the windoze machines on the network, but the server disappears from Network Neighborhood, and I can no longer telnet into it. The end result is that I have to reinstall eSmith (if I reboot a couple of times, the computer refuses to find Linux).
Any ideas? I'm completely out, and I don't want to switch products if I can help it.
TIA
Quade
-
Hi Quade,
Sorry to hear about your system bombs. I'm wondering if you might possibly have a bad mainboard? It sounds like the system is having trouble with the hard disk, and you've done the right experiment to rule out a hardware problem with the hard disk drive. That stills leaves a possible problem with your hard disk controller. Have you experienced the problem on more than one computer?
Best regards,
- Joe
-
Well, I took the machine down for a few days and ran diags on it. The disk controllers check out, and the mainboard appears to be fine as well. I replaced the IDE cable, and I thought that was it, but I got the same series of error messages once since then. It's been fine for the past few days, though, and I will continue to keep an eye on my baby.
If anybody else has run accross this problem, please let me know what you've found. This is one of those things where the answer seems like it's obvious--I'm just not seeing it.
TIA,
Quade