From owner-freebsd-fs@FreeBSD.ORG Mon Feb 23 11:13:24 2004 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9393916A4CE for ; Mon, 23 Feb 2004 11:13:24 -0800 (PST) Received: from happy.cow.org (happy.cow.org [216.130.13.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F33443D1D for ; Mon, 23 Feb 2004 11:13:24 -0800 (PST) (envelope-from ravi@cow.org) Received: by happy.cow.org (Postfix, from userid 1001) id 5CA5AEBE0A; Mon, 23 Feb 2004 14:13:18 -0500 (EST) Date: Mon, 23 Feb 2004 14:13:18 -0500 From: ravi pina To: freebsd-fs@freebsd.org Message-ID: <20040223191318.GA69611@happy.cow.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Subject: Possible corrupt disklabel and more X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: ravi@cow.org List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Feb 2004 19:13:24 -0000 hi. i have a 4 disk raid5 using the 3ware 7410 using their fbsd driver on 4.8. at one point one of my targets failed and the system seized. not knowing the former, i rebooted the system and it did its regular fsck. after finding a unusually large number of mussing or corrupt inodes, i stopped the check and left the volume mounted read only. accessing (i'm guessing) certain parts of the array while in the degraded state caused the kernel to panic. after (finally) learning of the state of the array i left it dismounted until i was able to replace the disk. after doing so the array appeared to rebuild fine and it went from a degraded state to a ok state. long story short: it seems the disklabel got blown away and other filesystem important data is corrupt preventing me from accessing data. so my question is: is the data still there and if so, will recreating the disklabel by hand and doing a newfs -N to find where the alternate superblocks may reside bring me any closer to getting the data back without having to seriously consider professional data recovery? if so, how would i go about zeroing out the corrupt disklabel and manually creating a new one? specifically how would i obtain the drive geometry suitable for a disklabel import? thanks a bunch, -r --