From owner-freebsd-questions@freebsd.org Mon Apr 2 04:11:38 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18091F7091B for ; Mon, 2 Apr 2018 04:11:38 +0000 (UTC) (envelope-from jmvandette@securenet.net) Received: from ms.securenet.net (ms.securenet.net [205.236.147.20]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B45146C147 for ; Mon, 2 Apr 2018 04:11:37 +0000 (UTC) (envelope-from jmvandette@securenet.net) Received: from ms.securenet.net (localhost [127.0.0.1]) by ms.securenet.net (Postfix) with ESMTP id 61B8911E22; Mon, 2 Apr 2018 00:11:31 -0400 (EDT) X-Virus-Scanned: by f-prot anti-virus, and clamav anti-virus at SecureNet Inc. Received: from ms.securenet.net ([127.0.0.1]) by ms.securenet.net (ms.securenet.net [127.0.0.1]) (amavisd-new, port 10001) with ESMTP id oFzey2W_QMOt; Mon, 2 Apr 2018 00:11:29 -0400 (EDT) Received: from office.securenet.net (office.securenet.net [205.236.147.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ms.securenet.net (Postfix) with ESMTPS id D156411E1F; Mon, 2 Apr 2018 00:11:29 -0400 (EDT) Received: from office.securenet.net (172.16.0.194) by office.securenet.net (172.16.0.194) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1034.26; Mon, 2 Apr 2018 00:11:28 -0400 Received: from office.securenet.net ([fe80::fc2a:207d:850e:3424]) by office.securenet.net ([fe80::fc2a:207d:850e:3424%9]) with mapi id 15.01.1034.033; Mon, 2 Apr 2018 00:11:28 -0400 From: "Jean M. Vandette" To: Erich Dollansky CC: "freebsd-questions@freebsd.org" Subject: Re: gpart recovery FreeBSD 7.4 Thread-Topic: gpart recovery FreeBSD 7.4 Thread-Index: AdPH67s6+2Xno425Q4Gw3Y3ODMy5+wAZ1aOAAAgLB7AAClZQAAAIULXwABRMGwAAAW9JQABQpD8A///CqCw= Date: Mon, 2 Apr 2018 04:11:28 +0000 Message-ID: References: <6b89534c97b14e51b67581e34efac71c@securenet.net> <20180330221523.0b5f8fdd.freebsd.ed.lists@sumeritec.com> <20180331070140.00a1b6fa.freebsd.ed.lists@sumeritec.com> <20180331204056.619965d1.freebsd.ed.lists@sumeritec.com> <3856200b233947ca939e1c5ffa152661@securenet.net>, <20180402115102.08679f26.freebsd.ed.lists@sumeritec.com> In-Reply-To: <20180402115102.08679f26.freebsd.ed.lists@sumeritec.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-avg-scannedformalware-engineversion: 16.0.8039 4793/15532 435436 x-avg-scannedformalware-signature: 5948518D47896C3E8BBA4F03453DB28DA475572966E2494E25D85A99F7B5D2B4 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2018 04:11:38 -0000 Erich When you say dd the first sector of the disk are you referring to mfid0 itself or the / partition mfid0p3 ? I have all the dd of / Let me know Jean M Vandette Sent from my iPhone > On Apr 1, 2018, at 11:52 PM, Erich Dollansky wrote: > > Hi, > > On Sat, 31 Mar 2018 18:43:06 +0000 > "Jean M. Vandette" wrote: > >> I used the recoverdisk >> root@central:/ # recoverdisk /dev/gpt/root /mnt2/root.img > > I never used this program. > >> I did newfs on the boot then it mounted seems it does not recognize > > That was dangerous. When I have had the problem I really went down to > read the partition information from the disk into a file and tried to > understand it. > > This method helped recently when a disk has had developed so many bad > sectors that it shrank its size during a boot. So, I did the same with > its GPT information, mounted it, made a backup of the last hours of > work and returned it to the manufacturer. > >> I don't have other mount points ie disks to make copy. > > This is a real problem at this stage. > >> the recoverydisk with state 0 says it encountered no errors so it is >> seeing the data (I presume) just it is a binary file it seems. Now >> is the data usable is another question. Using more or less I see a >> lot of binary gibberish so far. > > Yes, the data is all binary. The key to any disk is its first sector. >> >> I don't know if there is a way to write the superblock information >> without losing all the data if you or anyone knows I would appreciate >> the procedure. Did it once before or should say my mentor did it back >> on 3.1 and then was able to fsck and mount the data. > > This is all not a problem but it come much, much later. There is > something wrong with your partitioning tables. I would try to find this > out. > > Get a hex editor of your choice. dd the first sector of the disk, open > it in the editor. I used Wikipedia to provide me with the structure > information of the disk. This all depends how it was partitioned and > later formatted. MBR, GPT ... > > I know that this is hard work and will take time. > > Erich ------------------------------- Checked by AVG. Version: 16.0.8039 / Virus Database: 4793/15532 - Release D= ate: Sun Apr 01 09:04:00 2018. The message does not contain any threats. -------------------------------