GPT raid array swon as RAW
Posted: 28 Feb 2016, 02:54
Hello,
I'm currently trying to recover from what I believe is partitioning issue on my raid drive. Two WD 4TB drives running as raid1, visible under Win7 64b as MARVEL Raid VD. I had two NTFS partitions 1TB and 3TB. This is not my C drive.
Wednesday morning after boot I noticed that 1TB partition is gone - windows disk management saw it as RAW. I did a backup of 3TB partition that was fully available at that time. In the meantime it occurs that last two backups on my 1TB partition stored on a separate NAS are corrupted and unusable. So since Wednesday I'm trying to recover from that. So far no luck.
I tried TestDisk 7.1-WIP and 7.0. The EFI GPT is recognized after a disk selection. Also - Analyse can see basically correct (as far as I understand) partition structure - no overlaps, size in sectors is matching my 1TB / 3TB split. However - information about errors are displayed for every partition:
The advanced menu got no boot button, no matter which partition I highlight:
The Boot option is available on different drives - that is including one GPT 4TB WD....
The 'Quick search' after a few days of running found a massive number of partitions (log file is 380kB big), most of them are called [NO NAME], some [EFISECTOR], a few [Boot]. Which is a bit strange, as both drives were bought new from Amazon and used only for this RAID.
Anyway - I checked those partitions and none of them is displaying my files I'm looking for - some have some files, but that is not my stuff. None of the found partitions got names I gave them originally. And size vary - from a few MB to a couple of GB. Nothing close to 1TB....
At the moment I finally got additional bigger drive so I'm doing image of my beloved partition 1TB. I also managed to recover massive number of files with PhotoRec - unstructured as you can imagine.
In the meantime the 3TB partition after one reboot also switched to RAW.
So to be honest I actually ran out of ideas what I can do next to recover from this.... I will run Quick scan and then maybe Deep, but that will take maybe a week. Any hints will be much appreciated. Thank you.
I'm currently trying to recover from what I believe is partitioning issue on my raid drive. Two WD 4TB drives running as raid1, visible under Win7 64b as MARVEL Raid VD. I had two NTFS partitions 1TB and 3TB. This is not my C drive.
Wednesday morning after boot I noticed that 1TB partition is gone - windows disk management saw it as RAW. I did a backup of 3TB partition that was fully available at that time. In the meantime it occurs that last two backups on my 1TB partition stored on a separate NAS are corrupted and unusable. So since Wednesday I'm trying to recover from that. So far no luck.
I tried TestDisk 7.1-WIP and 7.0. The EFI GPT is recognized after a disk selection. Also - Analyse can see basically correct (as far as I understand) partition structure - no overlaps, size in sectors is matching my 1TB / 3TB split. However - information about errors are displayed for every partition:
The advanced menu got no boot button, no matter which partition I highlight:
The Boot option is available on different drives - that is including one GPT 4TB WD....
The 'Quick search' after a few days of running found a massive number of partitions (log file is 380kB big), most of them are called [NO NAME], some [EFISECTOR], a few [Boot]. Which is a bit strange, as both drives were bought new from Amazon and used only for this RAID.
Anyway - I checked those partitions and none of them is displaying my files I'm looking for - some have some files, but that is not my stuff. None of the found partitions got names I gave them originally. And size vary - from a few MB to a couple of GB. Nothing close to 1TB....
At the moment I finally got additional bigger drive so I'm doing image of my beloved partition 1TB. I also managed to recover massive number of files with PhotoRec - unstructured as you can imagine.
In the meantime the 3TB partition after one reboot also switched to RAW.
So to be honest I actually ran out of ideas what I can do next to recover from this.... I will run Quick scan and then maybe Deep, but that will take maybe a week. Any hints will be much appreciated. Thank you.