SUMMARY: Get the cause of a crash wtihout /var?

I asked

> I was updating a v490 from Sol10_u5 to Sol10_u10. The upgrade went fine,
but
> on reboot afterwards the /var partition was totally corrupted and could not
be
> mounted. I tried to fsck, but after thousands of unlinked inodes and the
like
> we newfs-ed the partition and restored from tape. The system is now fine
and
> updated. But management would (understandably) like a postmortem and
> root-cause-analysis report. Can anyone think of a way to get a record of
what
> happened on a system without using any information from /var?

The answer:

I'm pretty much SOL.  A few people pointed to consolehistory in the RSC, but
that will just record what was typed, What I was hoping for was a crash dump
file of some sort that could be analyzed after-the-fact.  After fscking ad
repopulating /var from tape, btw, the server is fine and has been running for
over a week now without issue.

Thanks to those who tried to help.  Much appreciated.

Christopher L. Barnard
-------------------
comment your code as if the maintainer is a homicidal maniac who knows where
you live.