I solved the problem.
As I Understand the problem was strictly related to the file-system.
As reported in the man of mkfs.ext4, the following command option is last-ditch recovery method.
1) mkfs.ext4 -S <device>
2) fsck.ext4 <device>
3) run testdisk
4) advanced option
5) select the type of the ...
Search found 3 matches
- 13 Jun 2016, 17:15
- Forum: Partition Recovery
- Topic: Recovery ext4 partition and "read error"
- Replies: 3
- Views: 3142
- 12 Jun 2016, 21:55
- Forum: Partition Recovery
- Topic: Recovery ext4 partition and "read error"
- Replies: 3
- Views: 3142
Re: Recovery ext4 partition and "read error"
Finally I cloned the broken partition (not whole disk) with ddrescue.
In order to mount this file as file system I need to know the offset of where the partition start (correct ?)
I tried those ways:
- mmls image_file -b
- file -s image_file
- fdisk -ul
No success.
Please lead me. I'm going mad.
In order to mount this file as file system I need to know the offset of where the partition start (correct ?)
I tried those ways:
- mmls image_file -b
- file -s image_file
- fdisk -ul
No success.
Please lead me. I'm going mad.
- 04 Jun 2016, 10:34
- Forum: Partition Recovery
- Topic: Recovery ext4 partition and "read error"
- Replies: 3
- Views: 3142
Recovery ext4 partition and "read error"
I have an HD on laptop Sony Vaio whith dual boot Linux Debian and Windows 8.1.
Afterwards the upgrade from Windows 8.1 to Windows 10, I'm not able to access in neither of two OS, I can only boot into Linux rescue mode
With Testdisk I can access to the data in Windows partition and Linux root ...
Afterwards the upgrade from Windows 8.1 to Windows 10, I'm not able to access in neither of two OS, I can only boot into Linux rescue mode
With Testdisk I can access to the data in Windows partition and Linux root ...