From owner-freebsd-questions@FreeBSD.ORG Tue Jan 6 10:45:02 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 BD60B16A4CE for ; Tue, 6 Jan 2004 10:45:02 -0800 (PST) Received: from mx.tele-kom.ru (mx.tele-kom.ru [213.80.148.6]) by mx1.FreeBSD.org (Postfix) with SMTP id D651243D1D for ; Tue, 6 Jan 2004 10:44:59 -0800 (PST) (envelope-from doublef@tele-kom.ru) Received: (qmail 93900 invoked by uid 555); 6 Jan 2004 21:44:57 +0300 Received: from hal.localdomain (213.80.149.213) by t-k.ru with TeleMail/2 id 1073414696-93884 for scott@sremick.net; Tue, Jan 6 21:44:56 2004 +0300 (MSK) Date: Tue, 6 Jan 2004 21:44:42 +0300 From: Sergey 'DoubleF' Zaharchenko To: scott@sremick.net Message-Id: <20040106214442.11343be2.doublef@tele-kom.ru> In-Reply-To: <20040106174840.31457.qmail@web41105.mail.yahoo.com> References: <20040106203649.6eac1b6b.doublef@tele-kom.ru> <20040106174840.31457.qmail@web41105.mail.yahoo.com> X-Mailer: Sylpheed version 0.9.6claws (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=_Tue__6_Jan_2004_21_44_42_+0300_3ganNB/++ppFG0xM" 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: Tue, 06 Jan 2004 18:45:02 -0000 --Signature=_Tue__6_Jan_2004_21_44_42_+0300_3ganNB/++ppFG0xM Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: 7bit On Tue, 6 Jan 2004 09:48:40 -0800 (PST) "Scott I. Remick" probably wrote: > > --- Sergey 'DoubleF' Zaharchenko wrote: > > > I can't find a zero-bad floppy in this place! It's all the holidays! > > That's what AOL disks (vs. discs) used to be good for. :) > > > With `c', they're all offset by 63(why?). But still, you can mount the > > partitions on the ad4s1, so the disklabel should be ok... > > Yeah. Starts to suggest what we were thinking was a evidence related to the > problem is really unrelated and "normal" behavior (is disklabel/bsdlabel > only meant to be run on slices and not bsd-partitions?). Are we looking in > the wrong place? After trying out 5.2-RC2, it seems like the offsets reported with the `c' slice are from the beginning of the disk, not from the beginning of the slice. That accounts for the +63 difference. I guess it's documented somewhere, but as I don't use 5.x I haven't read its docs. > What about that potentially good superblock we found a > while ago? (the skip 16 one that contained "/data" in it) Should we be > saving that somewhere while we can? (how?) I think you already have a copy (the data at offset 32 seems to be it). If you want, do a # dd if=/dev/ad6s1 skip=16 count=16 of=/some/file Please tell me everything what you tried to use to mount/fsck the drive (and the results, of course). > Anyone out there know 5.x file-system dirtiness like the back of their hand? > C'mon, you know you wanna join the fun. :) Try booting from a 4.x floppy and doing it all over again... The FS is UFS1, isn't it? -- DoubleF Why does New Jersey have more toxic waste dumps and California have more lawyers? New Jersey had first choice. --Signature=_Tue__6_Jan_2004_21_44_42_+0300_3ganNB/++ppFG0xM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/+wIlwo7hT/9lVdwRAmj3AJ9D1ASxleoREHaWzOZ5GeVbFb3njgCfWnn/ hU18ffxf2eUqBDpH3eN7NZo= =DbDO -----END PGP SIGNATURE----- --Signature=_Tue__6_Jan_2004_21_44_42_+0300_3ganNB/++ppFG0xM--