Date: Tue, 3 Apr 2018 04:14:01 +0000 From: "Jean M. Vandette" <jmvandette@securenet.net> To: Erich Dollansky <freebsd.ed.lists@sumeritec.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: RE: gpart recovery FreeBSD 7.4 Message-ID: <b6a6d431f75e4e44982b6335ce40ff8c@securenet.net> In-Reply-To: <20180402115102.08679f26.freebsd.ed.lists@sumeritec.com> References: <6b89534c97b14e51b67581e34efac71c@securenet.net> <20180330221523.0b5f8fdd.freebsd.ed.lists@sumeritec.com> <a1ad4c0f59e240e4a87d5feb0dcc9344@securenet.net> <20180331070140.00a1b6fa.freebsd.ed.lists@sumeritec.com> <aab034b9617b42dcb4cf74dc6811dec3@securenet.net> <20180331204056.619965d1.freebsd.ed.lists@sumeritec.com> <3856200b233947ca939e1c5ffa152661@securenet.net> <20180402115102.08679f26.freebsd.ed.lists@sumeritec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Erich Found an old post on partition repair https://forums.freebsd.org/threads/partition-repair.5869/ Got the scan_ffs an here are the results: root@central:~ # scan_ffs -l /dev/mfid0 X: 2097152 9786530 4.2BSD 2048 16384 0 # / X: 2097152 9787042 4.2BSD 2048 16384 0 # / X: 4194304 12232866 4.2BSD 2048 16384 0 # /tmp X: 41943040 17126306 4.2BSD 2048 16384 0 # /usr X: 42068388 17126818 4.2BSD 2048 13350 0 # /usr X: 62914560 66061474 4.2BSD 2048 16384 0 # /usr/local X: 83886080 139462050 4.2BSD 2048 16384 0 # /var X: 1258291200 237328290 4.2BSD 2048 16384 0 # /usr/local/system X: 21973958460 1705333922 4.2BSD 2048 16384 0 # /usr/local/storage X: 21973958460 1705334434 4.2BSD 2048 16384 0 # /usr/local/storage The gpart show is =3D> 40 27341619120 mfid0 GPT (13T) 40 128 1 freebsd-boot (64K) 168 8388602 2 freebsd-swap (4.0G) 8388770 2097152 3 freebsd-ufs (1.0G) 10485922 4194304 4 freebsd-ufs (2.0G) 14680226 41943040 5 freebsd-ufs (20G) 56623266 62914560 6 freebsd-ufs (30G) 119537826 83886080 7 freebsd-ufs (40G) 203423906 1258291200 8 freebsd-ufs (600G) 1461715106 25879904054 9 freebsd-ufs (12T) It seems to differ from the scan of the file system Your thoughts? Regards Jean M. Vandette SecureNet Information Services Net-Vu Television Distribution Divisions 159272 Canada Inc. 283-100 Alexis Nihon Blvd St Laurent, Quebec H4M 2N7 514-744-4242 800-469-7774 514-744-1552 Fax IMPORTANT: Les informations contenues au pr=E9sent courriel ainsi que dans tout docume= nt annex=E9 sont de nature privil=E9gi=E9e et confidentielle et ne peuvent = =EAtre utilis=E9es que par la ou les personnes ou entit=E9s dont le nom par= a=EEt ci-dessus. Si le lecteur du pr=E9sent message n'est pas le destinatai= re pr=E9vu ou n'a pas =E9t=E9 mis en copie, il est par les pr=E9sentes pri= =E9 de noter qu'il est strictement interdit de divulguer, de distribuer de = copier ou d'utiliser de quelconque fa=E7on ce message ou ses annexes. Si ce= ux-ci vous ont =E9t=E9 transmis par m=E9garde, veuillez les effacer et nous= en aviser imm=E9diatement. This E-mail along with its attachments, if any, contain privileged and conf= idential information intended only for the use of the individuals or entiti= es named above. Any dissemination, distribution, copying or use of the same= by anyone other than the intended recipients is strictly prohibited. If yo= u have received this communication in error, please delete both E-mail and = attachments and notify us immediately. -----Original Message----- From: Erich Dollansky [mailto:freebsd.ed.lists@sumeritec.com] Sent: Sunday, April 01, 2018 11:51 PM To: Jean M. Vandette <jmvandette@securenet.net> Cc: freebsd-questions@freebsd.org Subject: Re: gpart recovery FreeBSD 7.4 Hi, On Sat, 31 Mar 2018 18:43:06 +0000 "Jean M. Vandette" <jmvandette@securenet.net> 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 secto= rs that it shrank its size during a boot. So, I did the same with its GPT i= nformation, mounted it, made a backup of the last hours of work and returne= d 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 i= n 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/15535 - Release D= ate: Mon Apr 02 09:04:00 2018. The message does not contain any threats. -------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b6a6d431f75e4e44982b6335ce40ff8c>