Date: Thu, 19 Oct 2017 10:25:31 +0100 From: "Frank Leonhardt (m)" <frank2@fjl.co.uk> To: freebsd-questions@freebsd.org Subject: Re: How to recover data from dead hard drive. Message-ID: <AE761404-1C5A-4540-849B-4A4181BE55C4@fjl.co.uk> In-Reply-To: <20171014202115.GA92751@acer.zyxst.net> References: <59DBA387.4050108@gmail.com> <20171009191435.145c9dd2.freebsd@edvax.de> <72772933-C642-43DB-AFD6-6B5D40EEF39E@fjl.co.uk> <BN6PR2001MB1730D947FADA3A9DC9A370A480490@BN6PR2001MB1730.namprd20.prod.outlook.com> <59E21214.4020509@gmail.com> <20171014214926.2fed03aa.freebsd@edvax.de> <20171014202115.GA92751@acer.zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 14 October 2017 21:21:15 BST, tech-lists <tech-lists@zyxst.net> wrote: >Interesting thread. > >I have a similar problem, this time with a failing (now failed) disk >that had freebsd-11-stable installed with the root-on-ZFS option. I >manged to dd over ssh an image of the disk. However, I've not been able >yet to mount the image to get the data. I think it's ZFS in the image >that's causing the issue. I've tried to spin up the image in bhyve on >another system. It gets past the demon graphic, tries to boot but drops > >to the mountroot or mfsroot (can't remember exactly) prompt. No matter >what I enter there, it still won't boot. What it defaults to is what >it used successfully when it was on the (now failed) hardware. > >Can anyone tell me how to mount and recover the image? If you're lucky this is caused by bhyve. However, by this stage, if you're booting from a once-working boot drive then the ZFS stuff should have been brought in by the loader, allowing it to mount the FS and load the OS. Have you tried specifying a different device? (Its safe to guess). I'd probably mount the image using mdconfig on a ZFS enabled machine (type zpool to check it's been compiled with the right modules) and see if it can auto-mount. Easier than sorting out boot problems, especially if the boot partition has been clobbered. ZFS is surprisingly good at reassembling stuff from odd locations using GUID metadata. Only worry I have is that its part of a striped vdev, which will allow you to boot that far using code duplicated on each drive, but then no further. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AE761404-1C5A-4540-849B-4A4181BE55C4>