Page 1 of 1

big oops, can TestDisk fix this?

Posted: 13 Sep 2013, 13:24
by JaredT6694
I was messing around trying to format a usb drive with exFat under Ubuntu. I ran something like this:

sudo mkfs.exfat /dev/sdb

which had output like this:

mkexfatfs 1.0.1
Creating... done. Flushing... done.
File system created successfully.

While that all seems well and good, I realized moments later I ran that command not from my local shell window, but from a window I was ssh'd to a different PC.

I've run through the default analyse and testdisk does find the ext4 partitions.

Any guidance would be much appreciated,

Thanks,

-jt

Re: big oops, can TestDisk fix this?

Posted: 14 Sep 2013, 10:04
by cgrenier
If your ext4 partition is listed, choose to write the partition table. Next you may have to go in TestDisk, Advanced, Superblock to get a fsck.ext4 command able to repair the damaged filesystem.

Re: big oops, can TestDisk fix this?

Posted: 20 Sep 2013, 22:27
by JaredT6694
ok, maybe I spoke too soon, this is what I'm seeing

The following partitions can't be recovered:
Linux 121427 152 6 364628 233 5 3907029168 [Tsch2TB]
EXT4 Large file Sparse superblock Recover, 2000 GB / 1863 GiB

I've uploaded a log file, is there a different option I should be trying or is it a lost cause?

Re: big oops, can TestDisk fix this?

Posted: 05 Oct 2013, 10:37
by cgrenier
What I wrote is still the way to go. Run TestDisk, Analyse, QUick Search, if your ext4 partition isn't listed use Deeper Search, set your ext4 partition to P(rimary), write the new partition table...