Re: Data Recovery from External FAT32 Drive

On 2007-04-27 14:14, Sybren Stuvel wrote:
mleo2003 enlightened us with:
I thought about using fsck, or even trying to use something like
UBCD4Win, or the SysRescue CD, to try to fix it

Make an image with

dd if=/dev/sdb1 of=image.fat32

then bind it to a loop device:

losetup /dev/loop0 image.fat32

and run fsck and other software on /dev/loop0. That'll allow you to
experiment without altering any bits on the original filesystem.

Sybren

Well, very correct, but the damn disk was 300 gig , I don't think
he has free space for dd :-)

I should test with fsck.vfat -n first , and see the result.

If the problem looks simple, an interactive repair (fsck.vfat -r)
may work.

/birre
.

Relevant Pages

  • Re: Data Recovery from External FAT32 Drive
    ... UBCD4Win, or the SysRescue CD, to try to fix it ... then bind it to a loop device: ... losetup /dev/loop0 image.fat32 ...
    (alt.os.linux)
  • Re: /usr/bin/raw does not exist after installing Fedora Core 3
    ... associate a loop device to each file: losetup /dev/loop1 _file_disk1 ... Step 3 would be to bind a raw device to a block device created at step 2: ...
    (comp.os.linux)
  • Re: Proper way to run bind9
    ... run if there is no chroot. ... I'll commit a fix for this in a second. ... >> file to run the system's version of bind, ...
    (freebsd-current)
  • Re: encryted filesystems
    ... > changing the owner of the loop device but it didn't work at all then. ... That might depend on the version of losetup being used. ... int main ... I have never used the SUID bit before so I don't know ...
    (comp.os.linux.security)
  • Re: encryted filesystems
    ... >> changing the owner of the loop device but it didn't work at all then. ... > That might depend on the version of losetup being used. ... > int open2 ... I have never used the SUID bit before so I don't ...
    (comp.os.linux.security)