V890自动重启，帮忙分析一下（/crash里面没有产生文件）

lidasuai

一台V890接HP的阵列，双路光纤做负载。上周6主机自动重启，在/var/crash/`uname -n`/里面没有产生文件。下面的内容是当日的message信息。大家帮忙分析一下是什么原因？\r\n\r\nAug 26 19:02:22 s1 eri: [ID 517527 kern.info] SUNW,eri0 : Local Ethernet address = 0:3:ba:db:e1:c9\r\nAug 26 19:02:22 s1 pcisch: [ID 370704 kern.info] PCI-device: network@1,1, eri0\r\nAug 26 19:02:22 s1 genunix: [ID 936769 kern.info] eri0 is /pci@9,700000/network@1,1\r\nAug 26 19:02:26 s1 scsi: [ID 365881 kern.info] /pci@9,600000/scsi@1/st@3,0 (st3):\r\nAug 26 19:02:26 s1         <HP DAT-72>\r\nAug 26 19:02:26 s1 scsi: [ID 193665 kern.info] st3 at mpt0: target 3 lun 0\r\nAug 26 19:02:26 s1 genunix: [ID 936769 kern.info] st3 is /pci@9,600000/scsi@1/st@3,0\r\nAug 26 19:02:27 s1 ebus: [ID 521012 kern.info] su0 at ebus0: offset 1,3062f8\r\nAug 26 19:02:27 s1 genunix: [ID 936769 kern.info] su0 is /pci@9,700000/ebus@1/rsc-control@1,3062f8\r\nAug 26 19:02:27 s1 ebus: [ID 521012 kern.info] su1 at ebus0: offset 1,3083f8\r\nAug 26 19:02:27 s1 genunix: [ID 936769 kern.info] su1 is /pci@9,700000/ebus@1/rsc-console@1,3083f8\r\nAug 26 19:02:32 s1 scsi: [ID 799468 kern.info] ses32 at fp0: name w50800200001f55c1,0, bus address dc\r\nAug 26 19:02:32 s1 genunix: [ID 936769 kern.info] ses32 is /pci@8,600000/SUNW,qlc@2/fp@0,0/ses@w50800200001f55c1,0\r\nAug 26 19:02:32 s1 pseudo: [ID 129642 kern.info] pseudo-device: fssnap0\r\nAug 26 19:02:32 s1 genunix: [ID 936769 kern.info] fssnap0 is /pseudo/fssnap@0\r\nAug 26 19:02:32 s1 pseudo: [ID 129642 kern.info] pseudo-device: winlock0\r\nAug 26 19:02:32 s1 genunix: [ID 936769 kern.info] winlock0 is /pseudo/winlock@0\r\nAug 26 19:02:32 s1 pseudo: [ID 129642 kern.info] pseudo-device: lockstat0\r\nAug 26 19:02:32 s1 genunix: [ID 936769 kern.info] lockstat0 is /pseudo/lockstat@0\r\nAug 26 19:02:32 s1 pseudo: [ID 129642 kern.info] pseudo-device: llc10\r\nAug 26 19:02:32 s1 genunix: [ID 936769 kern.info] llc10 is /pseudo/llc1@0\r\nAug 26 19:02:33 s1 pseudo: [ID 129642 kern.info] pseudo-device: lofi0\r\nAug 26 19:02:33 s1 genunix: [ID 936769 kern.info] lofi0 is /pseudo/lofi@0\r\nAug 26 19:02:33 s1 pseudo: [ID 129642 kern.info] pseudo-device: fcp0\r\nAug 26 19:02:33 s1 genunix: [ID 936769 kern.info] fcp0 is /pseudo/fcp@0\r\nAug 26 19:02:33 s1 ebus: [ID 521012 kern.info] gpio_873170 at ebus0: offset 1,300600\r\nAug 26 19:02:33 s1 genunix: [ID 936769 kern.info] gpio_873170 is /pci@9,700000/ebus@1/gpio@1,300600\r\nAug 26 19:02:33 s1 pseudo: [ID 129642 kern.info] pseudo-device: rsm0\r\nAug 26 19:02:33 s1 genunix: [ID 936769 kern.info] rsm0 is /pseudo/rsm@0\r\nAug 26 19:02:33 s1 ge: [ID 580805 kern.info] SUNW,pci-gem0: SUNW,pci-gem (Rev Id = 1) Found\r\nAug 26 19:02:33 s1 ge: [ID 580805 kern.info] SUNW,pci-gem0: Local Ethernet address = 0:3:ba:db:e1:ca\r\nAug 26 19:02:33 s1 pcisch: [ID 370704 kern.info] PCI-device: network@1, ge0\r\nAug 26 19:02:33 s1 genunix: [ID 936769 kern.info] ge0 is /pci@8,600000/network@1\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd0\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd0 is /pseudo/wrsmd@0\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd1\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd1 is /pseudo/wrsmd@1\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd2\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd2 is /pseudo/wrsmd@2\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd3\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd3 is /pseudo/wrsmd@3\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd4\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd4 is /pseudo/wrsmd@4\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd5\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd5 is /pseudo/wrsmd@5\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd6\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd6 is /pseudo/wrsmd@6\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd7\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd7 is /pseudo/wrsmd@7\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd8\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd8 is /pseudo/wrsmd@8\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd9\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd9 is /pseudo/wrsmd@9\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd10\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd10 is /pseudo/wrsmd@10\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd11\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd11 is /pseudo/wrsmd@11\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd12\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd12 is /pseudo/wrsmd@12\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd13\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd13 is /pseudo/wrsmd@13\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd14\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd14 is /pseudo/wrsmd@14\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: wrsmd15\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] wrsmd15 is /pseudo/wrsmd@15\r\nAug 26 19:02:34 s1 pseudo: [ID 129642 kern.info] pseudo-device: fcsm0\r\nAug 26 19:02:34 s1 genunix: [ID 936769 kern.info] fcsm0 is /pseudo/fcsm@0\r\nAug 26 19:27:57 s1 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.8 Version Generic_117350-26 64-bit\r\nAug 26 19:27:57 s1 genunix: [ID 913632 kern.notice] Copyright 1983-2003 Sun Microsystems, Inc.  All rights reserved.\r\nAug 26 19:27:57 s1 genunix: [ID 678236 kern.info] Ethernet address = 0:3:ba:db:e1:c9\r\nAug 26 19:27:57 s1 unix: [ID 389951 kern.info] mem = 16777216K (0x400000000)\r\nAug 26 19:27:57 s1 unix: [ID 930857 kern.info] avail mem = 16526458880\r\nAug 26 19:27:57 s1 unix: [ID 796976 kern.notice] System booting after fatal error FATAL Sys Hardware\r\nAug 26 19:27:57 s1 rootnex: [ID 466748 kern.info] root nexus = Sun Fire V890\r\nAug 26 19:27:57 s1 rootnex: [ID 349649 kern.info] pcisch0 at root: SAFARI 0x8 0x700000\r\nAug 26 19:27:57 s1 genunix: [ID 936769 kern.info] pcisch0 is /pci@8,700000\r\nAug 26 19:27:57 s1 rootnex: [ID 349649 kern.info] pcisch1 at root: SAFARI 0x8 0x600000\r\nAug 26 19:27:57 s1 genunix: [ID 936769 kern.info] pcisch1 is /pci@8,600000\r\nAug 26 19:27:57 s1 rootnex: [ID 349649 kern.info] pcisch2 at root: SAFARI 0x9 0x700000\r\nAug 26 19:27:57 s1 genunix: [ID 936769 kern.info] pcisch2 is /pci@9,700000\r\nAug 26 19:27:57 s1 rootnex: [ID 349649 kern.info] pcisch3 at root: SAFARI 0x9 0x600000\r\nAug 26 19:27:57 s1 genunix: [ID 936769 kern.info] pcisch3 is /pci@9,600000\r\nAug 26 19:27:57 s1 qlc: [ID 171021 kern.info] Qlogic FCA Driver v20050209-1.40 (1)

milan

怎么感觉少了点启动前的信息？POST之

lidasuai

整个message里面只有我加了下划线的地方提示到了系统遇到故障。但是没有发现别的错误信息。

solarislog

我遇到多次这样的情况，都是找不到原因为什么会“ System booting after fatal error FATAL Sys Hardware”\r\n打电话给Sun, 他只会叫你装个explorer，收集一些信息，但多半不了了之。他们还有叫你接个console，如果下次再有同样问题，希望在console里可以看到些东西。我觉得现在你能做的也只有这样了。你还可以把OBP升级一下。

metor78

做个post，目前看不出哪里问题。

simbar

原帖由 solarislog 于 2006-8-28 16:15 发表\r\n我遇到多次这样的情况，都是找不到原因为什么会“ System booting after fatal error FATAL Sys Hardware”\r\n打电话给Sun, 他只会叫你装个explorer，收集一些信息，但多半不了了之。他们还有叫你接个console，如果 ...

\r\n其实他说的有道理的，有些器件，比如CPU之类的，出现某种问题的时候，会自动重起，起来做post 查不到任何问题，但过段时间（一天，一周也可能是一小时）会再次重起， 但其显示的log 太快，system来不及往messages里面写好, 系统已经重启了.  接个console, 最好 是notebook接个可以记录日志的, 这样就可以找到问题.

lidasuai

哦哦。原来是这样啊。在串口上接个notebook来记录日志是个好方法。现在V890主机上在跑应用，不能停机的，POST是没法做了。客户就是要一个说法，为什么会莫明其妙的停机。我已经采集了explorer文件下来。查了半天也看不到什么可疑的信息。

phage

可以和客户说，还需要观察两天。吼吼