Date: Mon, 2 Apr 2018 11:51:02 +0800 From: Erich Dollansky <freebsd.ed.lists@sumeritec.com> To: "Jean M. Vandette" <jmvandette@securenet.net> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: gpart recovery FreeBSD 7.4 Message-ID: <20180402115102.08679f26.freebsd.ed.lists@sumeritec.com> In-Reply-To: <3856200b233947ca939e1c5ffa152661@securenet.net> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180402115102.08679f26.freebsd.ed.lists>