From owner-freebsd-questions@FreeBSD.ORG Mon Aug 24 20:51:42 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7AE41106568C for ; Mon, 24 Aug 2009 20:51:42 +0000 (UTC) (envelope-from tajudd@gmail.com) Received: from mail-yw0-f202.google.com (mail-yw0-f202.google.com [209.85.211.202]) by mx1.freebsd.org (Postfix) with ESMTP id 32DE38FC1F for ; Mon, 24 Aug 2009 20:51:41 +0000 (UTC) Received: by ywh40 with SMTP id 40so3818728ywh.14 for ; Mon, 24 Aug 2009 13:51:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LYHWp/iOJM0DiwV3udXmYtM749OakQ2m72hxw32CUFo=; b=mwWFk1QXuVoBT98FJqSnxuQB5rYGb9Mn7dySMASSu5Xa6y1Y7VCZBSawyCt/LQLA17 ULl8EqxFmCAI33cSM6N5Tf6vwSXeZhDbtlhdHwlMfp5IjN6KL+OMNSOnsf/fyQZb7YIr dsb2rWlszf2X0nYzNGRCXS7yjgOG6hj/mxXLY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=r8oI88YACRs966ytBxrPsBVS80s7Fnx3jA/zfjYQXKeetw427bgr84BtUPE8+7+uIG iz0MjUmWxw0phPjwU3BgRK9ZGGF/3bmfhMDMEZl1XZcyl/Sqbre9StwriE/YM5NYq2I9 0SiXCv8FLIur1KQc6d+pGvMK9bXR8Ar3tFQMY= MIME-Version: 1.0 Received: by 10.101.183.1 with SMTP id k1mr5336897anp.18.1251147101415; Mon, 24 Aug 2009 13:51:41 -0700 (PDT) In-Reply-To: <20090824224003.0b5ac2df.freebsd@edvax.de> References: <1338880b0908241129p75b6845cg26d21804e118364@mail.gmail.com> <20090824224003.0b5ac2df.freebsd@edvax.de> Date: Mon, 24 Aug 2009 14:51:41 -0600 Message-ID: From: Tim Judd To: Polytropon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Kelly Martin , FreeBSD Questions Subject: Re: hard disk failure - now what? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2009 20:51:42 -0000 On 8/24/09, Polytropon wrote: > On Mon, 24 Aug 2009 14:13:22 -0600, Tim Judd wrote: >> If I were you, get a copy of spinrite (from grc.com) and always keep >> it handy. It can be risky on a drive already failing. Here's what >> I'd do.... >> >> Buy spinrite, no matter what. > > Is it really such a good tool? From my own problems, I researched > that common recovery tools are "R-Studio" and "UFS Explorer". Both > do not natively run on BSD, but the first one offers a bootable > CD. Without buying, you can run the diagnostics mode fullwise. > For recovery, you need to buy the program. > > The "Spinrite" web page reads as follows: > > The industry's #1 hard drive data recovery > software is NOW COMPATIBLE with NTFS, > FAT, Linux, and ALL OTHER file systems! It's OS/FS independent. it works on the bits stored on the magnetic platters, NOT on a filesystem. TiVo, Linux, BSD and Mac OSX drives are treated the same. Bits on a magnetic platter. It's recovery stems from the randomization and movement of the head to the sector in question that allows it to salvage any bits it can (for example, other recovery will abandon 512bytes if 1 bit cannot be read. spinrite will recover 512bytes-1bit to a hard drive's spare sector once spinrite says "i'm done working with this sector".) It leads to a very successful rate. > > What? Linux and other file systems? > > Is this just marketing, in order to look good to the not very > educated ones? Or do they not know what they're talking about? > > In fact, I will keep an eye on this program. Maybe it can help me > get my data back (inode defect of $HOME entry). I'm reading their > web page some more right now. > Again, works on the bits. if it's a bit problem, it will do it's best to fix the problem, unless it's a hardware defect and cannot be relocated. If enough sectors are relocated, and the drive has run out of spare sectors, it's time to scrap the drive anyway. > >> slave the bad drive, read-only mount.. even if the FS is dirty, >> read-only.. no fsck. > > You can at least do one fsck run without any modification options, > like a "read only file system check". This of course can - like > any read operation on the disk - be risky if the disk is fast > degrading, simply by using it. which is why i recommend against making changes to the disk until a spinrite has completed. Personally, I setup a spinrite to be net-bootable (not officially supported). I can write a walkthrough to people who want to net-boot it. I won't provide spinrite, of course. I currently netboot: FreeBSD memtest86 spinrite with no changes to my setup any time I want to boot anything. > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... >