From owner-freebsd-geom@FreeBSD.ORG Thu Oct 13 05:00:17 2005 Return-Path: X-Original-To: freebsd-geom@freebsd.org Delivered-To: freebsd-geom@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AC43A16A41F for ; Thu, 13 Oct 2005 05:00:17 +0000 (GMT) (envelope-from cdjones-freebsd-geom@novusordo.net) Received: from correo.novusordo.net (cdjj.org [216.194.85.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58B0B43D45 for ; Thu, 13 Oct 2005 05:00:17 +0000 (GMT) (envelope-from cdjones-freebsd-geom@novusordo.net) Received: from [192.168.2.100] (S010600c049bda6b5.ed.shawcable.net [68.149.198.157]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by correo.novusordo.net (Postfix) with ESMTP id 6A6BD11522; Wed, 12 Oct 2005 23:00:16 -0600 (MDT) Message-ID: <434DE9E0.9030406@novusordo.net> Date: Wed, 12 Oct 2005 23:00:16 -0600 From: Chris Jones User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joshua Bell References: <20051012153312.71befe49.josh@oplink.net> <20051012170853.00097b64.josh@oplink.net> In-Reply-To: <20051012170853.00097b64.josh@oplink.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-geom@freebsd.org Subject: Re: GEOM causes kernel panic X-BeenThere: freebsd-geom@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GEOM-specific discussions and implementations List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 05:00:17 -0000 Joshua Bell wrote: >From this state, if I do anything like `gvinum start` it panics and reboots. If I am at console, I can see an errors, but unable to 'catch' all of it. > > I think your best bet is going to be trying to trap memory dumps prior to reboot and seeing if you can get any data out of that. See the Developer's Handbook, ch. 10 (http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html) for details. You may also be able to get a copy of some of the errors printed to the console by SSHing in from another machine and doing a 'tail -f /var/log/console.log'. Cheers, Chris