Dear all:

I have a very similar problem as Roland Smith almost two years ago. My hard drive got corrupted (I do not really know why) and when running fsck the first error message is "ROOT INODE UNALLOCATED" (the full output of fsck is given below. I can then type "y" and it looks like 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 cannot be created. If I mount the file system, there is still no root directory on the drive (no "." and ".." or anything else) and if I run 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 "." and ".." in the root directory but nothing more. Running again fsck 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 there a chance to get the data back? I do not know if it is important 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=2  OWNER=root MODE=40755
SIZE=2048 MTIME=Nov 16 17:21 2010
DIR=/

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

BAD TYPE VALUE  I=2  OWNER=root MODE=40755
SIZE=2048 MTIME=Nov 16 17:21 2010
DIR=/

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

BAD TYPE VALUE FOR '..'  I=151745536  OWNER=root MODE=40755
SIZE=512 MTIME=Oct 19 17:19 2010
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

BAD TYPE VALUE  I=2  OWNER=root MODE=40755
SIZE=2048 MTIME=Nov 16 17:21 2010
DIR=

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

BAD TYPE VALUE FOR '..'  I=301465600  OWNER=root MODE=40755
SIZE=19968 MTIME=Nov 12 09:16 2010
DIR=?

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

BAD TYPE VALUE  I=2  OWNER=root MODE=40755
SIZE=2048 MTIME=Nov 16 17:21 2010
DIR=

UNEXPECTED SOFT UPDATE INCONSISTENCY

FIX? [yn] y

** Phase 3 - Check Connectivity
UNREF DIR  I=151745536  OWNER=root MODE=40755
SIZE=512 MTIME=Oct 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=301465600  OWNER=root MODE=40755
SIZE=19968 MTIME=Nov 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=151745536  OWNER=root MODE=40755
SIZE=512 MTIME=Oct 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 *****
--
________________________________________________________________________________

Dr. Thomas E. Exner
Juniorprofessur "Theoretische Chemische Dynamik"
Fachbereich Chemie
Universität Konstanz
78457 Konstanz

Tel.: +49-(0)7531-882015
Fax:  +49-(0)7531-883587
Email: thomas.ex...@uni-konstanz.de
________________________________________________________________________________

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to