From owner-freebsd-stable  Fri Jun  4 14: 3:12 1999
Delivered-To: freebsd-stable@freebsd.org
Received: from ideaglobal.com (ultra2.ideaglobal.com [194.36.20.11])
	by hub.freebsd.org (Postfix) with ESMTP id A383E14E73
	for <freebsd-stable@FreeBSD.ORG>; Fri,  4 Jun 1999 14:03:07 -0700 (PDT)
	(envelope-from kiril@ideaglobal.com)
Received: (from kiril@localhost)
	by ideaglobal.com (8.9.2/8.9.2) id VAA19464;
	Fri, 4 Jun 1999 21:58:07 +0100 (BST)
From: Kiril Mitev <kiril@ideaglobal.com>
Message-Id: <199906042058.VAA19464@ideaglobal.com>
Subject: Re: vinum disk has gone AWOL, help!
To: Cy.Schubert@uumail.gov.bc.ca
Date: Fri, 4 Jun 1999 21:58:07 +0100 (BST)
Cc: kiril@ideaglobal.com, freebsd-stable@FreeBSD.ORG
In-Reply-To: <199906042014.NAA49261@passer.osg.gov.bc.ca> from "Cy Schubert" at Jun 4, 99 01:13:41 pm
X-Mailer: ELM [version 2.4 PL25]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

That looks like it might actually fix it, unless there
more corruption somewhere

thanks, thanks, thanks

Kiril

> 
> Try fsck -b 32 <filesystem>.
> 
> If that fails, try fsck -b <another number> <filesystem>.  To get 
> the other block numbers for alternate superblocks, use newfs -N, 
> which will go through all of the motions of creating a filesystem, 
> e.g. print the superblock numbers, without actually creating a 
> filesystem.  If this fails, you're pretty much hosed.
> 
> 
> Regards,                       Phone:  (250)387-8437
> Cy Schubert                      Fax:  (250)387-5766
> Open Systems Group          Internet:  Cy.Schubert@uumail.gov.bc.ca
> ITSD                                   Cy.Schubert@gems8.gov.bc.ca
> Province of BC            
>                       "e**(i*pi)+1=0"
> 
> In message <199906041920.UAA17798@ideaglobal.com>, Kiril Mitev 
> writes:
> > (Sorry if this is more appropriate for -questions...)
> > 
> > 
> > after my last reboot, which was NOT a panic or anything like that
> > my vinum volume sort of disappeared...
> > 
> > vinum itself is still happy, and a listing shows all my 
> > bits & pieces, up to the volume level as OK.
> > 
> > however, mount/fsck attempts come up with
> > errors like this:
> > 
> > # fsck /dev/vinum/rmassive
> > ** /dev/vinum/rmassive
> > BAD SUPER BLOCK: MAGIC NUMBER WRONG
> > /dev/vinum/rmassive: NOT LABELED AS A BSD FILE SYSTEM (unused)
> > 
> > _I_ havent touched anything, so it seems like something really
> > bad has happened. 
> > 
> > Can anyone suggest a way/hack to recover the damn disk? Its
> > a desperete situation :-(), so even desperate suggestion
> > will be appreciated. (i.e., is it possible to hack a 'label'
> > or an 'id' or something back into the disk. 
> > 
> > when a dd from the raw device, i do see something that looks 
> > like the root directory of the disk, so its not
> > as if everything was lost
> > 
> > 
> > -uname- (If it makes any difference)
> > 
> > FreeBSD loki 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Tue Jun  1 18:59:38 GMT 1999
> > root@loki:/usr/src/sys/compile/LOKI  i386
> > 
> > 
> > TIA
> > 
> > Kiril
> > 
> > 
> > 
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-stable" in the body of the message
> 
> 
> 



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