From owner-freebsd-questions@freebsd.org Wed Apr 11 12:54:16 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 ECF94F926BA for ; Wed, 11 Apr 2018 12:54:15 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: from mail-wr0-x234.google.com (mail-wr0-x234.google.com [IPv6:2a00:1450:400c:c0c::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68D926F555 for ; Wed, 11 Apr 2018 12:54:15 +0000 (UTC) (envelope-from g8kbvdave@googlemail.com) Received: by mail-wr0-x234.google.com with SMTP id y7so1663200wrh.10 for ; Wed, 11 Apr 2018 05:54:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=oWso7btleDgJlYAgja5owscEgeY/nGjM2Pwub24dntU=; b=CqRqsc7tyvUgeE69jBPG70w5hWSQrWWetDbFUJLECfkzlPv2z103lCT5L8ClG11U28 hk6HV1OKqp5ROI7F5S1jKrP85ZdyfO5/CSfeCJRqw84+HI7vKA8FiS7n4mhatXQ1ZTsk X7v0rY4CFDq6h7IqPdqHrkdoeX2wo9A6uR3OHW7UpqibpULPPpspOVVKjKCVNsOUAPhf AyLqqI2vA/gXVR+z/KqndWlJz4OyuRDNb+1FEDxzgCGeEgKrY6pASwI9aX+1cZNSEc/7 ZQxTYkP9tNrbWPjksTkQAgCU0B7myYYkZ1pOIV3OU5omYi3VIjJL1F5aLkAsCF5haXxW Xe0w== X-Gm-Message-State: ALQs6tBFhpfBLBX4dHTJbAYHk+/RAXbW4voggXg4Wrv+CbEktdJGj168 Gec/Isqmsh3D4PeG9sD0jJLLJo6E X-Google-Smtp-Source: AIpwx49ZeCKIlEg9SKnWcr/nH+mLRzuASvFmSgPO4/DrJW5MvK8X7ZPRvLPi+cViBoFMyDf2iePBbg== X-Received: by 10.223.166.179 with SMTP id t48mr3347825wrc.161.1523451253560; Wed, 11 Apr 2018 05:54:13 -0700 (PDT) Received: from [192.168.2.55] ([217.41.35.220]) by smtp.gmail.com with ESMTPSA id l34sm1185605wre.14.2018.04.11.05.54.12 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 11 Apr 2018 05:54:12 -0700 (PDT) Subject: Re: Recover directory tree with files from win10 HD To: freebsd-questions@freebsd.org References: From: Dave B Message-ID: <2e3003c1-047e-7609-162b-f65a50c7a124@googlemail.com> Date: Wed, 11 Apr 2018 13:54:12 +0100 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Content-Language: en-GB 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: Wed, 11 Apr 2018 12:54:16 -0000 On 11/04/18 13:00, freebsd-questions-request@freebsd.org wrote: > Keep in mind: It will take time. There is no "one size fits > all" GUI solution where you just click and icon and then have > all your files (and the directory structure) back. IN worst > case, what you're searching for has already been overwritten > by "Windows" attempting to "repair" it. > > Your alternative: Take $500-3000 and ship the disk to a > recovery business. If a "whole digital life" is worth that > much money, you can give them a change. Note that there is > absolutely no guarantee that they will succeed. > > Good luck! What happened to the drive to cause it to fail?   Power spike, got dropped while running, or "user finger trouble" from within the OS? Assuming it's "just" a corrupted media issue, often called "bit rot", causing read errors so the OS gives up... I've also had times where trying to make a bit for bit backup copy of a suspect drive fails due to read errors.  In such cases... https://grc.com/spinrite  Is likely to be able to help.  So long as the PC BIOS (or whatever low level software that runs before Win10) can "See the drive" and identify it correctly, it is likely to be able to do the job.    It runs from a bootable CD or USB drive, so no pre-existing OS is needed. If you have to resort to paid for tools, at $89 it is MUCH less than the above figures...   Plus, you get to keep it for future needs.  (They will do money back too on a case by case basis, if it can't do the job where the drive is not physically damaged so it can't be seen by the software...) It's often the first tool the pro's use anyway, before needing to get the big guns, tool-kits and specialist HD Foo knowledge, clean rooms and so on... It is OS agnostic, just working on individual sectors, having no knowledge of any file-system format, so works on just about any spinning magnetic media.    In extreme cases, it will recover what it can, often enough when a sector is not full, but damaged in the "empty" area. If however, the drive itself has mechanical or electrical problems, failed spindle motor driver, bearings, or head positioner servo, or read/write electronic problems, then all bets are off. No affiliation, other than as a happy owner/user for some years myself, so can vouch for it's abilities on Windows drives, Linux & FreeBSD systems, and the drive from my Humax PVR!  (It can also refresh/recover floppy disks.) If it can be recovered, it will be, but it can take some time (I forget the record, but with a UPS powered system, Months have been mentioned in the past before it completed, successfully...) Laptops and some external cased drives often need extra cooling while it's running, due to the workload imposed on the drive. Regards to All. Dave B. PS:  I actually test new drives with spinrite.  When (not if!)  Faults are found, just mentioning spinrite results in instant money back, or a free replacement, no other questions asked.   I was one time asked to send a screen photo showing what it found.   Got a free replacement and carriage costs refunded too! -- Created on and sent from a Unix like PC running and using free and open source software. :