From owner-freebsd-fs Sun Jan 10 09:11:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12518 for freebsd-fs-outgoing; Sun, 10 Jan 1999 09:11:57 -0800 (PST) (envelope-from owner-freebsd-fs@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12509 for ; Sun, 10 Jan 1999 09:11:55 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA27906 for ; Sun, 10 Jan 1999 18:11:19 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA39194 for fs@freebsd.org; Sun, 10 Jan 1999 18:11:18 +0100 (MET) Date: Sun, 10 Jan 1999 18:11:18 +0100 From: Eivind Eklund To: fs@FreeBSD.ORG Subject: Finding a lost FS Message-ID: <19990110181118.F25747@bitbox.follo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org An error during some build experiments made disklabel run against the wrong disk, overwriting just the label before quitting. Have anybody got any good starters for how to recover the information on where the FS on that disk is located? I'm presently just running fsck -n -b against the disk, looking for alternate superblocks with good checksums. This has also uncovered at least one bug in fsck (it gives a bus error when scanning the bogus 'file system' described by one of those superblocks), so it is probably an exercise I should do more regularly... Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message