After this thing has been running clean now for a couple of years the
following messages and problems started popping up last night.


On console at startup:

Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 393216 Kbytes, lockable: 296672 Kbytes, available:
343188 Kbytes

/sbin/ioinitrc:
insf: Installing special files for pseudo driver framebuf

/sbin/bcheckrc:

Checking for LVM volume groups and Activating (if any exist)

* There is no keyboard connected or monitor. Access via RS-232
console.

/sbin/itemap: can't indentify HIL keymap named "": No such file or
directory

Checking hfs file systems
/sbin/fsclean: /dev/dsk/c0t6d0 (root device) ok
/sbin/fsclean: /dev/dsk/c0t0d0 not clean, run fsck

FILE SYSTEM(S) NOT PROPERLY SHUTDOWN,BEGINNING FILE SYSTEM REPAIR

/dev/rdsk/c0t0d0: 13853 files, 0 icont, 440971 used, 571472 free (760
frags, 71339 blocks)

FILE SYSTEM IS NOW FIXED

The above disk was being accessed at time of lockup. fsck tests
performed later had no problems.

System continues to boot normally...

Time passes...

--> System Heartbeat LED and other three LED's go dark. Power LED is
on.

--> System is restarted. After boot completes the following messages
are seen:

Entries in /var/adm/OLDsyslog.log:

Jul 13 09:12:41 sdhj16 vmunix: hil_ldcmd: command timeout
Jul 13 09:12:41 sdhj16 vmunix: hil_ldcmd: command timeout
Jul 13 09:12:41 sdhj16 vmunix: reconfig_timeout: hil has timed out
Jul 13 09:14:41 sdhj16 vmunix: hil_ldcmd: command timeout
Jul 13 09:14:41 sdhj16 vmunix: reconfig_timeout: hil has timed out

Entries in /var/adm/syslog.log

Jul 13 09:55:38 sdhj16 vmunix: hil_ldcmd: command timeout
Jul 13 09:55:38 sdhj16 last message repeated 17 times
Jul 13 09:55:38 sdhj16 vmunix: reconfig_timeout: hil has timed out
Jul 13 09:55:38 sdhj16 vmunix: hil_ldcmd: command timeout
Jul 13 09:55:38 sdhj16 last message repeated 15 times
Jul 13 09:55:38 sdhj16 vmunix: reconfig_timeout: hil has timed out

Time passes... System Heartbeat LED and other three LED's go out.

Load 'diag' CD and run all non-destructive Disk tests

STARTING EXECUTION OF DISKUTIL

Testing SEAGATE ST32151N Index 1
------------------------------------------------------------

SECTION 001

SelfTest being done.
SelfTest done successfully.

SECTION 002

Butterfly Seek Test being done.
10% Complete
20% Complete
30% Complete
40% Complete
50% Complete
60% Complete
70% Complete
80% Complete
90% Complete
100% Complete
Butterfly Seek Test done successfully.

SECTION 003

Read Media Test being done.
.......... 10% Complete
.......... 20% Complete
.......... 30% Complete
.......... 40% Complete
.......... 50% Complete
.......... 60% Complete
.......... 70% Complete
.......... 80% Complete
.......... 90% Complete
..........100% Complete
Read Media Test done successfully.

RUN COMPLETED.
DISKUTIL>

All other accessable diagnostics were run without indcident.

After rebooted syslog.log messages start again even though the machine
appears to be working fine. Since diagmon is started at startup do
you think there would be diagmon log entries? I can't remember how to
display diagmon logs. Any ideas?

Any help would be appreciated.

Ken