In almost all the cases I had dealt with where the user reported that TestDisk found that the Volume Boot sector its backup as well as MFT and MFT mirror is OK , running checkdisk was successful in restoring the data. You have also read rik33or's thread (File System Corruption) External SSD, NTFS, RAW
Beyond that what more can I say? Best of luck is all that I can say
Last edited by jumanji; 01 Feb 2023 at 22:50.
Here (windows 7 - Change RAW partition to NTFS or recover files from RAW - Super User) could be a potential fix.
I'm now looking for a bit-bit full clone software to clone the corrupted SSD to another EVO 870 1TB. Redo Rescue has a bug that doesn't show identical SSDs. Any suggestions on software to use/install to bootable USB?
You are going way off the track bringing in recovery from different scenarios.. The Super User scene is that the user resized his C: partition and it became RAW and unbootable. Your case is not so.
It is a simple file system corruption that could be repaired running Checkdisk. chkdsk.exe F: /f /v /x. You are asking for guarantee.Can you guarantee that I will be alive tomorrow?
If you are not keen on it fearing that it may go awry, yes,, do a sector by sector clone and then run chkdsk.exe F: /f /v /x on the clone. ( Check MFT status by running TestDisk [Advanced] - Filesystem Utils as you have done before and confirm that MFT and MFT mirror is OK before running checkdisk after all that you have done and are doing out of jumanji's syllabus
The you tube video you referred was also a half-baked one where in the first part he advised running checkdisk. Yes, many went by that and repaired the file system. Luckily it so happened that their MFT was not corrupt. But atleast one user reported that by running checkdisk he lost all data.
"@vibhanshubiswas8729
2 years ago
First method is not recommended, it rewrites the index in the tables which results in the loss of the crucial information of the files and folder structure. I just lost a hell lot of information while doing this. No doubt it reinstated the partition but I lost a lot of files and data. I should have booted with linux and should have recovered the data from there. Trying my luck with MiniPartition now. which I doubt now because the index entries have been deleted by Chkdsk operation. Will update you all with my progress."
Why did this happen? Because the file index in MFT was corrupt and checkdisk deleted all the "orphaned files" "that did n't have a proper index in MFT
If you keep trying various recovery procedures not relevant to your problem, you are likely to damage your files making recovery impossible thereafter.
Last edited by jumanji; 02 Feb 2023 at 09:55.
Hello.
Just joined to answer your thread (discovered on ddrescue's mailing list).
Your best chance is first to backup/clone the drive with ddrescue.
This will warrant you to be able to restore the copy on another drive (would it be a SSD or a classical hard disk).
And ddrescue will show you while rescuing if there are bad sectors, so you'll know if your SSD is in a good state.
After the copy, you can do what you want, as you are able to restore from the copy.
Maybe your issue came from the robocopy which can have hardly stressed the SSD; perhaps should you monitor its temperature ...
Thank you for spending the time to create and account and comment.
I've ran robocopy from same SSD to same computer many, many times before in instances where it's transferring a *lot* more data and it hasn't occurred then. Although, who knows it could be the case.
ddrescue sure is a headache for someone who has never used it before, any suggestions for my case?
Concerning ddrescue and its syntax, you can rely on the post made by Adrien Cordonnier on ddrescue's mailing list.
I regularly use it (under Linux
"ddrescue /dev/sdX <fullpath_to_other_disk>/diskimage.img <fullpath_to_other_disk>/disk.map", X being the letter associated to your source disk.
For example, if your disk is /dev/sdc and the path to receive the image is "/media/user/my_disk" :
ddrescue /dev/sdc /media/user/my_disk/disk_c_image.img /media/user/my_disk/disk_c.map
It's important to use a mapfile to record the good and bad zones for later usage or in case of interruption.
As said by Adrien on the mailing list, be sure to store the image on a disk having enough available room (if your SSD is a 256 Go, be sure to have at least more than 256 Go free on it).
Should you have to restore the image on the disk, the syntax would be :
ddrescue -f /media/user/my_disk/disk_c_image.img /dev/sdc /media/user/my_disk/restore_c.map
- The "-f" flag is needed to write to a disk or partition
- The restore_c.map file will contain the status of the restoration (good zones and bad zones)
If you are not familiar with Linux, it can be a headache, but it's really efficient
@sklerder,
As does JumanjiFan, I appreciate your effort to register and chip in here to help him.
In my perception ddrescue is best suited for data recovery from a failing HDD riddled with bad sectors. In 2014. I even wrote an exploratory thread titled Best method/tool for cloning a failing HDD for Data Recovery? wherein ddrescue was discussed.
Best method/tool for cloning a failing HDD for Data Recovery? Solved - Windows 7 Forums. Many members contributed to that thread and many members even took a cue from it and used ddrescue to recover data even on 4% health remaining failing HDD.
Since then ddrescue has gone through many iterations including the change in its algorithm but still I presume it will be the best to recover data from failing HDDs. In that thread I had advised Windows users not to go in for mapfiles ( since windows users do not know to use correct Linux syntax, neither do I know
When there are many proven Windows cloning software, recommending ddrescue for a Windows user for just cloning/imaging would be farfetched.
It will be far more easier for the OP to use the trial version of Macrium Reflect to clone his SSD rather than going the Linux way ( a huge learning curve) to clone/image.
I agree it's not easy to switch from Windows to Linux ...
To ease things with ddrescue, there's a GUI usable in Windows for ddrescue, called DDRescue-GUI, which can be downloaded from this url :
DDRescue-GUI Downloads - www.hamishmb.com
It uses the Cygwin environment and a port of ddrescue under Cygwin, which can be launched in Windows.
My proposition to use ddrescue was due to the fact that JumanjiFan asked support on the ddrescue mailing list, but it is not the only way.
Macrium Reflect is effectively a good tool to make an image of the failing SSD, though I find it a little confusing in its GUI ...
But in my opinion, the most important point for JumanjiFan is that before making any other work on the failing SSD, he would be advised to backup or make an image of this SSD.
It's like a snapshot on a VM, it can be used to revert back to a known state of the drive, would it be bad or not ...
And if ddrescue is an excellent tool to image a failing disk, it is at least as excellent to image a good disk ;-)
I have done the following after weeks of researching.
Latest Progress:
- Contacted everyone on the support contacts. Surprising to hear that Aomei replied with that a sector-by-sector backup via AMOEI Backupper would not work, wouldn't you have thought that's the reason they created that software.
- Purchased DMDE Professional. Created a .bin image of corrupted SSD to another SSD (after running h2testw_1.4 on the target).
- Then, I used DMDE to clone that image on to another SSD (to create an identical copy of the corrupted SSD).
- On this, I attempted convert X: /fs:ntfs /v and chkdsk.exe X: /f /v /x of which you can see the results below. TLDR didn't run.
- Whilst running DMDE, it appears that no sectors are damaged.
- Also, I've narrowed the entire issue down to either my laptop's USB-C port or the wire used. Leaning more towards the port. However, just like the SSDs the laptop is in excellent condition, never dropped, stored in temperature controlled environments, running Windows 10 2016 LTSB. It is 7 years old and still runs fast enough, i7-7th Gen, NVIDIA etc etc.
Corrupted SSD Details:
- Samsung 2.5" EVO 870 1TB, Partition 1, X:\, 512,001 MB, NTFS, MBR, 4096 Cluster Size, 280 GB Written
- Cable Matters 2.5" Hard Drive Enclosure, Gen 2 USB C 3.1
- ULT-WIIQ USB C to USB C Cable, Type C 3.2 Gen2x2, PD 100W 5A, 4K 60Hz
Software List:
- TestDisk [File Scraper]
- PhotoRec [File Recovery]
- Recuva [File Recovery]
- MiniTool Partition Wizard [Unknown]
- MiniTool Power Data Recovery [Clone Disk]
- AOMEI Partition Assistant [Unknown]
- AOMEI Backupper [Clone Disk]
- Acronis True Image [Clone Disk]
- Macrium Reflect [Clone Disk]
- Disk Editor and Data Recovery Software (DMDE) [Clone Image]
- DDRescue [Clone Image]
- DDRescue-GUI [hamishmb.com/html/ddrescue-gui.php] [Clone Image]
- Redo Rescue [github.com/redorescue/redorescue/issues/116] [Clone Device]
- Clonezilla [Clone Device]
- H2Testw [Verify Memory Capacity]
- R-Studio Technician [Image Browser]
- FTK Imager [Image Browser]
- ZAR Data Recovery and Klennet Storage Software
Thread List:
- Samsung SSD 2.5 EVO 970 Raw Corruption from NTFS
- View topic - Data Recovery Expert Required - How to Fix SSD NTFS to RAW
- Samsung EVO 870 Raw Corruption NTFS Fix Partition ... - Samsung Community - 2497954
- Samsung EVO 870 How to Fix Raw Partition to NTFS [Assistance Needed] | TechPowerUp Forums
- Reddit - Dive into anything
Support Contacts:
- support@dmde.com
- bug-ddrescue@gnu.org
- support@minitool.com
- support@aomeitech.com
- support@dmde.com
- care@acronis.com
- joep@disktuna.com
DMDE Videos:
- How to create Image by DMDE - YouTube
- Creating a disk image (cloning) using DMDE - YouTube
DD Videos:
- Using Windows DD to Image a Disk - YouTube
Running convert X: /fs:ntfs /v and chkdsk.exe X: /f /v /x did not work.
Conformation of no corrupt/damaged sectors. Creating a .bin image clone of original 'corrupted' SSD to another new SSD.
MiniTool Partition Recovery Wizard finds a few 'overlapping' partitions, I select this one but nothing happens. Can not view files in explorer.
Rebuild MBR and Check File System (chkdsk) in MiniTool Partition Wizard does not work.
What Now?
I'm now looking for new solutions to return RAW back to NTFS, running it on the clone of original. If you have an idea, please let me know.
- - - Updated - - -
Klennet Recovery scanning 'NTFS' and 'SCAN'.
Klennet Recovery after verification.
Klennet Recovery NTFS results.
Klennet Recovery SCAN results.
- - - Updated on Feb 21st 2023 - - -
I've updated this forum. I have cloned the corrupt drive to an image using DMDE. Then, I have cloned this image to another SSD drive to simulate the 'broken corrupted drive'. Now, I'm asking for solutions on how to 'fix' this drive and return RAW to NTFS. I have attempted 'convert', 'chkdsk', and MiniTool Partition Wizard.
Current progress, I've cloned the first 2048 sectors of a working drive then will clone to first 2048 sectors of the 'cloned broken drive' using DMDE. First attempt didn't work, so I shall try again with identical device (as I have x2 Samsung EVO 870, one is the original corrupt, another can be used). Once I find a solution on how to fix the NTFS RAW corruption (return RAW back to NTFS), I can then compare the original drive to backup drive to ensure DMDE has successfully extracted a minimum of 100.00% of the data (can go over this i.e. deleted or 'lost' files).
If you're aware of a hex-edit solution, cloning MBR sectors solution or and other ideas to return NTFS to RAW. Please let me know.
Appreciate all the help and support.
Update Feb 25th 2023
- Attempted to simulate the original error causing NTFS to turn into RAW by re-creating the original scenario. Running robocopy to cloud storage. It worked sometimes but when I disconnect the drive and put back in, it would be auto-fixed (somehow) and usable again. Drive tested on is EVO 850 500 GB.
- Also attempted to simulate the error by cloning 'corrupted drive image' sectors.
- Then attempt to fix it (as now RAW) using cloned sectors from a drive both empty and filled (but in good NTFS condition) with same data (that's been recovered from DMDE).
- Above is empty clone and below is filled clone.
- I was indeed able to get a clone of the original corrupt drive working again with data missing. Comparing DMDE recovered to this, best results were 4287 files are missing and 74 directories (but not as bad as you think, as this was the last set of data written to the drive before corruption and stems from 2 main directories). Other results yielded 40,000+ missing files.
- Note that prior to testing an attempt at fixing the drive. I purchased and used DDRescue-GUI (runs a Linux 'emulator' through third-party software XLaunch) and R-Studio to extract data from the original corrupted drive. This way, I can verify that DMDE has successfully extracted 100% of the data by using 'robocopy /L' to compare. Some issues popped up saying 'modified' even when '/copy:dat /dcopy:dat /fft etc etc' were selected. But after extensive tests and comparisons it appears that DMDE did do a proper job (at least as well as I can see). The only way to 100% verify this is if the original drive started to magically work. Otherwise, I'm currently satisfied that DMDE has done the job.
- What I haven't tested yet is trying the original SSD in another enclosure, writing a cloned version of my other Samsung 870 EVO to the original SSD (likely same results as above tests) and a SMART report.
- - - Updated - - -
DDRescue-GUI Support:
- contact@hamishmb.com
Last edited by JumanjiFan; 25 Feb 2023 at 10:16.
Quote
