Date: Thu, 18 Nov 2004 10:24:30 -0500 From: Gerard Samuel <fbsd-questions@trini0.org> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Corrupted Disk? [Was: Re: FreeBSD 5.x & CCD] Message-ID: <419CBEAE.4060808@trini0.org> In-Reply-To: <419CB7A0.4020608@trini0.org> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?419CBEAE.4060808>