Date: Thu, 18 Nov 2010 10:41:56 +0100 From: Thomas Exner <thomas.exner@uni-konstanz.de> To: freebsd-questions@freebsd.org Subject: disk recovery problem(s) Message-ID: <4CE4F4E4.10606@uni-konstanz.de>
next in thread | raw e-mail | index | archive | help
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 _________________________________________________________________________= _______
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4CE4F4E4.10606>