Date: Fri, 13 Oct 2017 12:03:11 +0100 From: "Frank Leonhardt (m)" <frank2@fjl.co.uk> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: How to recover data from dead hard drive. Message-ID: <72772933-C642-43DB-AFD6-6B5D40EEF39E@fjl.co.uk> In-Reply-To: <20171009191435.145c9dd2.freebsd@edvax.de> References: <59DBA387.4050108@gmail.com> <20171009191435.145c9dd2.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Good list that. ddrescue is, IME, the place to start. Or have I confused it with dd_rescue again :-) But what do you mean by dead? If its not spinning or not recognized by the system as existing, you'll get nowhere with software. I transplant the platters to a new IDENTICAL drive mechanism and work from that. You can by an identical drive from companies who stock samples them "just in case". Unsurprisingly, they're not cheap. And transferring platters is not easy. I also have some expensive licensed software for recovering incomplete file systems, and charge Windows users like a wounded rhinoceros when they need their data back. On 9 October 2017 18:14:35 BST, Polytropon <freebsd@edvax.de> wrote: >On Mon, 09 Oct 2017 12:27:51 -0400, Ernie Luzar wrote: >> A while back I remember reading a post giving the steps and software >to >> use to recover data from a dead H.D. > >Last time it appeared: > >Subject: Re: Recovering data from a broken HDD >Date: Mon, 18 Sep 2017 01:17:47 +0200 > > > >> Could that be reposted again. > >Sure. :-) > >System: > dd > fsck_ffs > clri > fsdb > fetch -rR <device> > recoverdisk > >Ports: > ddrescue > dd_rescue > ffs2recov > magicrescue > testdisk > The Sleuth Kit: > fls > dls > ils > autopsy > scan_ffs > recoverjpeg > foremost > photorec > fatback > >Proprietary (free test version for diagnostics): > > SysDev Laboratories LLC "UFS Explorer" > >Most tools require you to know what you're doing, so learning >how to use those tools appears to be mandatory. As I said, work >with (a copy of) the copy of the disk if possible, so in worst >case you can start from the beginning without feeling guilty >that you did something wrong. ;-) > > >-- >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" -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From owner-freebsd-questions@freebsd.org Fri Oct 13 11:52:51 2017 Return-Path: <owner-freebsd-questions@freebsd.org> 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 3CF8EE45BB5 for <freebsd-questions@mailman.ysv.freebsd.org>; Fri, 13 Oct 2017 11:52:51 +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 D85181AAB for <freebsd-questions@freebsd.org>; Fri, 13 Oct 2017 11:52:50 +0000 (UTC) (envelope-from frank2@fjl.co.uk) Received: from [10.154.179.141] ([85.255.236.93]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id v9DBqlg6023691 (version=TLSv1/SSLv3 cipher=DHE-DSS-AES256-SHA bits=256 verify=NO); Fri, 13 Oct 2017 12:52:48 +0100 (BST) (envelope-from frank2@fjl.co.uk) User-Agent: K-9 Mail for Android In-Reply-To: <7531e98e-6910-0853-b4e2-a3fe92bfb694@rail.eu.org> References: <59DA19E8.5000602@gmail.com> <7531e98e-6910-0853-b4e2-a3fe92bfb694@rail.eu.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Subject: Re: forcing new dynamic ip address From: "Frank Leonhardt (m)" <frank2@fjl.co.uk> Date: Fri, 13 Oct 2017 12:18:55 +0100 To: Erwan David <erwan@rail.eu.org>, freebsd-questions@freebsd.org Message-ID: <9E9FD41B-997F-4506-AAF7-C70F038BBF70@fjl.co.uk> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 13 Oct 2017 11:52:51 -0000 On 8 October 2017 13:37:30 BST, Erwan David <erwan@rail.eu.org> wrote: >Le 10/08/17 à 14:28, Ernie Luzar a écrit : >> Hello List; >> >> I have a "home service" account from my ISP. The ISP issues an >dynamic >> ip address which has not changed in 12 years. >> >> My host has 2 NICs, one which is not used. I know if I plug the >internet >> cable into the un-used NIC and make the appropriate config changes >and >> reboot I will get a different dynamic ip address. >> >> Is there a simpler way to expire the lease to force the ISP dhcp to >> refresh with a different dynamic ip address? >> >> The goal is to have a cron job that gets a different dynamic ip >address >> assigned to my host's front door every a week. >> >> Just another level of security to make it very hard for the script >> kiddies from finding any open ports I may have. >> >> Thanks for the help. >> > >DHCP protocol states that the server should try to give you the same IP >address. And dhcp servers keep track of the addresses they allocated in >the past, to give them back if possible. Hate to be a pendent, but it may not be a DHCP server giving you the IP address unless you're running Ethernet. In some parts of the world people do run PPPoE instead of ATM, so it might conceivability work this way. Most DSL use LCP to configure IP address IME. Once you go past the modem socket it doesn't look like Kansas any more. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?72772933-C642-43DB-AFD6-6B5D40EEF39E>