From owner-freebsd-questions@FreeBSD.ORG  Wed Feb  4 06:06:09 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 270A416A4CE
	for <freebsd-questions@freebsd.org>;
	Wed,  4 Feb 2004 06:06:09 -0800 (PST)
Received: from web41115.mail.yahoo.com (web41115.mail.yahoo.com
	[66.218.93.31])	by mx1.FreeBSD.org (Postfix) with SMTP id 10CED43D31
	for <freebsd-questions@freebsd.org>;
	Wed,  4 Feb 2004 06:06:07 -0800 (PST)
	(envelope-from scott@sremick.net)
Message-ID: <20040204140606.17220.qmail@web41115.mail.yahoo.com>
Received: from [199.172.45.60] by web41115.mail.yahoo.com via HTTP;
	Wed, 04 Feb 2004 06:06:06 PST
X-RocketYMMF: siremick
Date: Wed, 4 Feb 2004 06:06:06 -0800 (PST)
From: "Scott I. Remick" <scott@sremick.net>
To: Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru>
In-Reply-To: <20040204132710.78956223@Hal.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: Jerry McAllister <jerrymc@clunix.cl.msu.edu>
cc: FreeBSD <freebsd-questions@freebsd.org>
Subject: Re: "Cannot find file system superblock" error - how to recover?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: scott@sremick.net
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: Wed, 04 Feb 2004 14:06:09 -0000


--- Sergey 'DoubleF' Zaharchenko <doublef@tele-kom.ru> wrote:
> Well, as it's UFS1 as we've figured out, the next logical thing would be
> to try mounting /dev/ad2s1c r/o, and if that fails, try fscking it.

bash-2.05b# mount -r /dev/ad2s1c /data
mount: /dev/ad2s1c on /data: incorrect super block

bash-2.05b# fsck /dev/ad2s1c
** /dev/ad2s1c
BAD SUPER BLOCK: MAGIC NUMBER WRONG
/dev/ad2s1c: NOT LABELED AS A BSD FILE SYSTEM (unused)