From owner-freebsd-questions@FreeBSD.ORG  Sun Jul 22 09:53:35 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 6CA75106564A
	for <freebsd-questions@freebsd.org>;
	Sun, 22 Jul 2012 09:53:35 +0000 (UTC)
	(envelope-from bonomi@mail.r-bonomi.com)
Received: from mail.r-bonomi.com (mx-out.r-bonomi.com [204.87.227.120])
	by mx1.freebsd.org (Postfix) with ESMTP id 1021C8FC08
	for <freebsd-questions@freebsd.org>;
	Sun, 22 Jul 2012 09:53:34 +0000 (UTC)
Received: (from bonomi@localhost)
	by mail.r-bonomi.com (8.14.4/rdb1) id q6M9stCG021928;
	Sun, 22 Jul 2012 04:54:55 -0500 (CDT)
Date: Sun, 22 Jul 2012 04:54:55 -0500 (CDT)
From: Robert Bonomi <bonomi@mail.r-bonomi.com>
Message-Id: <201207220954.q6M9stCG021928@mail.r-bonomi.com>
To: freebsd-questions@freebsd.org, leslie@eskk.nu
In-Reply-To: <500ABECA.5010404@eskk.nu>
Cc: 
Subject: Re: Power failure during portsnap fetch update
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Jul 2012 09:53:35 -0000

> From owner-freebsd-questions@freebsd.org  Sat Jul 21 09:40:20 2012
> Date: Sat, 21 Jul 2012 16:38:02 +0200
> From: Leslie Jensen <leslie@eskk.nu>
> To: freebsd-questions@freebsd.org
> Subject: Power failure during portsnap fetch update
>
>
> My file system /usr/ports/net go damaged
>
> I've done fsck -F in single user mode but there are warnings about not 
> being able to fix this.

"Insufficient Data" for a meaningful response.  *sigh*

_Exactly_ WHAT the command line used was, and *WHAT* the exact text of
the error message says is needed before anyone can help.