Destroyed RAID while cloning
Hello.
I used TI 2015 to clone old 2 Tb WD Green to new 3 Tb Toshiba P300. After rebooting I found out that it cloned all right, but my Adaptec 1430SA RAID 10 was totally destroyed. It was neither source, nor destination, also not a system drive. It had no relation to cloning at all. Now it has no partitions and only some scraps of MFT. I used some recovery software, but all recovered files are just garbage. I also tried raid reconstruction software, but they all just couldn't recognize raid structure at all.
What TI did to my raid? Is there any way to recover files?


- Anmelden, um Kommentare verfassen zu können

Thanks for the link, but I didn't see anything there that could relate to my situation.
What information you might need to provide help?
BTW, 6 years ago I got similar problem - I cloned a disk with TI WD Edition and after reboot I also got my raid-10 destroyed. Difference is it was connected to TR-824 and was a bootable system drive. At that time I thought that was the root of the problem (system drive). But now this obviously couldn't be an excuse.
- Anmelden, um Kommentare verfassen zu können

Let's start again here please, just so that we fully understand exactly what your cloning scenario is, what exactly you were doing and how you were doing it?
Reading your initial post again, it seems that the 2 drives involved in the clone action are not part of any RAID set, if I read what you wrote correctly?
What exact version & build of ATI 2015 are you using here? Is this the full Acronis product, or is it an OEM version like the WD one you mentioned?
As you have ATI 2015, have you been using this to make backups of your OS drive(s) and are those backups stored on another backup drive (not one of the drives involved in the clone?
What type of computer is involved here, what version of Windows OS, how are the drives connected?
How was the clone being performed? Was this from within Windows or were you using the Acronis bootable Rescue Media (on CD/DVD or USB stick)?
- Anmelden, um Kommentare verfassen zu können

Yes, 2 cloning drives were not part of the raid, they were connected to mb controller. Raid consisted of 4 WD RE3 disks.
Build is 6526, not oem.
I used ATI to make daily backups of system ssd, backups were stored on raid drive.
It's an ordinary self-assembled PC, Windows 7 x64. 4 drives connected to the raid, the others 4 connected to mb controller (as single drives, no raid were ever configured on mb)
Clone was started within windows.
- Anmelden, um Kommentare verfassen zu können

Thanks for the clarification. Build 6526 is one behind the final build for ATI 2015 #6613 but impossible to say if that has any relevance in this situation.
Are any of your daily system backups still available for recovery, given you say that some were stored on a RAID drive?
Unfortunately, the most likely key contributor to this problem is with starting the clone from within Windows, assuming that this then forced a restart into the default Linux OS standalone environment, and this then didn't handle your RAID setup correctly?
Not sure where to take this matter further here. ATI 2015 is long out of support so Acronis will not be making any changes to resolve any issues found. This is especially true now that they have just released ATI 2019, so will soon be phasing out support even for the 2018 version.
- Anmelden, um Kommentare verfassen zu können

Well, only the most sensitive information had backups. And there're still lots of stuff I'd like to recover.
I don't really want ATI 2015 to be fixed (what's the point now anyway?). All I want - to get some clues on what it actually did, that could help in recovering.
- Anmelden, um Kommentare verfassen zu können

I can only suggest considering using the Acronis Pay Per Incident support to see if they can help you with any possible recovery (with the hope that they may drop or reduce any costs given this arose out of the use of their software?).
- Anmelden, um Kommentare verfassen zu können