From owner-freebsd-questions@FreeBSD.ORG Mon May 5 16:11:45 2003 Return-Path: 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 B7C0837B404 for ; Mon, 5 May 2003 16:11:45 -0700 (PDT) Received: from adsl-64-161-78-226.dsl.lsan03.pacbell.net (adsl-64-161-78-226.dsl.lsan03.pacbell.net [64.161.78.226]) by mx1.FreeBSD.org (Postfix) with SMTP id F1C6443FD7 for ; Mon, 5 May 2003 16:11:44 -0700 (PDT) (envelope-from oremanj@adsl-64-161-78-226.dsl.lsan03.pacbell.net) Received: (qmail 7901 invoked by uid 1001); 5 May 2003 23:12:11 -0000 Date: Mon, 5 May 2003 16:12:11 -0700 From: Joshua Oreman To: Paul English Message-ID: <20030505231211.GB7604@webserver.get-linux.org> References: <20030504005204.GK84427@wantadilla.lemis.com> <20030503183948.W10431-100000@dynamic.hydro.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030503183948.W10431-100000@dynamic.hydro.washington.edu> User-Agent: Mutt/1.4i cc: questions@freebsd.org Subject: Re: Incorrect super block on a disk X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 May 2003 23:11:46 -0000 On Mon, May 05, 2003 at 02:04:35PM -0700 or thereabouts, Paul English seemed to write: > > > > On Sun, 4 May 2003, Greg 'groggy' Lehey wrote: > > > > it tries for an alternate superblock, fails and then I try doing > > > fsck -b 32 (as recommended in the manpages) and I get the same error. > > > > > > Is there anything I'm doing wrong or something else to try? > > > > It seems pretty certain that whatever they sent back from the data > > recovery house is not a UFS file system. You should try to find out > > how they got the data there. I can't imagine them creating a new file > > system. Until you know that, there's not much point trying > > alternatives, though some of them exist. > > I will check with them - it looks like they don't have someone I can talk > to on Saturday. I believe though that they just did a bit-for-bit or > byte-for-byte copy. The partition table information is still there - the > output of disklabel shows what appears to me to be a valid disk label for > all of the partitions, this one included. file -s is your friend. Try: # file -s /dev/da0s1 where da0s1 is the partition on the recovered disk. It should tell you what type FS it is. This is an extremely useful feature that very few people actually know about. > > > > Can I somehow regenerate the super block? > > > > Regenerating super blocks is simple: that's what newfs(8) does. The > > trick is keeping your data. > > Aah... > > Fortunately they still have the source data, and I can also do a dd of the > partition to another drive before I go mucking with newfs. > > I don't suppose that newfs has a special option to just try to regenerate > superblocks and save the data? In my web searching for solutions, it looks > like Linux has a -S option for mke2fs that will attempt to rebuild > superblocks while saving the data. > > Are there any other alternate superblocks? Again it appears that Linux > saves them every 8K clusters, but the fsck manpage on freebsd only > mentions that block 32 is usually an alternate. > > Paul > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" HTH, -- Josh