string

2. Major kernel configuration faults, such as a buggy device driver;
3. Major kernel tuning errors, such as a too-large value for maxusers;
4. Data corruption, including corruption of the operating system files;
5. Manual intervention is needed, as when fsck(1M) expects answers to its queries.
Action
To find out why a system crashed, you can
1. Look in the /var/adm/message* log files;
Action
Of these methods, using savecore(1M) is the most informative. The
savecore(1M) command transfers the system crash dump image generated by the
panic routine from the dump device to a file system. The image can then be analyzed
with a debugger such as adb(1).
See Also
Correctly setting up savecore(1M) and interpreting its results can be difficult. For
more information about debugging system panics, refer to Panic! UNIX System
Crash Dump Analysis by Chris Drake and Kimberley Brown (ISBN 0-13-149386-8).
PARTIALLY ALLOCATED INODE I=int CLEAR?
Cause
During phase 1, fsck(1M) found that the specified inode was neither allocated nor
unallocated. The reason is probably that the system crashed in the middle of a
sync(2) or write(2) operation.
Action
Should you answer yes to this question, "UNALLOCATED" messages might result
during phase 2, if any directory entries point to this inode. If you are being careful,
exit fsck(1M) and run ncheck(1M) (specifying the inode number after the -i
option) to determine which file or directory is involved here. You might be able
restore this file or directory from another system. It is also possible that fsck(1M)
will copy this file to the lost+found directory in a later phase.
Alphabetical Message Listing 153