From owner-freebsd-questions@FreeBSD.ORG Sat Feb 7 00:17:35 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EA651065785 for ; Sat, 7 Feb 2009 00:17:35 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id C25D38FC13 for ; Sat, 7 Feb 2009 00:17:34 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r55.edvax.de (port-92-196-52-176.dynamic.qsc.de [92.196.52.176]) by mx02.qsc.de (Postfix) with ESMTP id E3ABD16C059D; Sat, 7 Feb 2009 01:17:33 +0100 (CET) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n170HXOt001585; Sat, 7 Feb 2009 01:17:33 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Sat, 7 Feb 2009 01:17:33 +0100 From: Polytropon To: Robert Huff Message-Id: <20090207011733.76c68040.freebsd@edvax.de> In-Reply-To: <18828.37913.857833.472632@jerusalem.litteratus.org> References: <18828.37913.857833.472632@jerusalem.litteratus.org> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: questions@freebsd.org Subject: Re: disk recovery problem(s) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2009 00:17:35 -0000 On Fri, 6 Feb 2009 14:48:41 -0500, Robert Huff wrote: > > Had a power outage recently; when trying to fsck several > external hard drives I'm getting unexpected errors. > For example: > > huff@>> fsck /dev/da3a > ** /dev/da3a > ** Last Mounted on /backup > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ROOT INODE UNALLOCATED > ALLOCATE? [yn] > > a) what's probably happened? > b) is there a way to recover the data? I can scrub the disk > and restore, but would like to avoid that if at all possible. I really hope you don't get into the trouble that I have (allthough you mentioned that you've got backups)... Your fsck output seems to indicate that fsck can handle the damage. You could now let it continue. If a parent inode has disappeared, its child inodes (orphaned ones) - or, to be correct, the files or directories they represent - get restored in the lost+found/ directory where their name (probably lost) gets replaced by the inode number. If it's a directory, it content will usually be present with the file names, only the topmost part of a hierarchy will be affected. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...