Date: Thu, 11 Mar 2004 10:25:47 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Daniel Lang <langd-freebsd-hackers@leo.org> Cc: hackers@freebsd.org Subject: Re: off topic - disk crash Message-ID: <20040311162545.GF27984@dan.emsphone.com> In-Reply-To: <20040311142128.GG20701@atrbg11.informatik.tu-muenchen.de> References: <200403101736.i2AHaqIF029948@www.kukulies.org> <20040311142128.GG20701@atrbg11.informatik.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Mar 11), Daniel Lang said: > C. Kukulies wrote on Wed, Mar 10, 2004 at 06:36:52PM +0100: > [..] > > The disk boots into FreeBSD but already at power on time the disk > > does seek retries or some recalibration noise. > > > > The question is what else can I do to recover the data. Put it in > > the icebox? Turn the computer upside down? > > Put it into another box running a working FreeBSD and enough > disk-space to contain all the contents of the damaged disk. > > Check if you can still read the disklabel (just do "disklabel ad1s1 > (or whatever your device is)). > > If you can read the disklabel, grab the contents of each partition > with dd, use the 'conv=noerror,sync' options to fill unreadable > sectors with zeros. Also, if it looks like a single bad area of the disk, try a dd starting a couple megs past the bad spot (with iseek+oseek) if the drive stops responding after it hits the bad area. I recovered data from a failed disk this way. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040311162545.GF27984>