HDD recovery
by iscsi from LinuxQuestions.org on (#5D75G)
Hi,
Unfortunately I f@cked up my linux hdd-s under windows, so now I would like to recover. These 2 HDD are the same 2 TB hdd disk, and had only one (probably ext4) partition just storing photos. Actually one of those has just stored some not important things, so I started my recovery "research" on that.
I've try to use testdisk, when I select the None media type and analyze it shows this (quick search result):
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
Partition Start End Size in sectors
>P ext4 0 0 1 243201 80 63 3907029168 [Photo2]
Structure: Ok.
when I press continue here, I've got this error message:
Write isn't available because the partition table type "None" has been selected.
When I choose advanced-> superblock option : I've got this:
Partition Start End Size in sectors
ext4 0 0 1 243201 80 63 3907029168 [Photo2]
superblock 0, blocksize=4096 [Photo2]
superblock 32768, blocksize=4096 [Photo2]
superblock 98304, blocksize=4096 [Photo2]
superblock 163840, blocksize=4096 [Photo2]
superblock 229376, blocksize=4096 [Photo2]
superblock 294912, blocksize=4096 [Photo2]
superblock 819200, blocksize=4096 [Photo2]
superblock 884736, blocksize=4096 [Photo2]
superblock 1605632, blocksize=4096 [Photo2]
superblock 2654208, blocksize=4096 [Photo2]
To repair the filesystem using alternate superblock, run
fsck.ext4 -p -b superblock -B blocksize device
after that I've tried to run: fsck.ext4 -p -b 32768 -B 4096 /dev/sdb command, the result :
Photo2: Superblock needs_recovery flag is clear, but journal has data.
Photo2: Recovery flag not set in backup superblock, so running journal anyway.
Photo2: recovering journal
Photo2: Padding at end of inode bitmap is not set. FIXED.
Photo2: 11/122101760 files (0.0% non-contiguous), 7947223/488378646 blocks
but unfortunately the recover data just contains a lost+found (empty) directory.
If I choose other than none media type its just showing some weird probably windows related thing. Could you help me what should I try?
What kind of type should I choose in the testdisk? Is the above fsck command correct, or I just made the things more worse?
Thanks
Unfortunately I f@cked up my linux hdd-s under windows, so now I would like to recover. These 2 HDD are the same 2 TB hdd disk, and had only one (probably ext4) partition just storing photos. Actually one of those has just stored some not important things, so I started my recovery "research" on that.
I've try to use testdisk, when I select the None media type and analyze it shows this (quick search result):
Disk /dev/sdb - 2000 GB / 1863 GiB - CHS 243201 255 63
Partition Start End Size in sectors
>P ext4 0 0 1 243201 80 63 3907029168 [Photo2]
Structure: Ok.
when I press continue here, I've got this error message:
Write isn't available because the partition table type "None" has been selected.
When I choose advanced-> superblock option : I've got this:
Partition Start End Size in sectors
ext4 0 0 1 243201 80 63 3907029168 [Photo2]
superblock 0, blocksize=4096 [Photo2]
superblock 32768, blocksize=4096 [Photo2]
superblock 98304, blocksize=4096 [Photo2]
superblock 163840, blocksize=4096 [Photo2]
superblock 229376, blocksize=4096 [Photo2]
superblock 294912, blocksize=4096 [Photo2]
superblock 819200, blocksize=4096 [Photo2]
superblock 884736, blocksize=4096 [Photo2]
superblock 1605632, blocksize=4096 [Photo2]
superblock 2654208, blocksize=4096 [Photo2]
To repair the filesystem using alternate superblock, run
fsck.ext4 -p -b superblock -B blocksize device
after that I've tried to run: fsck.ext4 -p -b 32768 -B 4096 /dev/sdb command, the result :
Photo2: Superblock needs_recovery flag is clear, but journal has data.
Photo2: Recovery flag not set in backup superblock, so running journal anyway.
Photo2: recovering journal
Photo2: Padding at end of inode bitmap is not set. FIXED.
Photo2: 11/122101760 files (0.0% non-contiguous), 7947223/488378646 blocks
but unfortunately the recover data just contains a lost+found (empty) directory.
If I choose other than none media type its just showing some weird probably windows related thing. Could you help me what should I try?
What kind of type should I choose in the testdisk? Is the above fsck command correct, or I just made the things more worse?
Thanks