Aller au contenu principal

Restore from bootable media destroyed the data on two drives.

Thread needs solution

I just used the Acronis bootable media (created with Acronis TI 2016) to restore an image to my drive and on the first attempt it incorrectly attempted to restore a 193GB image to a 100GB drive. I didn't pick the 100GB drive as the target and, in fact, I couldn't because the option was greyed out due to it being too small. Despite the fact that I chose the correct drive (I'm sure because I always read the confirmation before doing an operation) it tried to restore to the wrong drive and failed halfway through with a "disk full" error. I figured maybe it was a fluke (the 100GB drive was connected via USB) so I tried the operation again. I didn't think my other drives were in danger as they were connected via SATA. The operation succeeded and I booted into Windows and opened Disk Management to see if there were any partitions on the 100GB drive. Unfortunately, it somehow deleted the partition from a 500GB drive as well. Luckily the data is replaceable (Steam games and .iso/utilities) but a pain nonetheless. The desktop application is crap as well. It costs $50 yet it's basically nagware. There are a bunch of utilities in the program that are locked behind a paywall. Not to mention the fact that it wouldn't even run on my laptop until I forced it to use the high performance graphics mode in CCC. It's a known issue that was supposed to have been fixed on the newest build. I never had an issue with Acronis TI 2013 and decided to upgrade to 2016, in part, because of the fact that the bootable media supports WiFi. Except it doesn't work. It recognizes my network adapter but never locates any WiFi networks. Every other Linux based utility I've used works just fine with my wireless NIC. I guess I'll go back to Clonezilla as I don't even trust TI 2013 now.

-Andy

Fichier attaché Taille
img_20160420_094237.jpg 6.84 Mo
img_20160420_095337.jpg 2.77 Mo
0 Users found this helpful

Andrew - I've never experienced this - I use ATIH 2016 and Snap Deploy products to deploy dozen of systems each week.  What version of the bootable recovery media are you using - click the help drop down when booted up.

Please definitely reach out to tech support as this is a recovery issue and someting that is always covered.  If it is a bug, they need to address it so it doesn't keep happening to you or anyone else.

https://forum.acronis.com/forum/18623

5.    Recovery issue
- Related to recovery issues with the full version of the product
- Free of charge
- 24x7
- Not limited (Assistance with the recovery issue can be requested any time, even if you’re out of 30 days free support and don’t have PPI)
- Provided with e-mail and chat
Response time:
-  3 business days via e-mail
 - immediate via chat

 

 

 

I created the recovery media on 9APR2016 with ATI 2016 build 6027. I booted it in legacy mode, my BIOS is UEFI with CSM enabled, Win 10 is booted in legacy mode, and all local drives are MBR. The drive I was restoring the image from is GPT. I can't boot the recovery media as I no longer have the .ISO. I've uninstalled ATI 2016 and have received a refund. The .ISO was on the 100GB USB HDD in question. It's a hard drive enclosure with a CD-ROM emulator, it's what I booted from and it defaults to dual mode (HDD and CD) which is why it was available in the target list. I don't know if that has anything to do with it as I used it to restore several backups on my laptop previously (the issue happened on my desktop). I talked to a representitive via live chat but I wasn't really very receptive to help. The data is replaceable and my main reason for contacting support was to request a refund. I did notate the circumstances in the support ticket with some detail. I'll attach a dxdiag to this post if somebody from Acronis cares to look at it. I have no logs so I don't know how much more help I can be. If you can think of anything let me know. I'd hate for somebody to lose something important.

-Andy

Fichier attaché Taille
350678-128116.txt 67.48 Ko

Bummer. I've been restoring with v6027 numerous times with both internal and USB drives attached without issue.  I really don't know what the cause would be at this point.  You're the first I've heard of this happening to.  It shouldnt matter what type of drive your images are stored on (GPT or MBR).  Likewise, it shouldn't matter how your OS is installed or how the bootable media is launched.  The only time the bootable media needs to be launched a spefic way is to match how the OS is installed (launch in UEFI mode if OS is UEFI/GPT and launch in Legacy mode if OS is installed in Legacy/MBR).  Sounds like you did that though.

Maybe the emulator is the problem, I have no idea - I've never used one. I just let Acronis burn the bootable media directly to a USB flash drive and that has always worked.

Wish I had more info to work with and sorry to see you go.  Don't wish data loss on anyone and can understand your situation at this point. Do you use any BCD tweakers or dual boot.  I've also seen external drives show up as "raw" all of a sudden and have some success fixing that:

http://html5.litten.com/updated-how-to-fix-external-disk-drive-suddenly…

I suppose it could apply to internals too, but don't think the liklihood of 2 wiped drives on your system - right after using Acronis is coincidence.

Could be worth a shot trying the link above to see if it brings back the data in tact if you haven't reinitialized or reformatted them yet.

Thank you for your concern and your swift response. Luckily the data on the drives has pretty much been replaced already. The 500GB SSD only contained Steam games which I've already redownloaded for the most part. The 100GB external/CD emulator only contained ISOs and some utilities. I had most of the ISOs backed up and can download the rest along with the utilities.

Yes, I've been booting the ISO in legacy mode, my Win 10 installation uses legacy boot on a MBR disk and I don't duel boot on my desktop. I tried a UEFI boot of the TI boot media once and it spit out some errors (too fast to read) and lacked the Universal Restore options from the selection screen (makes sense considering how it works). So I rebooted and used legacy from that point on.

It could be the iodd drive as I know not a lot of people use those. It can be finicky booting Linux sometimes (WinPE and Windows based utilities always seem to boot fine). Although, as far as I can tell, the TI bootCD runs entirely from memory once loaded so it seems like it shouldn't matter. I have a multicard reader that connects to just one USB header but shows up as four sperate drives so it's definitely a hub. Maybe that's common with these types of card readers? Perhaps my combination of usb devices caused it to enumerate the drives incorrectly? I have no idea if that could even make sense. It's so wierd that it restored to a drive that wasn't large enough for the image and that it was aware of the fact because the choice was greyed out. Also strange is that I performed two restore operationions and it wiped three drives; the 100GB drive it tried to restore to, the 240GB intended target it successfully restored to, and the 500GB drive it seemed to only delete the partition of.

I'm thinking the data on the 500GB could have been salvaged, but it was so much easier to just redownload the few games that were on there. The 100GB drive was probably toasted as it was written to until full. I didn't bother to dig very deep. I just checked them out in Windows disk management snap in. They both seemed to have valid partition tables as they both showed up as MBR, the capacity was correct, and they only required that I create a new volume (no initialization required). Thank Jeebus nothing happened to my 1TB mechanical drive. I will be backing that up when I finish reorganizing. So I dunno, I suspect the card reader, the iodd, or a combination of the two. Totally spitballing though.

-Andy