Date: Tue, 25 Aug 2009 19:45:08 +0200 From: Polytropon <freebsd@edvax.de> To: Jerry McAllister <jerrymc@msu.edu> Cc: Kelly Martin <kellymartin@gmail.com>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: hard disk failure - now what? Message-ID: <20090825194508.a6c3983e.freebsd@edvax.de> In-Reply-To: <20090825150438.GA10392@gizmo.acns.msu.edu> References: <1338880b0908241129p75b6845cg26d21804e118364@mail.gmail.com> <20090824222611.025c4e56.freebsd@edvax.de> <20090825150438.GA10392@gizmo.acns.msu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 25 Aug 2009 11:04:38 -0400, Jerry McAllister <jerrymc@msu.edu> wrote: > dd will barf on bad bits too. > You can tinker to make it skip over the bad block, but it > won't read it. As it has been suggested, there are interesting tools in the ports collection. I'll post my "famous list" again. Among them, note ddrescue and dd_rescue. But base system tools such as the fetch program can help. 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 Those programs are not ordered in any way. -- 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?20090825194508.a6c3983e.freebsd>