Now I ask/beg for advice because I don't know how to proceed, I have little bullets left. There is very important data on the drive: code, projects, personal information...
I think that the corrupted drive is physically ok, (at least SMART stats seem ok).
I created an image of the drive using ddrescue (forgot to create the log) and worked on it. No errors in the process. I didn't specify an extension of the image and I don't know what is the default format for ddrescue. I guess it must be ".dd".
The drive partition format is MBR, and the only partition it has -default partition of the product- seems to be ok.
I ran TestDisk first on Windows and now on Ubuntu and it detects Intel/PC partition system, and when entering on the Analyse option shows the partition info:
QuickSearch->P and I think that it shows the files following the data of a corrupted FAT:
These kind of strange names are the same (or similar) that I see when I plug in the device in Windows. Testdisk highlights some of the files in red.
This is what happens when I try to enter in one of the directories shown on the picture:
Thus I came to the conclusion that the FAT of the main partition has been corrupted and the system is not able to properly swim throw the file system. It shows random directories and it is not able to enter to the files because the pointers are random.
Now I ran the Advanced options, and boot sector and backup bootsector are Ok. It shows this message:
And here is where I am lost. I don't know what to do here. I have used the RebuildBS option just to see what happened though if the boot sectors are ok it doesn't make sense. I pressed the Automatic option and it came to the result that Extrapolated boot sector and current boot sector are different.
Code: Select all
Partition Start End Size in sectors 1 * FAT32 LBA 0 1 1 121596 254 63 1953455742 Boot sector OK Backup boot sector OK First sectors (Boot code and partition information) are not identical. Second sectors (cluster information) are not identical. A valid FAT Boot sector must be present in order to access any data; even if the partition is not bootable.
Am I wrong in some conclusion?
What should be my next step?