From owner-freebsd-questions@FreeBSD.ORG  Tue Jan  6 17:01:59 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 2044416A4CE
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jan 2004 17:01:59 -0800 (PST)
Received: from web41104.mail.yahoo.com (web41104.mail.yahoo.com
	[66.218.93.20])	by mx1.FreeBSD.org (Postfix) with SMTP id A448343D54
	for <freebsd-questions@freebsd.org>;
	Tue,  6 Jan 2004 17:01:54 -0800 (PST)
	(envelope-from scott@sremick.net)
Message-ID: <20040107010154.19289.qmail@web41104.mail.yahoo.com>
Received: from [65.174.25.25] by web41104.mail.yahoo.com via HTTP;
	Tue, 06 Jan 2004 17:01:54 PST
X-RocketYMMF: siremick
Date: Tue, 6 Jan 2004 17:01:54 -0800 (PST)
From: "Scott I. Remick" <scott@sremick.net>
To: Malcolm Kay <malcolm.kay@internode.on.net>
In-Reply-To: <200401070929.46078.malcolm.kay@internode.on.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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, 07 Jan 2004 01:01:59 -0000


--- Malcolm Kay <malcolm.kay@internode.on.net> wrote:
> 
> This is true. That partition is labeled as unused.
> I believe you should be trying to mount /dev/ad6s1e.

su-2.05b# mount -r /dev/ad6s1e /data
mount: /dev/ad6s1e on /data: incorrect super block


> > #/dev/ad6s1c            /data           ufs     rw              2      
> 2
> >
> 
> Certainly wrong in 4.x, I suspect also wrong in 5.x.

Yikes, well that's the way it had been for about a year. How come it worked?
I must have made an inexperienced mistake early on, but it WAS working. Can
this be fixed?

> Do you have a line mounting ad4s1c for the other disk?

No, that's the only one using the "c" partition.