From owner-freebsd-questions@FreeBSD.ORG Thu Nov 18 10:11:18 2010 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 EBFF6106564A for ; Thu, 18 Nov 2010 10:11:18 +0000 (UTC) (envelope-from thomas.exner@uni-konstanz.de) Received: from pyrimidin.rz.uni-konstanz.de (pyrimidin.rz.uni-konstanz.de [134.34.240.46]) by mx1.freebsd.org (Postfix) with ESMTP id 7FF208FC22 for ; Thu, 18 Nov 2010 10:11:18 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.59,216,1288569600"; d="scan'208";a="14179811" Received: from alanine.chemie.uni-konstanz.de (HELO [10.0.0.65]) ([134.34.110.7]) by mailhub.uni-konstanz.de with ESMTP; 18 Nov 2010 09:41:56 +0000 Message-ID: <4CE4F4E4.10606@uni-konstanz.de> Date: Thu, 18 Nov 2010 10:41:56 +0100 From: Thomas Exner User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.14) Gecko/20101013 SUSE/2.0.9-0.5.1 SeaMonkey/2.0.9 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Subject: disk recovery problem(s) 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: Thu, 18 Nov 2010 10:11:19 -0000 Dear all: I have a very similar problem as Roland Smith almost two years ago. My=20 hard drive got corrupted (I do not really know why) and when running=20 fsck the first error message is "ROOT INODE UNALLOCATED" (the full=20 output of fsck is given below. I can then type "y" and it looks like=20 that fsck is doing something. But in phase 3, when it tries to reconnect = the inodes and put them in the lost+found directory, this directory=20 cannot be created. If I mount the file system, there is still no root=20 directory on the drive (no "." and ".." or anything else) and if I run=20 fsck again, the exact same error massages occur again. If I only perform = the "ALLOCATE?" and answer all the other questions with "no", I get a=20 "." and ".." in the root directory but nothing more. Running again fsck=20 destroys everything again. Does anyone have an idea why fsck is not able = to perform the recovery or why the changes are undone at one point? Is=20 there a chance to get the data back? I do not know if it is important=20 but the file system is on a raid5. Any help would be highly appreciated. Best, Thomas Full fsck output: nas1:/mnt# /sbin/fsck -t ufs -f /dev/raid5/nasraid1p1 ** /dev/raid5/nasraid1p1 ** Last Mounted on /mnt/nasraid1 ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ROOT INODE UNALLOCATED UNEXPECTED SOFT UPDATE INCONSISTENCY ALLOCATE? [yn] y BAD TYPE VALUE I=3D2 OWNER=3Droot MODE=3D40755 SIZE=3D2048 MTIME=3DNov 16 17:21 2010 DIR=3D/ UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y BAD TYPE VALUE I=3D2 OWNER=3Droot MODE=3D40755 SIZE=3D2048 MTIME=3DNov 16 17:21 2010 DIR=3D/ UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y BAD TYPE VALUE FOR '..' I=3D151745536 OWNER=3Droot MODE=3D40755 SIZE=3D512 MTIME=3DOct 19 17:19 2010 DIR=3D? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y BAD TYPE VALUE I=3D2 OWNER=3Droot MODE=3D40755 SIZE=3D2048 MTIME=3DNov 16 17:21 2010 DIR=3D UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y BAD TYPE VALUE FOR '..' I=3D301465600 OWNER=3Droot MODE=3D40755 SIZE=3D19968 MTIME=3DNov 12 09:16 2010 DIR=3D? UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y BAD TYPE VALUE I=3D2 OWNER=3Droot MODE=3D40755 SIZE=3D2048 MTIME=3DNov 16 17:21 2010 DIR=3D UNEXPECTED SOFT UPDATE INCONSISTENCY FIX? [yn] y ** Phase 3 - Check Connectivity UNREF DIR I=3D151745536 OWNER=3Droot MODE=3D40755 SIZE=3D512 MTIME=3DOct 19 17:19 2010 RECONNECT? [yn] y NO lost+found DIRECTORY CREATE? [yn] y SORRY. CANNOT CREATE lost+found DIRECTORY UNEXPECTED SOFT UPDATE INCONSISTENCY UNREF DIR I=3D301465600 OWNER=3Droot MODE=3D40755 SIZE=3D19968 MTIME=3DNov 12 09:16 2010 RECONNECT? [yn] y NO lost+found DIRECTORY CREATE? [yn] y SORRY. CANNOT CREATE lost+found DIRECTORY UNEXPECTED SOFT UPDATE INCONSISTENCY UNREF DIR I=3D151745536 OWNER=3Droot MODE=3D40755 SIZE=3D512 MTIME=3DOct 19 17:19 2010 RECONNECT? [yn] y NO lost+found DIRECTORY CREATE? [yn] y SORRY. CANNOT CREATE lost+found DIRECTORY UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups SUMMARY INFORMATION BAD SALVAGE? [yn] y BLK(S) MISSING IN BIT MAPS SALVAGE? [yn] y 35257960 files, 1247115068 used, 171932417 free (5559497 frags, 20796615 = blocks, 0.4% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** ***** FILE SYSTEM WAS MODIFIED ***** --=20 _________________________________________________________________________= _______ Dr. Thomas E. Exner Juniorprofessur "Theoretische Chemische Dynamik" Fachbereich Chemie Universit=E4t Konstanz 78457 Konstanz Tel.: +49-(0)7531-882015 Fax: +49-(0)7531-883587 Email: thomas.exner@uni-konstanz.de _________________________________________________________________________= _______