From owner-freebsd-questions@freebsd.org Wed Apr 11 12:53:26 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 713CAF92619 for ; Wed, 11 Apr 2018 12:53:26 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (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 0C58F6EE31 for ; Wed, 11 Apr 2018 12:53:25 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x235.google.com with SMTP id t192-v6so17764547itc.1 for ; Wed, 11 Apr 2018 05:53:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=Zbhyaw+gouB0erACMMiiyjpoZVU+acSEiD1OvSw0/H4=; b=UnpEz85xBMxPqmotaJ1EPv4Z5NKYIm8TJnnv1O1MmtmMK5MJb4Xzr+g1+15qfB9KCC j5MU9he/kRw7z2w/YFtFC3Ws2vr0arrI40WU7ti5EVqYTfuYNC/2t5E2F+YIbqFMHk2w pfIUoP9MLuB3PZo1gznlSgefkUXBPLd6vFYKpq+yztvMZx7mFf7H0snOEmLwa2/kq8Fv IpTEXSS9JMRVNlT3L/ZGap6gDIksYcjnlQhZs5fk4Tk5aAXffzmovGEFk/0RsjDPpnL+ Tcf3X+9J5nLpzYlGOeITCnEC5FB/+oeZOCaj1L1iG+N4XLR/JTT+KGy9U9kXnGuSTqhZ bz2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=Zbhyaw+gouB0erACMMiiyjpoZVU+acSEiD1OvSw0/H4=; b=Y714m0+QKpnIMWaTSCtx4GvvczPv9ecy35th5SUr7fHqSR2mfSRR+5aK6sylsiNyT6 q7bVIWxCTxhKQY7Bmk5KM6O5AMNtNudrJ9cCSCOUIxG90g5PrzJSgd+DM0sE1BwDqKMn QcSPm70EQl6kI41RDp5M2uTnXoa8GVMmh9zS9phjlRKdRJL1EluJuaj06cVyg7vNahgN IKwVM+inlqyz6zC3seqHQg3X1oA3jRjQSoZ5Dlo8t39O/7SxKEV2nHuTWodqLH7+eqSs wZBjamQbCapgNG8aNCNBNAKjUMAdPQYTxEy4s8ya6qzZHFtAQoLXIg71SS7JrbOMpBY+ 3a9Q== X-Gm-Message-State: ALQs6tDEg51FSk7iB993ajhfEpGXlB+Rw3tVMcPHunPYCUvaL0f3Fo5Y u1zkkzpxv77Y+N08p7Sd0BUYmQ== X-Google-Smtp-Source: AIpwx4+NpqcwhlzlGwuXb3H0vxwaWIW6eI8IwyUImqL/F7k6U6c2fCbNgdmNXjien50uLz8n3zKLMQ== X-Received: by 2002:a24:7b86:: with SMTP id q128-v6mr3756649itc.145.1523451205348; Wed, 11 Apr 2018 05:53:25 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id 74-v6sm677159ith.17.2018.04.11.05.53.23 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 11 Apr 2018 05:53:24 -0700 (PDT) Message-ID: <5ACE0543.7030607@gmail.com> Date: Wed, 11 Apr 2018 08:53:23 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org" Subject: Re: Recover directory tree with files from win10 HD References: <5ACD536C.5010407@gmail.com> <20180411113740.2b245110.freebsd@edvax.de> In-Reply-To: <20180411113740.2b245110.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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:53:26 -0000 Polytropon wrote: > On Tue, 10 Apr 2018 20:14:36 -0400, Ernie Luzar wrote: >> My mothers win10 pc has external usb 3tb sata drive with 600gb of data >> that has hardware data problems. It will not mount on win10 pc. > > Do not try any further with "Windows", it could do more damage. > On "Windows 10", they use NTFS or FAT as file systems, and both > are known to do the "funniest things" when getting into some > inconsistent state ("silent" data corruption, data loss, no > access due to damaged hiberfile, etc.). > > > >> My >> mother has her whole digital life on the external drive. > > Just restore from backup! Sorry, couldn'r resist... ;-) > > > >> I can not find >> any win10 software to recover the data from a drive that will not mount. > > First of all, use tools that work with a copy of the damaged > disk (or partition). Create this 1:1 copy first in a read-only > manner, then work with the image. Do not try to repair the > data "on-disk", it will probably destroy more data and reduce > the chances of getting the "whole digital life" back. > > Seriously. I'm not making this up - I learned from my own > faults. Check the mailing list archives for the terrible > truth. :-) > > Do not use "Windows" any further without knowing _exactly_ > what the problem is. > > > >> I am thinking about using FreeBSD to recover the directory structure and >> the files contained in them. Asking anyone if they know of a port that >> will recover the data with their full file names in their directories? > > That depends on the actual damage. This is how you should > proceed: > > 1. Make a 1:1 copy of the disk or partition. Use that copy > in all further steps. (Two copies are handy, in case you > mess up one.) > > 2. Examine the data. What has happened? Can you use FUSE's > NTFS mount program to mount it read-only? Can you use > tools from the ntfs-tools package to repair things like > the MFT. Or is it a FAT drive? Try mount_msdos instead, > maybe even fsck_msdosfs. It could be sufficient to copy > all the data (cp -R). > > 3. No luck getting the partition to mount? Assume the data > is still there. Make yourself familiar with professional > forensic tools. Start with the easy ones. If they get > back what you expect to recover, well done. If not, use > the more complex ones. > > On this mailing list, I have published my "famous list of > data recovery tools" from time to time. Note that in order > to make use of that list, you'll have to learn (!) about > lower-level file system design, because you _must_ understand > what you're doing. > > Here is this list. Note that I've added a few comments that > might help in your specific situation (damaged FAT or NTFS > drive): > > System: > dd <- for making 1:1 copy > fsck_ffs > clri > fsdb > fetch -rR > recoverdisk > > Ports: > ddrescue <- if 1:1 copy is hard > dd_rescue <- same > ffs2recov > magicrescue <- get data back (no structure) > testdisk > The Sleuth Kit: > fls > dls > ils > autopsy > scan_ffs > recoverjpeg > foremost > photorec > fatback <- FAT > ntfs-tools <- NTFS (ntfsfix, ntfsinfo, ntfsmount) > > 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! > Thank you for your post. Lets talk about making a copy to work with. Question is about unused space. Disk is 3TB with 600GB used. How do I reduce the working copy size to the data only size of 600GB? Using the dd command I don't see any way to tell it to ignore coping empty space. Do I need another 3TB disk to hold the working copy? Do I dd the bad HD to another HD of same size making a complete image copy resulting in 2 ntfs hard drives? Or should I have the dd command create a single flat file of the bad disk on the target disk?