From owner-freebsd-questions  Mon Jul 22 00:48:20 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id AAA24684
          for questions-outgoing; Mon, 22 Jul 1996 00:48:20 -0700 (PDT)
Received: from ki.net (root@ki.net [205.150.102.1])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id AAA24679
          for <freebsd-questions@freebsd.org>; Mon, 22 Jul 1996 00:48:17 -0700 (PDT)
Received: from localhost (scrappy@localhost) by ki.net (8.7.5/8.7.5) with SMTP id DAA00892; Mon, 22 Jul 1996 03:47:59 -0400 (EDT)
Date: Mon, 22 Jul 1996 03:47:59 -0400 (EDT)
From: "Marc G. Fournier" <scrappy@ki.net>
To: Paul Reece <paul@tassie.net.au>
cc: freebsd-questions@freebsd.org
Subject: Re: help! panic! ;)
In-Reply-To: <Pine.BSF.3.91.960722165540.817A-100000@merlin.tassie.net.au>
Message-ID: <Pine.NEB.3.94.960722034657.272D-100000@ki.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Mon, 22 Jul 1996, Paul Reece wrote:

> 
> Anyone have any quick solutions (besides using mkfs) to get fsck through 
> this?:
> 
> merlin# fsck -n /dev/sd0s1a
> ** /dev/rsd0s1a (NO WRITE)
> BAD SUPER BLOCK: MAGIC NUMBER WRONG
> Floating exception (core dumped)
> 
> 
> The disk corrupted itself and as you can expect, barfs during rebooting..
> 
> Suggestions GREATLY appreciated...
>

	Don't know if this helps, but remembered it fro mback in my BSDi
days:

>From FreeBSD's 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, I'd assume something like: fsck -n -b 32 /dev/sd0s1a ?



Marc G. Fournier                                  scrappy@ki.net
Systems Administrator @ ki.net               scrappy@freebsd.org