Hi Jim, Thanks for the pointers. I'll definitely look into this.
-- Peter Blajev IT Manager, TAAZ Inc. Office: 858-597-0512 x125 On Wed, Mar 20, 2013 at 11:29 AM, Jim Klimov <jimkli...@cos.ru> wrote: > On 2013-03-20 17:15, Peter Wood wrote: > >> I'm going to need some help with the crash dumps. I'm not very familiar >> with Solaris. >> >> Do I have to enable something to get the crash dumps? Where should I >> look for them? >> > > Typically the kernel crash dumps are created as a result of kernel > panic; also they may be forced by administrative actions like NMI. > They require you to configure a dump volume of sufficient size (see > dumpadm) and a /var/crash which may be a dataset on a large enough > pool - after the reboot the dump data will be migrated there. > > To "help" with the hangs you can try the BIOS watchdog (which would > require a bmc driver, one which is known from OpenSolaris is alas > not opensourced and not redistributable), or with a software deadman > timer: > > http://www.cuddletech.com/**blog/pivot/entry.php?id=1044<http://www.cuddletech.com/blog/pivot/entry.php?id=1044> > > http://wiki.illumos.org/**display/illumos/System+Hangs<http://wiki.illumos.org/display/illumos/System+Hangs> > > Also, if you configure "crash dump on NMI" and set up your IPMI card, > then you can likely gain remote access to both the server console > ("physical" and/or serial) and may be able to trigger the NMI, too. > > HTH, > //Jim > > >> Thanks for the help. >> >> >> On Wed, Mar 20, 2013 at 8:53 AM, Michael Schuster >> <michaelspriv...@gmail.com >> <mailto:michaelsprivate@gmail.**com<michaelspriv...@gmail.com>>> >> wrote: >> >> How about crash dumps? >> >> michael >> >> >> On Wed, Mar 20, 2013 at 4:50 PM, Peter Wood <peterwood...@gmail.com >> <mailto:peterwood...@gmail.com**>> wrote: >> >> I'm sorry. I should have mentioned it that I can't find any >> errors in the logs. The last entry in /var/adm/messages is that >> I removed the keyboard after the last reboot and then it shows >> the new boot up messages when I boot up the system after the >> crash. The BIOS log is empty. I'm not sure how to check the IPMI >> but IPMI is not configured and I'm not using it. >> >> Just another observation - the crashes are more intense the more >> data the system serves (NFS). >> >> I'm looking into FRMW upgrades for the LSI now. >> >> >> On Wed, Mar 20, 2013 at 8:40 AM, Will Murnane >> <will.murn...@gmail.com <mailto:will.murn...@gmail.com**>> wrote: >> >> Does the Supermicro IPMI show anything when it crashes? >> Does anything show up in event logs in the BIOS, or in >> system logs under OI? >> >> >> On Wed, Mar 20, 2013 at 11:34 AM, Peter Wood >> <peterwood...@gmail.com <mailto:peterwood...@gmail.com**>> >> wrote: >> >> I have two identical Supermicro boxes with 32GB ram. >> Hardware details at the end of the message. >> >> They were running OI 151.a.5 for months. The zpool >> configuration was one storage zpool with 3 vdevs of 8 >> disks in RAIDZ2. >> >> The OI installation is absolutely clean. Just >> next-next-next until done. All I do is configure the >> network after install. I don't install or enable any >> other services. >> >> Then I added more disks and rebuild the systems with OI >> 151.a.7 and this time configured the zpool with 6 vdevs >> of 5 disks in RAIDZ. >> >> The systems started crashing really bad. They >> just disappear from the network, black and unresponsive >> console, no error lights but no activity indication >> either. The only way out is to power cycle the system. >> >> There is no pattern in the crashes. It may crash in 2 >> days in may crash in 2 hours. >> >> I upgraded the memory on both systems to 128GB at no >> avail. This is the max memory they can take. >> >> In summary all I did is upgrade to OI 151.a.7 and >> reconfigured zpool. >> >> Any idea what could be the problem. >> >> Thank you >> >> -- Peter >> >> Supermicro X9DRH-iF >> Xeon E5-2620 @ 2.0 GHz 6-Core >> LSI SAS9211-8i HBA >> 32x 3TB Hitachi HUS723030ALS640, SAS, 7.2K >> >> ______________________________**_________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> >> <mailto:zfs-discuss@**opensolaris.org<zfs-discuss@opensolaris.org> >> > >> >> http://mail.opensolaris.org/** >> mailman/listinfo/zfs-discuss<http://mail.opensolaris.org/mailman/listinfo/zfs-discuss> >> >> >> >> >> ______________________________**_________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> <mailto:zfs-discuss@**opensolaris.org<zfs-discuss@opensolaris.org> >> > >> >> >> http://mail.opensolaris.org/**mailman/listinfo/zfs-discuss<http://mail.opensolaris.org/mailman/listinfo/zfs-discuss> >> >> >> >> >> -- >> Michael Schuster >> >> http://recursiveramblings.**wordpress.com/<http://recursiveramblings.wordpress.com/> >> >> >> >> >> ______________________________**_________________ >> zfs-discuss mailing list >> zfs-discuss@opensolaris.org >> http://mail.opensolaris.org/**mailman/listinfo/zfs-discuss<http://mail.opensolaris.org/mailman/listinfo/zfs-discuss> >> >> > ______________________________**_________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/**mailman/listinfo/zfs-discuss<http://mail.opensolaris.org/mailman/listinfo/zfs-discuss> >
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
