System Abends...
RODNEY HOFFMAN
Has anyone ever had experience with a ZEOS 66DX2 server that abends at
the slightest touch? Here are the symptoms...
Most often, the system crashes with a parity error in the RAM. The
server will hang at the most inopertune times with a major load on the
server and processing. At other times, the server will just hang (the
keyboard will lock, all I/O will cease, and yet other times the
Ethernet card will hang thee sysem wwith an error in the adapter's
RAM.
This bcomes very frustrating for me and more important, the users
will become very iirrate
The configuration of the system is as follows:
A ZEOS 66DX2 EIISA Motherboard
2 - 1.2 Gb Maxtor hard drives (FH, old technology)
32 Mb RAM in 4 Mb 70 ns SIMMS - one bank of 16 Mb purchased seperately
2 1540 Adaptec SCSI Hard Drive interface cards
1 Intel EtherExpress 16 Ethernet card
1 Arcnet card
Any ideas??
Rod
---
* Inn on the Park (602)970-0105 AZ's RIME & FIDO Source for mail!
* PostLink(tm) v1.11 INNPARK (#1037) : RelayNet(tm)
JERRY SHENK
> server will hang at the most inopertune times with a major load on the
> server and processing. At other times, the server will just hang (the
> keyboard will lock, all I/O will cease, and yet other times the
> Ethernet card will hang thee sysem wwith an error in the adapter's
> RAM.
RH> A ZEOS 66DX2 EIISA Motherboard
> 2 - 1.2 Gb Maxtor hard drives (FH, old technology)
> 32 Mb RAM in 4 Mb 70 ns SIMMS - one bank of 16 Mb purchased seperately
> 2 1540 Adaptec SCSI Hard Drive interface cards
> 1 Intel EtherExpress 16 Ethernet card
> 1 Arcnet card
You have an EISA motherboard with no EISA parts. That seems to be a
bit wastefull. Also running a 66mHz machine with an actual clock
speed of 33 mHZ will not give you as good performance as a 50mHz
machine.
Are you using the correct parameters with your AHA1540.DSK? In
particular, there is an above16=y command-line switch which should be
set for use in an ISA machine (not sure about EISA). Are you using
the EISA .CFG files for the 1540s? Even though they are not EISA
cards, I believe they do come with EISA configuration files to assist
in getting things set up correctly.
If you suspect that RAM might be a problem (mentioning that one module
was purchased separately) you certainly have enough RAM to pull that
16 meg bank. If you are duplexing you could EASILY run with only 16
megs. Even if you are not duplexing you could still run with 16. 16
mnegs for 2.4 gigs of a drive space is a little low but would
certainly run. You didn't mention any NLMs, name space, backup or
anything like that so these memory figures are based on there being
none. Is it correct that you have 4 banks of 16megs per bank?
---
ş SPEED 1.10 [NR] ş If voting changed anything, Congress would outlaw it...
* Lancaster Area Bulletin Board * Lancaster, PA (717) 394-1357
* PostLink(tm) v1.07 LABB (#32) : Relaynet (tm)
GARY HALLEEN
RH | server and processing. At other times, the server will just hang (the
RH | keyboard will lock, all I/O will cease, and yet other times the
RH | Ethernet card will hang thee sysem wwith an error in the adapter's
RH | RAM.
This makes it really sound like you have some bad memory. Are all the
SIMMS the same speed, and with the same number of chips?
* QMPro 1.52 * Modem Addiction Help line: Data only.
---
* Chemeketa OnLine Salem, OR 503-393-5580
* PostLink(tm) v1.11 CHEMEK (#233) : RelayNet(tm)
Dennis R. Hilton
>Hey all,
>
>Has anyone ever had experience with a ZEOS 66DX2 server that abends at
>the slightest touch? Here are the symptoms...
Well, I've seen this kind of thing in the past. Here's what I do...
1. Open the box and make sure that the motherboard is mounted
properly to the box, with insulating washers wherever screws
are used. Check for contacts that shouldn't be, and make sure
that the little white plastic thingies are in place.
2. Pull the adapter cards and memory. Clean all connecting surfaces
and replace everything firmly and securely.
3. Properly ground your box.
4. If the box is in a carpeted area, buy static elimination spray
and use it liberally. With some of the cheaper boxes, you can
slide into a fabric-seat chair, touch the keyboard, and you're
down. In fact, you can rub your feet on the carpet and touch
some one else nearby - with no contact to the machine at all -
and you're down. Static mats for the keyboards help, but they
must discharge through a resistor - an immediate un-resisted
discharge through a static mat will down you, too.
Good luck.
頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰頰
Dennis R. Hilton <drhi...@kaiwan.com>
"You need only reflect that one of the best ways to get yourself a
reputation as a dangerous citizen these days is to go about repeating
the very phrases which our founding fathers used in their struggle for
independence." --- C. A. Beard
Jeffrey Bergman
>
>The configuration of the system is as follows:
>
>A ZEOS 66DX2 EIISA Motherboard
>2 - 1.2 Gb Maxtor hard drives (FH, old technology)
>32 Mb RAM in 4 Mb 70 ns SIMMS - one bank of 16 Mb purchased seperately
>2 1540 Adaptec SCSI Hard Drive interface cards
>1 Intel EtherExpress 16 Ethernet card
>1 Arcnet card
>
First of all, verify that the RAM in bank zero is compatible with that in
bank one. Second, if the RAM is of different speed, put the faster RAM in
Bank zero. Third, are you using the "ABOVE16=YES" switch in the
Startup.ncf? Fourth, are you registering all your memory with the "Auto
Register Memory" or "Register Memory 1000000 1000000" switch? Fifth, (and
final) how many users does the Server support, yes, 32MB of RAM will suport
2.4Gb of volume, but if the traffic is comming fast and hard, you may need
more RAM. Check your Cache Buffers in the Monitor NLM (listed under
"System resources" If it is under 30%, bump up yor RAM.
Good luck.
Jeff Bergman
Joi L. Ellis
>The configuration of the system is as follows:
>A ZEOS 66DX2 EIISA Motherboard
>32 Mb RAM in 4 Mb 70 ns SIMMS - one bank of 16 Mb purchased seperately
>Rod
I expanded a 2.2 server from 8Meg to 16Meg with 8 new 70ns simms. The
old simms were 80ns simms. The server ran perfectly with the new memory
under 2.2, but under 3.11 it would hang, usually during a backup. I
took all 8 simms to my dealer, swapped them for 16 identical 80ns simms,
and all problems went away. (Granted, 2.2 only used the first
12Meg...)
The dealer told me that he has had to do that a number of times to his
client installations because 3.11 seems to be a lot more demanding about
memory timing that 2.x ever was.
Note that all 16 simms were in perfect condition, they'd been running
for months/years in their previous workstations, and worked perfectly
when put back into their original machines. Not to mention two days
worth of intensive memory diagnostics in the server... Only NETWARE
didn't like them. The dealer said he particularly noticed problems when
mixing 9-chip simms with 3-chip simms, even of the same speed.
--
Joi Ellis ms...@uxa.ecn.bgu.edu
Student Residential Programs Western Illinois University
Fons en Willem
JERRY SHENK <jerry...@castle.com> wrote:
>RH> Most often, the system crashes with a parity error in the RAM. The
> > server will hang at the most inopertune times with a major load on the
> > server and processing. At other times, the server will just hang (the
> > keyboard will lock, all I/O will cease, and yet other times the
> > Ethernet card will hang thee sysem wwith an error in the adapter's
> > RAM.
>
>RH> A ZEOS 66DX2 EIISA Motherboard
> > 2 - 1.2 Gb Maxtor hard drives (FH, old technology)
> > 32 Mb RAM in 4 Mb 70 ns SIMMS - one bank of 16 Mb purchased seperately
> > 2 1540 Adaptec SCSI Hard Drive interface cards
> > 1 Intel EtherExpress 16 Ethernet card
> > 1 Arcnet card
>
so.
check your cache memory, I had a similar problem, I found the only
program that told me something was wrong with my memory was himem.sys of
dos 6.20. After changing to new cache chips everything was OK.
(I also tried checkit & ndiags to test memory,
checkit had trouble testing above 16M, ndiags said everything was OK)
another thing to check are interrupts, when you are using all ISA cards
they should all be different,
IO ports, check if the IO area of some printer port doesn't overlap
the IO space of one of your network cards (happened to me some time ago)
willem