On Sat, Jul 17, 2004 at 04:05:16PM +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
this will cause dd to continue after errors, and the blocks on the new
disk which could not be read from the old will be filled with null
bytes, rather then random data. using a 512 byte blocksize will help
reduce the number of blocks which will be filled with nulls.
> Jul 15 21:18:58 d kernel: end_request: I/O error, dev 22:41 (hdh),
> sector 243818336
> Can I do something to make it better? The disk is only one year old but
> maybe the temperature has been a little bit to high in the computer box.
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.
Description: PGP signature