Generally speaking, whenever you notice a fatal reset, as represented by the three magic words "<i>fatal error FATAL</i>", you'll have virtually no information in the messages file.
Your system had such an abrupt event that Solaris had no opportunity to log anything before the reboot.You could `maybe` get a hint if there were many DIMM errors or file-system-full errors in the minutes before the reboot, but those would only be hints and not the actual cause of the event.
A fatal reset gives you information through only one method.Your console.
... and of course you have your console logged and saved?
[probably not.very few people do that.]
If the V880 is up and sems to be functional, you have only one recourse for the near future: establish a dedicated logging console output and hope the system breaks again.
There was two lines referencing memory immediately prior to the FATAL Sys Hardware error message;
mem = <a ten digit number> (0 x 80000000000)
avail mem = <another ten digit number>
I just established a dedicated logging console just in case this happens again.
See my response above:
" Your system had such an abrupt event that Solaris had no opportunity to log anything before the reboot.You could `maybe` get a hint if there were many errors in the minutes before the reboot, but those would only be hints and not the actual cause of the event.
A fatal reset gives you information through only one methodYour console.
... and of course you have your console logged and saved?
( probably not.very few people do that. ) "
Use your service contract and open a support case with your local Sun Support Center.
http://www.sun.com/contact/index.jsp?tab=3
Let techsupport try to analyze the event.That is why they are on the payroll.
These forums are only user-to-user discussions.