I found myself in a little pickle with data being lost, However I was able to retrieve, but i didn't proceed with anymore since I didn't want to overwrite without clonning my ssd. I was using DMDE to recover those files, but I didn't find out about the cloning the drive until someone mentioned on the post. Then I realized, I should have taken look at the sticky points nailed to the sidebar.
I would like to follow the guide that you provided on datarecovery subreddit. Before, I proceed with the step with https://www.data-medics.com/forum/h...e-with-bad-sectors-using-ddrescue-t133.htmlto I really want to find out if I need to go through this step even if I don't have any failure or bad sectors. For recovery tool, I planning to use R-studio.
I was wondering if someone can suggest me what to do for my scenario where I have SSD drive that is perfectly working, though problem started within windows level.
I would like to follow the guide that you provided on datarecovery subreddit. Before, I proceed with the step with https://www.data-medics.com/forum/h...e-with-bad-sectors-using-ddrescue-t133.htmlto I really want to find out if I need to go through this step even if I don't have any failure or bad sectors. For recovery tool, I planning to use R-studio.
One of comment by Jared, it really stuck on my head. I would like to know if I got this right. From my understanding, does that mean when using ddrescue, it will overwrite and create new image. I don't want this to happen if thats the caseJared":xh6qwcxw said:When you clone a drive using ddrescue it's a block level copy, not file level. So anything you have on there will get nuked by the new image.
I was wondering if someone can suggest me what to do for my scenario where I have SSD drive that is perfectly working, though problem started within windows level.