fsck on FAT32 filesystem?

Jerry jerry at seibercom.net
Sun Jul 15 20:23:37 UTC 2012

On Sun, 15 Jul 2012 21:48:23 +0200
Polytropon articulated:

> For example, make an 1:1 copy using dd (or ddrescue or dd_rescue)
> of the disk. Work with a copy of that copy. Do not alter the disk.
> Then use tools that do the job of recovery (see my list postings
> about that topic, they contain a good list of tools you can use
> on UNIX). The suggestion of SpinRite is also good, even though
> the program is expensive. I'm confident it's worth its money.
> But if you are willing to _learn_ (which means to read and to
> experiment), the free recovery tools available through the
> Ports Collection are really good.

If I might interject here, making a copy is obviously imperative;
however, it also exposes a severe problem. You are working under the
assumption that the copy is actually correct.In fact, it is simply what
is being read from the disk at the time of the copy. It may in fact be
totally in error. SpinRite will attempt to read a damage sector up to
2000 times and through different algorithms determine what is most
likely the correct data. Obviously it cannot do that if it is working
with a copy of the drive. It must have access to the original drive. I
have to admit that am partial to SpinRite since it saved my ass twice
in the past 10 years when no other software could do the job 100%.
Hence, if you cannot afford to lose your data, back it up.

Jerry ♔

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.

More information about the freebsd-questions mailing list