Diskpart performed an unintended cleanup on the incorrect drive.
Diskpart performed an unintended cleanup on the incorrect drive.
I mistakenly cleaned the incorrect disk with DiskPart. It was included in a raid setup, so I need guidance on recovering my data. I considered watching the YouTube tutorial you linked but worried about it affecting the drive instead of the entire system. Since my main drive is part of a raid, I didn’t assign it a letter to the cleaned partition. I’m seeking advice on possible steps to restore my drive and retrieve my files. I also thought about using Linux USB or backing up via Windows 2nd boot, but I just want to wait and avoid any changes to my existing setup.
It’s nearly unavoidable during a raid based on the version used—whether it’s Raid 1 or Raid 0. Which one are you playing?
raid 0 also clarify what you meant by version. Regarding another point, I recall restoring my raid and files before. I think I messed up the drives possibly during an upgrade. Could there be something special about how I cleaned them that affects recovery chances?
You can create a snapshot of each drive using commands like dd. This will serve as your backup. Then restore the drives back to their original state, assigning them new letters if needed. After that, run recovery software on the system. I’m not sure what’s currently effective; I usually use Recuva because it works without feeling awkward. However, its performance isn’t great, especially with RAID 0. If your data has value, consider contacting a professional before proceeding. Some services offer remote recovery options, which can be reasonable in such cases.
but it isnt a damaged disk, it is two working disks. the files are not deleted, but would be exceptionally difficult to recover still. working through this logically, the file header should be at least on one or the other disk, but the file will just abruptly stop at the end of the sector and begin probably part way through a sector on the other disk if I am thinking it correctly. since raid0 I assume does not put a header and footer for each and every file that is written across disks like this (otherwise no one would say its impossible) it will be extremely difficult of a puzzle to reassemble each file. but you dont have to recover the files on their own, you have to recover the filesystem and the gpt table, which that part I am not sure of. I would like to assume that it is stored on one disk only in a raid0 but probably not idk. which is why if its any value, you are gonna have to talk with some company who knows what they are doing and can try to recover that.