UNIX for Dummies Questions & Answers

Everytime I boot up I get the following error message:

NOTICE: bad total free block count on Adaptec 294x/394x PCI SCSI Adapter <aha294x> DISK Target 0, LUN 0 partition 1

Then it asks me if I require a dump to be saved and I reply : NO

Once responded the next error message is :

/etc/rc2: 33 Memory fault - core dumped
IFS=

MAILCHECK=600
OPTIND=1
PATH=/bin:/etc:/usr/bin
TZ=GMT0
/etc/rc2:test: argument expected
/etc/rc3: 35 Memory fault - core dumped
IFS=

MAILCHECK=600
OPTIND=1
PATH=/bin:/etc:/usr/bin
TZ=GMT0
/etc/rc3:test: argument expected

I think that I don't have enough memory in the root directory but I cannot get a prompt.

Can anyone help me???

I think you mean "disk space" not "memory" in the root directory. You might try posting the output of your df command.

What is your OS?
Many Unices retreive their memory dump from their swap/dump device
on system reboot after a kernel panic (in your case probably resulting from a broken SCSI controller).
Usually the dump place in the filesystem as well as the amount how much of the memory should be dumped can be controlled by a user space command (e.g. dumpadm on HP-UX),
or dumps can be deactivated altogether.
If your box e.g. has large phys.memory (e.g. 16 GB or more as is not uncommon on enterprise servers) the writing of the dump into your filesystem (usually somewhere beneath /var) during boot up can quickly fill up all free space.
In this case find out how to supress the dump
(n.b. as long as you have no swap outs that could overwrite the dump area on your swap/dump device you can retreive the dump at any later time)

You other errors merely refer to syntax errors in init scripts' test blocks
probably resulting from unset vars.
(n.b. try using [[ -n $SOME_VAR ]] constructs to avoid those)

without some info about the OS it may be little difficult to ponder however try that:
1. first of all try to boot in single user mode to see that the actual memory is Ok, then go and see the log files, they normally are /var/log/messagesX in Solaris /var/adm/messages. read the logs carefully watch for time-stamps prior to the error it may provide the clue of what is wrong.
2. it is may as simple as a defective memory on the machine, in such case watch for something like "memory threshold exceeded"

The OS is Interactive UNIX 4.1.1

Anyone???

I'm getting desparate!!!