cgsecurity.org

did a test with photorec and it does recover files but i stopped it after a minute....this is a huge drive and files with no names or folders would take me years to organize. i apologize for the many posts im just trying to give u as much info as possible. if i can recover the partitions and ...

ok im kind of lost..it seems like the file system should be recoverable...but fsck says it has errors...but im unsure whether to select yes to repair all the errors...there is a long list of questions from fsck and i hit no to them

should i repair the file system using fsck?

or should i try to ...

next I ran testdisk again to check if the superblock info is now different..it has changed some

this is what came back:

Linux 0 1 1 243201 80 62 3907029104 [UB1 2TB]
superblock 0, blocksize=4096 [UB1 2TB]
superblock 32768, blocksize=4096 [UB1 2TB]
superblock 98304, blocksize=4096 [UB1 2TB ...

next I ran fsck to check the disk:

fsck /dev/sdc1

and got this back saying the file system is now ext2:

fsck from util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
fsck.ext2: Permission denied while trying to open /dev/sdc1
You must have r/w access to the filesystem or be root

next i ran with sudo ...

i next ran the command using the actual drive path (testdisk had it as /dev/sdc )

Ubuntu lists the drive as /dev/sdc1

testdisk lists the drive as /dev/sdc

i ran this command:

sudo fsck.ext4 -p -b 32768 -B 4096 /dev/sdc1

this is what came back: :

UB1_2TB: Superblock has an invalid journal ...

next i rant his command:

sudo e2fsck -b 1605632 /dev/sdc

and got this reply:

e2fsck 1.42.13 (17-May-2015)
e2fsck: Bad magic number in super-block while trying to open /dev/sdc

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it ...

i ran this command in terminal:

sudo fsck.ext4 -p -b 32768 -B 4096 /dev/sdc

this is what i got back:

fsck.ext4: Bad magic number in super-block while trying to open /dev/sdc
/dev/sdc:
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid ...

as there are several blocksizes listed above im not sure what this means or how to use it.

To repair the filesystem using alternate superblock, run
fsck.ext4 -p -b superblock -B blocksize device

im trying to be careful

any suggestions?

some more info:

the drive is a 2tb toshiba drive that has only one ext4 2tb volume to recover

when i formatted the disk i did a quick format to ntfs (i made a mistake thinking this internal 2tb drive was my unplugged external 1tb drive that i needed to format)

when i used testdisk the first time ...

ok i ran superblock and got this?

Disk /dev/sdc - 2000 GB / 1863 GiB - CHS 243201 255 63

Partition Start End Size in sectors

Linux 0 1 1 243201 80 62 3907029104 [UB1 2TB]
superblock 0, blocksize=4096 [UB1 2TB]
superblock 32768, blocksize=4096 [UB1 2TB]
superblock 1605632, blocksize=4096 [UB1 ...