Date: Mon, 16 Apr 2018 19:22:55 +0200 From: Polytropon <freebsd@edvax.de> To: Ernie Luzar <luzar722@gmail.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: ntfs HD with io errors Message-ID: <20180416192255.bb846fcb.freebsd@edvax.de> In-Reply-To: <5AD4CE4A.5020408@gmail.com> References: <5AD4AE2A.80400@gmail.com> <20180416163812.ed284db3.freebsd@edvax.de> <5AD4CE4A.5020408@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Apr 2018 12:24:42 -0400, Ernie Luzar wrote: > Since the mbr was deleted looks like win10 got a malicious virus that > made the external usb HD un-mountable and screwed with the last file I > had open. Nothing physically wrong with the HD. Your further comments suggest something different (unless I'm misunderstanding something, of course). > All ready used dd_rescues and recovered 50% of user data which had no > i/o errors. dd_rescue could not fix any of the i/o errors. But dd_rescue does not operate on files, it processes the input device as blocks. Block I/O errors often indicate a hardware defect. However, it _could_ also be a problem with your SATA->USB configuration. Do you have a chance to try a differnt adapter? Or can you attach the disk to an SATA connector natively? > Read the man on dd and found no mention of skipping "free space" IE; > unused space in the allocated partition. > > Only 600gb of data on the 3tb HD. > > Looking for method to copy this data to 1tb HD bypassing i/o errors. The problem is: The I/O errors are probably _within_ the data you want to copy, and the data itself maybe is not contiguous (i. e., fragmented), so having a bigger disk at hand is _never_ wrong. You cannot "read around the holes" and expect to get a mountable NTFS volume from it... :-( -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180416192255.bb846fcb.freebsd>