From owner-freebsd-questions@FreeBSD.ORG Fri Jan 14 00:35:45 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E5301065672 for ; Fri, 14 Jan 2011 00:35:45 +0000 (UTC) (envelope-from web@3dresearch.com) Received: from smtp.3dresearch.com (dorabella.3dresearch.com [66.167.251.2]) by mx1.freebsd.org (Postfix) with ESMTP id 39C138FC19 for ; Fri, 14 Jan 2011 00:35:44 +0000 (UTC) Received: from fracasso.3dresearch.com (pool-96-236-232-63.pitbpa.east.verizon.net [96.236.232.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by vmail.3dresearch.com (Postfix) with ESMTP id 350056D3AA for ; Thu, 13 Jan 2011 19:35:44 -0500 (EST) Received: from fracasso.3dresearch.com (localhost [127.0.0.1]) by fracasso.3dresearch.com (Postfix) with SMTP id 4BF995D25 for ; Thu, 13 Jan 2011 19:35:43 -0500 (EST) Date: Thu, 13 Jan 2011 19:14:39 -0500 From: Janos Dohanics To: freebsd-questions@freebsd.org Message-Id: <20110113191439.5c108486.web@3dresearch.com> X-Mailer: Sylpheed 3.0.3 (GTK+ 2.22.1; amd64-portbld-freebsd8.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Attempt to write outside dump device boundaries X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2011 00:35:45 -0000 I have been having problems with a newly built system which I have installed 8.2-PRERELEASE amd64. One problem I posted at http://lists.freebsd.org/pipermail/freebsd-questions/2011-January/225822.html (Fernando, thank you for replying). After wiping and reinstalling, I made sure that I could obtain a kernel dump. Next, I have set up gmirror. Upon reboot, synchronizing the mirror was going very slow. I checked the drives with smartctl; one drive turned out to be faulty. Next, removed the faulty drive from gmirror, and did reboot -d. At this point, I got the error "Attempt to write outside dump device boundaries" similar to what's described in http://lists.freebsd.org/pipermail/freebsd-stable/2008-December/046982.html Once the system came back up, and I could verify that the faulty drive was no longer part of gmirror, did reboot -d again, which caused the same error. Next, physically disconnected the faulty drive, and had no problem getting a kernel dump. Next, reconnected the faulty drive, but did not insert it into gmirror, and had no problem getting a kernel dump. I obviously need to replace the faulty drive. Beyond that, I'm wondering if someone could explain why is it not possible to get a kernel dump when a drive in gmirror fails. -- Janos Dohanics