On Fri, Jul 30, 2004 at 04:51:19PM +0200, Jan Banan wrote:
>
> >>I suppose the best stradegy is to get a new disk of the same size and
> >>then try to copy the whole damaged disk with "dd" to the new disk and
> >>then try to startup the raid again and after that run xfs_repair. What
> >>arguments to "dd" would fit best in this case? I think I've read that
> >>"dd" will normally abort when it can't read from a damaged disk and the
> >>disk is quite big, 250 GB (Maxtor).
> >>
> >>
> >
> >dd if=/dev/broken of=/dev/new bs=512 conv=sync,noerror
> >
> I have now got a new harddisk with the exact same size (250 GB). I have
> now started doing that "dd" command line you suggested. I can not find
> any kind of "verbose"-flag to "dd" so I do not know how long time this
> will take. Any idea? (Pentium II 450 MHz with 512 MB memory and running
> Red Hat Linux 9)
it will take quite awhile since bs=512 is the least efficient, but it
will also result in the least lost data.
> >ive heard you can sometimes make a disk temporarily become functional
> >again by shutting it down for a few days. i think ive even heard that
> >putting it in a freezer can help. in any event the most you could
> >hope for is just enough functional time to recover the data.
> >
> >
> I have tried both shutting it down for a few days and to put it in a
> freezer, but none of those two things did help :(
often not, unfortunatly.
> Best regards and thanks for all hints,
> Jan
--
Ethan Benson
http://www.alaska.net/~erbenson/
pgpknZJriaui3.pgp
Description: PGP signature
|