From owner-freebsd-questions@FreeBSD.ORG Wed Feb 4 02:24:15 2004 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 0F5C816A4CE for ; Wed, 4 Feb 2004 02:24:15 -0800 (PST) Received: from mx.tele-kom.ru (mx.tele-kom.ru [213.80.148.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 2691D43D3F for ; Wed, 4 Feb 2004 02:24:12 -0800 (PST) (envelope-from doublef@tele-kom.ru) Received: (qmail 82814 invoked by uid 555); 4 Feb 2004 13:24:10 +0300 Received: from hal.localdomain (213.80.149.161) by t-k.ru with TeleMail/2 id 1075890249-82750 for scott@sremick.net; Wed, Feb 4 13:24:09 2004 +0300 (MSK) Date: Wed, 4 Feb 2004 13:27:10 +0300 From: Sergey 'DoubleF' Zaharchenko To: scott@sremick.net Message-Id: <20040204132710.78956223@Hal.localdomain> In-Reply-To: <20040204070505.15051.qmail@web41110.mail.yahoo.com> References: <20040204082855.5111c74d@Hal.localdomain> <20040204070505.15051.qmail@web41110.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.8claws (GTK+ 1.2.10; i386-portbld-freebsd4.8) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha1"; boundary="Signature=_Wed__4_Feb_2004_13_27_10_+0300_L2t=k3WXsVopAw/o" cc: Jerry McAllister cc: FreeBSD Subject: Re: "Cannot find file system superblock" error - how to recover? 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: Wed, 04 Feb 2004 10:24:15 -0000 --Signature=_Wed__4_Feb_2004_13_27_10_+0300_L2t=k3WXsVopAw/o Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Tue, 3 Feb 2004 23:05:05 -0800 (PST) "Scott I. Remick" probably wrote: > --- Sergey 'DoubleF' Zaharchenko wrote: > > Sorry, you were recovering an 80G disk, and now you say the 80G has 4.9 > > on it. Did you erase anything? Is this a remote machine? > No, it was not the drive that had the OS on it. It was originally mounted as > /data on a system that had FreeBSD 5.1 installed on a separate drive. We > determined the 80GB was UFS1. You wanted to try troubleshooting using > FreeBSD 4.9, so I obtained a spare system which I installed FreeBSD > 4.9-RELEASE on. I then moved the 80GB from the 5.1 system (which is actually > 5.2 now) and installed it into the 4.9 system on the 2nd controller. So now > 4.9 is installed on a 20GB on /dev/ad0, and our problem 80GB is /dev/ad2. Thank you for the explanation. > > You can boot 4.9, right? Examine the output of disklabel ...s1 and > > ...s1c to make heart feel better. > bash-2.05b# disklabel /dev/ad2s1 [snip] > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 156344517 0 unused 0 0 # (Cyl. 0 - 9731*) > e: 156344517 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 9731*) > bash-2.05b# disklabel /dev/ad2s1c [snip] > 8 partitions: > # size offset fstype [fsize bsize bps/cpg] > c: 156344517 0 unused 0 0 # (Cyl. 0 - 9731*) > e: 156344517 0 4.2BSD 2048 16384 89 # (Cyl. 0 - 9731*) Good:) Well, as it's UFS1 as we've figured out, the next logical thing would be to try mounting /dev/ad2s1c r/o, and if that fails, try fscking it. -- DoubleF The faster we go, the rounder we get. -- The Grateful Dead --Signature=_Wed__4_Feb_2004_13_27_10_+0300_L2t=k3WXsVopAw/o Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQFAIMkJwo7hT/9lVdwRApCLAJ9zmre1FTqxoFLAcKgaETK1C0QSRQCeLxYu vGFiU7NJzP+a/1Fq5//Bc5Y= =D4tF -----END PGP SIGNATURE----- --Signature=_Wed__4_Feb_2004_13_27_10_+0300_L2t=k3WXsVopAw/o--