From owner-freebsd-questions@freebsd.org Mon Apr 16 14:45:05 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 9EE3EF88E2B for ; Mon, 16 Apr 2018 14:45:05 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (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 06D5476C9E for ; Mon, 16 Apr 2018 14:45:04 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-lf0-f52.google.com with SMTP id b23-v6so3543671lfg.4 for ; Mon, 16 Apr 2018 07:45:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=uFqnbvfeIVMVd9LLF1TjZiOnDk56e2kmxf1MpHR47Ww=; b=UBpiZR+WIkC8XGHNnQpDRfYk2Qy0MvpNFcmitcOjHboXXjeYf87jW9G8hcRdPf+9uE 50dhsAQKyqOyvJQUnaIjDZLY0wl6pv2s9fE8UKoLfgu8klxHESrz1aK2WQCaLHOn5djb q4tg/VF9suyd3n7gZNUXrFCxgKMdXhnmQIuJWgnJxkXkHBdXIQcXCs6wkbktam1+c3IR l4cv0urzTdGSpZSVaCAocYP1Y0k64JsMVKA+DjVcLqL5+L5y+9kOoArjVVD4H3GAp0lP qxpxcCeeHt8PZ1XdWYsMYmtCe5WKwJOeKAmjLCfCoj1dZa5PC1/URI0rdSgzgbJeiISG WABQ== X-Gm-Message-State: ALQs6tA8sgd3ZgAJjp7a/oSJ0iqB7Mwb8yW8/MJl09S+7n7yAHdUR9Wp 9/tVJfgbfOdPGEgFJJzCr8IdWcn2 X-Google-Smtp-Source: AIpwx4+/h1arMhkXjSWvIiLagCR9ws9Qx6rodzGDWWDIrBVF0d2oy6JlXwk4CV3Fv966qv1ovBoA6g== X-Received: by 2002:a19:7405:: with SMTP id v5-v6mr602229lfe.73.1523889902522; Mon, 16 Apr 2018 07:45:02 -0700 (PDT) Received: from mail-lf0-f45.google.com (mail-lf0-f45.google.com. [209.85.215.45]) by smtp.gmail.com with ESMTPSA id a189-v6sm2221993lfb.12.2018.04.16.07.45.02 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Apr 2018 07:45:02 -0700 (PDT) Received: by mail-lf0-f45.google.com with SMTP id q9-v6so22478699lfk.9 for ; Mon, 16 Apr 2018 07:45:02 -0700 (PDT) X-Received: by 10.46.44.9 with SMTP id s9mr10169618ljs.122.1523889902128; Mon, 16 Apr 2018 07:45:02 -0700 (PDT) MIME-Version: 1.0 References: <5AD4AE2A.80400@gmail.com> <20180416163812.ed284db3.freebsd@edvax.de> In-Reply-To: <20180416163812.ed284db3.freebsd@edvax.de> From: Ultima Date: Mon, 16 Apr 2018 14:44:51 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: ntfs HD with io errors To: Polytropon Cc: Ernie Luzar , FreeBSD Mailing List Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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: Mon, 16 Apr 2018 14:45:06 -0000 This is a 3 TB disk and spinrite can only scan the first 2 TB's. Usually that would be enough if the product can fix it, but it is worth noting. On Mon, Apr 16, 2018, 7:39 AM Polytropon wrote: > On Mon, 16 Apr 2018 10:07:38 -0400, Ernie Luzar wrote: > > Have a 3TB ntfs HD with i/o errors. > > > > ntfs-3g does read it, but a ls command of 2 different directories get > > error msg about i/o errors and nothing is listed. > > > > Is there a way to fsck this HD to fix it? > > This depends on the actual reason for the error message. > As it has been suggested, Spinrite can do a great job > to "re-activate" broken disks, at least for copying > their content once. Also check the tools in "ntfsprogs", > one might be able to repair the file system... but I/O > errors often indicate hardware failure. Have you tried > to get a smartctl report for the disk yet? > > > > > There is only 600GB of data on the 3TB HD. Looking for way to copy the > > data to a 1TB ufs HD. > > > > > What will dump command do with i/o errors? > > With dump, you can only process UFS file systems (as > input); NTFS does not support it. > > > > > Can dd command skip over unused space? > > I think it can. You can also try dd_rescue or ddrescue > which can handle I/O errors much better than stock dd, > for example by using a dynamically adjusted block size > for reading, or performing several attempts on a failed > block. > > > > > Any other ideas? > > Find out if you have a hardware error or a filesystem > inconsistency. > > Oh, and give Spinrite a try, it's really a great tool. > Why isn't it on my list?! ;-) > > In worst case, use magicrescue to get at least the data, > in case you might not be able to get the sorting information > (directory hierarchy and file systems lost). > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >