Re: [Dump-users] Can't read next inode ...

[Stelian P. <st...@po...>]

Le mercredi 20 août 2008 à 12:12 -0700, Perry Hutchison a écrit :

> I had already made a copy using dd with conv=noerror, and have
> encountered two problems (one definite, the other suspected):
> 
> - If I try to have dump read from the image file, it misinterprets
>   this as a request to dump the image file itself:

Yes, dump really expects a block device. So you should 'losetup' a loop
device on top of the disk file.

e2fsck works with a block device or a regular file (it just issues a
warning on startup iirc).

[...]

> - the dd manpage does not say what dd does about the unreadable
>   blocks.  Ideally it would have filled the corresponding parts
>   of the image file with zeros, but I suspect it skipped them
>   entirely (so everything beyond the first unreadable block is
>   probably at the wrong offset for either e2fsck or dump).

>From what I read, you should have been using:
	dd conv=noerror,sync

Even better, ddrescue seems to be more appropriate:
	http://www.gnu.org/software/ddrescue/ddrescue.html

-- 
Stelian Pop <st...@po...>