From owner-freebsd-questions@FreeBSD.ORG Thu Nov 18 15:24:30 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2825116A4CE for ; Thu, 18 Nov 2004 15:24:30 +0000 (GMT) Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E30BC43D39 for ; Thu, 18 Nov 2004 15:24:29 +0000 (GMT) (envelope-from fbsd-questions@trini0.org) Received: from hivemind.trini0.org (trini0.org[65.34.205.195]) by comcast.net (rwcrmhc12) with ESMTP id <2004111815242901400adcvfe>; Thu, 18 Nov 2004 15:24:29 +0000 Received: from [192.168.0.16] (gladiator.trini0.org [192.168.0.16]) by hivemind.trini0.org (Postfix) with ESMTP id 7BBE86103; Thu, 18 Nov 2004 10:24:28 -0500 (EST) Message-ID: <419CBEAE.4060808@trini0.org> Date: Thu, 18 Nov 2004 10:24:30 -0500 From: Gerard Samuel User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <419B88F1.3090404@trini0.org> <20041118010559.GB95231@xor.obsecurity.org> <419C077B.5030501@trini0.org> <20041118023043.GA23972@xor.obsecurity.org> <419C2D38.4030601@trini0.org> <419CB7A0.4020608@trini0.org> In-Reply-To: <419CB7A0.4020608@trini0.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions Subject: Re: Corrupted Disk? [Was: Re: FreeBSD 5.x & CCD] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 15:24:30 -0000 Gerard Samuel wrote: > Gerard Samuel wrote: > >> Kris Kennaway wrote: >> >>> On Wed, Nov 17, 2004 at 09:22:51PM -0500, Gerard Samuel wrote: >>> >>> >>> >>>> Well you just burst my bubble. >>>> I was hoping I was missing a node. Im trying to figure out a >>>> problem Im >>>> having -> >>>> http://lists.freebsd.org/pipermail/freebsd-questions/2004-November/064973.html >>>> >>>> Thanks >>>> >>> >>> >>> >>> Just mount /dev/ccd0 instead of /dev/ccd0c since the latter refers to >>> the entire disk anyway. >>> >> >> Here is what I did... >> 1. Unconfigured ccd >> hivemind# ccdconfig -U -f /etc/ccd.conf >> 2. Reconfigured it >> hivemind# ccdconfig -C -f /etc/ccd.conf >> 3. Tried mount the drive the way you recommended, and got >> hivemind# mount /dev/ccd0 /storage >> mount: /dev/ccd0: Operation not permitted >> >> Im going to try googling to see what I can find out. >> But if anyone knows why I cannot mount this, then by all means, >> let me know. >> Thanks > > > I noticed this in the logs when I was trying to mount the disk -> > Nov 18 09:05:20 hivemind kernel: WARNING: R/W mount of /storage > denied. Filesystem is not clean - run fsck > > I ran fsck a few times, but it could fix the drive. > > hivemind# fsck -t ffs -y /dev/ccd0 > --snip-- > > ** Phase 2 - Check Pathnames > MISSING '.' I=896624 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:18 2004 > DIR=? > CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS mesg.27.2.jar > MISSING '..' I=896624 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:18 2004 > DIR=? > CANNOT FIX, SECOND ENTRY IN DIRECTORY CONTAINS mesg.28.2.jar > DIRECTORY CORRUPTED I=941361 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > > SALVAGE? yes > > MISSING '.' I=941361 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > > FIX? yes > > DIRECTORY CORRUPTED I=941362 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > > SALVAGE? yes > > MISSING '.' I=941362 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > > FIX? yes > > DIRECTORY CORRUPTED I=941365 OWNER=nobody MODE=40755 > SIZE=1024 MTIME=Jun 11 23:19 2004 > DIR=? > > SALVAGE? yes > > MISSING '.' I=941365 OWNER=nobody MODE=40755 > SIZE=1024 MTIME=Jun 11 23:19 2004 > DIR=? > > FIX? yes > > DIRECTORY CORRUPTED I=941393 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > > SALVAGE? yes > > MISSING '.' I=941393 OWNER=nobody MODE=40755 > SIZE=512 MTIME=Jun 11 23:19 2004 > DIR=? > CANNOT FIX, FIRST ENTRY IN DIRECTORY CONTAINS > fsck_ffs: inoinfo: inumber -2115204267 out of range > > > My question. If fsck cannot repair a drive, does it mean that all > hope is lost? > Thanks Ah forget it. I bit the bullet, and newfs'ed the ccd, and now it mounts without any complaints. So all that data went to /dev/null Note to self (and hopefully to others): Back up your ccd arrays before reinstalling the OS...