From owner-freebsd-questions  Mon Apr 15  5:13:27 2002
Delivered-To: freebsd-questions@freebsd.org
Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52])
	by hub.freebsd.org (Postfix) with ESMTP id CBAE337B404
	for <freebsd-questions@freebsd.org>; Mon, 15 Apr 2002 05:13:22 -0700 (PDT)
Received: from i8k.babbleon.org ([66.57.86.84]) by mail5.nc.rr.com  with Microsoft SMTPSVC(5.5.1877.687.68);
	 Mon, 15 Apr 2002 08:12:47 -0400
Received: by i8k.babbleon.org (Postfix, from userid 111)
	id DB42ABB39; Mon, 15 Apr 2002 08:12:22 -0400 (EDT)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Brian T.Schellenberger <bts@babbleon.org>
To: "alexus" <ml@db.nexgen.com>, <freebsd-questions@FreeBSD.ORG>
Subject: Re: incorrect super block
Date: Mon, 15 Apr 2002 08:12:22 -0400
X-Mailer: KMail [version 1.3]
References: <000901c1e44a$c9b06ce0$faa0b542@noc>
In-Reply-To: <000901c1e44a$c9b06ce0$faa0b542@noc>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-Id: <20020415121222.DB42ABB39@i8k.babbleon.org>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

On Monday 15 April 2002 02:57 am, alexus wrote:
| hi
|
| i have a raid and when i'm trying i'm bootin it up i get this
|
| incorrect super block
|
| here is my mount line from /etc/fstab
|
| /dev/amrd0s1e /mnt/raid ufs rw,noatime 0 0
|
| anyone have any ideas what could be wrong?

You have an incorrect super block.

That means, basically, that the header at the start of the file system has 
gotten corrupted.  This is bad, but (from section 8 of the FBSD fsck man 
page):

     -b      Use the block specified immediately after the flag as the super
             block for the filesystem.  Block 32 is usually an alternate super
             block.


So try

   fsck -b 32

If that doesn't work, then I hope you have a backup of the file system as 
it's probably toast.  If you don't have a backup of the file system, you'll 
need to start learning a lot FreeBSD file systems and how to repair them.

|
|
| To Unsubscribe: send mail to majordomo@FreeBSD.org
| with "unsubscribe freebsd-questions" in the body of the message

-- 
Brian T. Schellenberger . . . . . . .   bts@wnt.sas.com (work)
Brian, the man from Babble-On . . . .   bts@babbleon.org (personal)
                                ME -->  http://www.babbleon.org
http://www.eff.org   <-- GOOD GUYS -->  http://www.programming-freedom.org 

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message