From owner-freebsd-questions@freebsd.org Thu Oct 19 09:25:48 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EFF6E35285 for ; Thu, 19 Oct 2017 09:25:48 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "bs1.fjl.org.uk", Issuer "bs1.fjl.org.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E6D7A300B for ; Thu, 19 Oct 2017 09:25:47 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [10.144.193.19] ([148.252.129.74]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id v9J9Pigr032593 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO) for ; Thu, 19 Oct 2017 10:25:45 +0100 (BST) (envelope-from frank2@fjl.co.uk) User-Agent: K-9 Mail for Android 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> <59E21214.4020509@gmail.com> <20171014214926.2fed03aa.freebsd@edvax.de> <20171014202115.GA92751@acer.zyxst.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: How to recover data from dead hard drive. From: "Frank Leonhardt (m)" Date: Thu, 19 Oct 2017 10:25:31 +0100 To: freebsd-questions@freebsd.org Message-ID: X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Oct 2017 09:25:48 -0000 On 14 October 2017 21:21:15 BST, tech-lists 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.