Win10PE - Can backup RAID but not recover it

TI 2011 through TI 2014 are not supported on Windows 10. Only TI 2015 and TI 2016 are supported. See this link for a backwards compatibility list https://kb.acronis.com/content/1689. You would need TI 2015 to recover your .tib file from TI 2011. Since this is a rcovery issue you should be entitled to free support for this. Contact Acronis support via your MY Account page on www.acronis.com by clicking on Get Support. On the next page in the right hand column click Contact Support.

thomasjk wrote:

TI 2011 through TI 2014 are not supported on Windows 10. Only TI 2015 and TI 2016 are supported. See this link for a backwards compatibility list https://kb.acronis.com/content/1689. You would need TI 2015 to recover your .tib file from TI 2011. Since this is a rcovery issue you should be entitled to free support for this. Contact Acronis support via your MY Account page on www.acronis.com by clicking on Get Support. On the next page in the right hand column click Contact Support.

Version 2011 works fine on non RAID drive within a Win10PE envirement. No problem to backup and restore. But this is a RAID and only the backup works but not restoring it.

I have tried different WinPE and different Acronis version, Acronis own bootable ISO, Acronis True Image 2016 from a new drive with a fresh WIN10 installed. IT DOES NOT WORK....

Running a "verifying image" with no erros on the files. I can browse the image file ans see all files. I can restore files from it. But I cannot restore the whole disc or partition from it. The program just blinks up or a Restore failed message pops up....

I have spent atleast 15 hours on this today.

Peter

If you must recover the image from TI 2011 your only option may be to contact support as I suggested in my earlier post.

I had hope to get that support here on this forum as I have seen Acronis people around here.

Wow, probably the worst support I have ever encountered... Asking the same question 3 times and getting brainless answers back not answering my question. So I return here in hope that someone here can help me.

The first support person (yes, i went true a few) suggested that v.2016 is not compatible with v.2011 and suggested me to try v.2015. Fine. The problem is that the ISO-file that i got does not work with Rufus Boot USB tool, which works well with other Acronis ISO-files, and I went back to the support. But now a new guy, who asked me to talk to another guy.... I asked them how to solve it and just got the answer that I should google on it for a third party tool.... 3 times... Support telling you to google on it, yea Crazy indeed.

Anyway, I want to try a full trail version of v.2015 on a real Win10 on another harddrive. Does anyone here know where I can find such?

Thanks,
Peter

I found and also tested a full trail version of v.2015 and exactly same behavior accured.... FAIL

As this is about BACKUPs maybe worth millions, one must be able to trust the backup solution and support.

I WILL NOT BUY THIS SOFTWARE AS IT HAS FAILED ME BIG TIME...

Thank goodness for the trailversion and SHAME on all the bribed reviewers who giving this software good reviews....

Peter Persson wrote:

I had hope to get that support here on this forum as I have seen Acronis people around here.

This is basically a user to user forum. You have to contact Acronis support directly.

I see you did that in your last post and it was unfortunatley no help.

Peter, 

Please see: 18623: How to get Technical Support: Tips, Tricks and Useful Information and in particular the section reproduced below:

Notes and tips:

• Forum is not a primary support channel

  It’s designed mainly for sharing experience, collecting feedback and joint Community efforts for addressing technical issues
  See Acronis Forum Terms of Use.
  We’re still doing our best to address as many problems reported as possible. 
  We still recommend contacting support directly in case of emergency.

• How to contact support:

  Please find the step-by-step screenshot instructions in this KB article.

I gave the support another run. Sent the AcronisSystemReport.zip file to them. Their conclusion was that my brand new disks had bad sectors and suggested my to run checkdisk. I did run it and nothing is wrong with my disks, see below... Now they refuses to help me further if I'm not buying the product. Trail version does not have any support. I would if it worked, but it obviously does not. This is similar to how ransom wares works. Hijacking your files and then asking for money to release it.

Attaching my AcronisSystemReport.zip here in hope for some help from you more experience users, Thanks

Checking file system on C:
The type of the file system is NTFS.
Volume label is 950Pro-Raid.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  266496 file records processed.                                                         File verification completed.
  7758 large file records processed.                                      0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
  364374 index entries processed.                                                        Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered to lost and found.                     
Stage 3: Examining security descriptors ...
Cleaning up 1060 unused index entries from index $SII of file 0x9.
Cleaning up 1060 unused index entries from index $SDH of file 0x9.
Cleaning up 1060 unused security descriptors.
Security descriptor verification completed.
  48940 data files processed.                                            CHKDSK is verifying Usn Journal...
  41208040 USN bytes processed.                                                            Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  266480 files processed.                                                                File data verification completed.

Stage 5: Looking for bad, free clusters ...
  238306999 free clusters processed.                                                        Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 999629823 KB total disk space.
  45837748 KB in 192220 files.
    159288 KB in 48941 indexes.
         0 KB in bad sectors.
    404787 KB in use by the system.
     65536 KB occupied by the log file.
 953228000 KB available on disk.

      4096 bytes in each allocation unit.
 249907455 total allocation units on disk.
 238307000 allocation units available on disk.

Internal Info:
00 11 04 00 c2 ad 03 00 da d6 07 00 00 00 00 00  ................
ce 00 00 00 2f 00 00 00 00 00 00 00 00 00 00 00  ..../...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Peter, in your system report data, it includes the log files from an attempt by ATIH 2015 to Recover your disk and this shows the following lines, which is why Support have advised a disk error.

iid=94;  date/time=03/05/2016 12:13:51;  message=MFT bitmap corrupted; line_tag=0x65B5EB7011094700
Error_Code=AfYBAQAARwkRcOu1ZU1GVCBiaXRtYXAgY29ycnVwdGVkACRtb2R1bGUAV0M6XFByb2dyYW0gRmlsZXMgKHg4NilcQ29tbW9uIEZpbGVzXEFjcm9uaXNcVHJ1ZUltYWdlSG9tZVxUcnVlSW1hZ2VIb21lU2VydmljZS5leGUAABgABwCc3cCkGBaL701GVCBiaXRtYXAgY29ycnVwdGVkAAA=
id=95;  date/time=03/05/2016 12:13:51;  message=MFT bitmap corrupted; line_tag=0xEF8B1618A4C0DD9C; hide=1

Also, in the Disks.TXT file contained in the System Report, it shows:

4-   d(?) MBR   932G    1K SATA  0-0-0    WDC WD10EZEX-75WN4A0      
  -1  p(1) --JH  100M  100M   87M NTFS   07 NTFS, HPFS   TB2-Revo-Sy -CC--V
  -2  p(2) --IE  224G  224G    0b NTFS   07 NTFS, HPFS   ........... AEE--V MFT bitmap corrupted
  -3  p(3) --KI  708G  708G  307G NTFS   07 NTFS, HPFS   TB2-Backups -CC--V
                 2.7M             free                               ------

This focusses the MFT bitmap corruption to your drive 4 1TB WD10EZEX-75WN4A0 on partition 2.

Finally, you are getting Warning messages issued to the Windows Event logs indicating corruption on your hard disk:

The description for Event ID 98 from source Microsoft-Windows-Ntfs cannot be found. 
Either the component that raises this event is not installed on your local computer 
or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event: 
E:
\Device\HarddiskVolume12
2

The XML View for the above log is shown below:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
  <Provider Name="Microsoft-Windows-Ntfs" Guid="{3FF37A1C-A68D-4D6E-8C9B-F79E8B16C482}" />
  <EventID>98</EventID>  <Version>0</Version>  <Level>2</Level>  <Task>0</Task>  <Opcode>0</Opcode>
  <Keywords>0x8000000000000002</Keywords>
  <TimeCreated SystemTime="2016-05-03T11:05:39.569688100Z" />
  <EventRecordID>1357</EventRecordID>  <Correlation />
  <Execution ProcessID="4" ThreadID="204" />  <Channel>System</Channel>
  <Computer>DESKTOP-H5LKLKH</Computer>  <Security UserID="S-1-5-18" />  </System>
<EventData>
  <Data Name="DriveName">E:</Data>
  <Data Name="DeviceName">\Device\HarddiskVolume12</Data>
  <Data Name="CorruptionActionState">2</Data>  </EventData>  </Event>

This is pointing to corruption on your drive E:\  plus there are other Warning entries which point at drives D:\ & G:\ too.

<EventData>  <Data Name="DriveName">D:</Data>
  <Data Name="DeviceName">\Device\HarddiskVolume9</Data>
  <Data Name="CorruptionActionState">1</Data>  </EventData>  </Event>

<EventData>  <Data Name="DriveName">G:</Data>
  <Data Name="DeviceName">\Device\HarddiskVolume9</Data>
  <Data Name="CorruptionActionState">1</Data>  </EventData>  </Event>

The recommendation at this point is to run CHKDSK /F /R against each of the indicated drives to check & attempt to repair any bad sectors that may be found plus repair the MFT bitmap corruption being reported.

Hi Steve, Thank you for taking the time.

The WCD-disk are not involved in the proces other than storing the .TIB-file on the "TB2-Backups". Do you think this can have affected the recovery of the NVMe-SSD-RAID negatively?

I did made a new backup and restore of the same NVMe-SSD-RAID with Acronis TI 2015 and had no problems. The .TIB-file was stored at the same folder on "TB2-Backups"

I'm currently running CHKDSK /F /R now, but it seems to take HOURS just for one partition I have 6 :-s

The support is telling me that RAID is not supported in v.2011. But I have successfully made a few SATA-SSD-RAID backups and restores with it as well. They refused to believe me, so I hade to make a video showing them. I haven't heard anything from them since then.

Thanks again,
Peter

Peter, there is a KB document: 11681: Acronis True Image: RAID Support which covers all ATIH versions from 2010 to 2016 but only shows a support status for 2014 and later versions.

Thomas quoted KB document: 1689: Backup Archive Compatibility Across Different Product Versions which shows that ATIH 2015 can restore archives created by ATIH 11, 2009 thru 2015.  So you should be able restore from your 2011 backup using the 2015 media assuming that it can see your RAID drives without problem.

With regard to WDC drive - it appears that ATIH walks the whole disk chain when performing these type of actions - you can see this in the log file:

id=38;  date/time=03/05/2016 12:13:36;  message=Analyzing partition '0-0'...
id=39;  date/time=03/05/2016 12:13:36;  message=Analyzing partition '1-1'...
id=40;  date/time=03/05/2016 12:13:36;  message=Analyzing partition '1-2'...
id=41;  date/time=03/05/2016 12:13:36;  message=Analyzing partition 'C:'...
id=42;  date/time=03/05/2016 12:13:36;  message=Analyzing partition '0-0'...
id=43;  date/time=03/05/2016 12:13:37;  message=Analyzing partition '2-1'...
id=44;  date/time=03/05/2016 12:13:37;  message=Analyzing partition '2-2'...
id=45;  date/time=03/05/2016 12:13:37;  message=Analyzing partition 'F:'...
id=46;  date/time=03/05/2016 12:13:37;  message=Analyzing partition '0-0'...
id=47;  date/time=03/05/2016 12:13:37;  message=Analyzing partition 'D:'...
id=48;  date/time=03/05/2016 12:13:37;  message=Analyzing partition 'G:'...
id=49;  date/time=03/05/2016 12:13:37;  message=Analyzing partition '0-0'...
id=50;  date/time=03/05/2016 12:13:38;  message=Analyzing partition 'H:'...
id=51;  date/time=03/05/2016 12:13:38;  message=Analyzing partition 'E:'...
id=52;  date/time=03/05/2016 12:13:38;  message=Analyzing partition 'I:'...
id=53;  date/time=03/05/2016 12:13:38;  message=Analyzing partition '0-0'...
id=54;  date/time=03/05/2016 12:13:38;  message=Analyzing partition 'J:'...

Unfortunately, CHKDSK with the /R switch can take a very long time, especially with larger drives due to the number of sectors that have to be scanned.  Others have tried to work out how long it can take:

See one hit I found or another one - essentially it is 'as long as a piece of string!'...

But my backup, made by V.2011 is not recovable, neither with V.2011 or V.2015 or V2016.
 I can browse the files within the TIB-file, I can recover files and folders but not recover the whole disk.

Regarding HDD-errors. I could not find any error in the log file, But im not an expert. See below

Microsoft Windows [Version 10.0.10586]
(c) 2015 Microsoft Corporation. All rights reserved.

C:\Windows\system32>chkdsk G: /F /R
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N)

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) n

Chkdsk cannot run because the volume is in use by another
process.  Would you like to schedule this volume to be
checked the next time the system restarts? (Y/N) n

C:\Windows\system32>chkdsk G: /F /R
The type of the file system is NTFS.

Chkdsk cannot run because the volume is in use by another
process.  Chkdsk may run if this volume is dismounted first.
ALL OPENED HANDLES TO THIS VOLUME WOULD THEN BE INVALID.
Would you like to force a dismount on this volume? (Y/N) y
Volume dismounted.  All opened handles to this volume are now invalid.
Volume label is TB1-Terrabyte.

Stage 1: Examining basic file system structure ...
  327936 file records processed.
File verification completed.
  2343 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  356430 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  14248 data files processed.
CHKDSK is verifying Usn Journal...
  343194408 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  327920 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  17840722 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 771955711 KB total disk space.
 699751100 KB in 211230 files.
     88584 KB in 14249 indexes.
         0 KB in bad sectors.
    753139 KB in use by the system.
     65536 KB occupied by the log file.
  71362888 KB available on disk.

      4096 bytes in each allocation unit.
 192988927 total allocation units on disk.
  17840722 allocation units available on disk.

C:\Windows\system32>chkdsk I: /F /R
The type of the file system is NTFS.
Volume label is TB2-Backups.

Stage 1: Examining basic file system structure ...
  2048 file records processed.
File verification completed.
  20 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  2504 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  229 data files processed.
CHKDSK is verifying Usn Journal...
  1455616 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  2032 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  70418859 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

 742298623 KB total disk space.
 460530428 KB in 1655 files.
       540 KB in 230 indexes.
         0 KB in bad sectors.
     92215 KB in use by the system.
     65536 KB occupied by the log file.
 281675440 KB available on disk.

      4096 bytes in each allocation unit.
 185574655 total allocation units on disk.
  70418860 allocation units available on disk.

C:\Windows\system32>chkdsk E: /F /R
The type of the file system is NTFS.
Volume label is TB2-SSD-Bootkopia.

Stage 1: Examining basic file system structure ...
  298496 file records processed.
File verification completed.
  1201 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  389006 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Security descriptor verification completed.
  45256 data files processed.
CHKDSK is verifying Usn Journal...
  37227576 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  298480 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  12538436 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

 234357759 KB total disk space.
 183640768 KB in 246271 files.
    153808 KB in 45259 indexes.
         0 KB in bad sectors.
    409439 KB in use by the system.
     65536 KB occupied by the log file.
  50153744 KB available on disk.

      4096 bytes in each allocation unit.
  58589439 total allocation units on disk.
  12538436 allocation units available on disk.

C:\Windows\system32>chkdsk H: /F /R
The type of the file system is NTFS.
Volume label is TB2-Revo-System Reserved.

Stage 1: Examining basic file system structure ...
  256 file records processed.
File verification completed.
  0 large file records processed.
  0 bad file records processed.

Stage 2: Examining file name linkage ...
  346 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
  46 data files processed.
CHKDSK is verifying Usn Journal...
  527104 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  240 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
  22259 free clusters processed.
Free space verification is complete.

Windows has scanned the file system and found no problems.
No further action is required.

    102399 KB total disk space.
      9556 KB in 42 files.
        44 KB in 47 indexes.
         0 KB in bad sectors.
      3759 KB in use by the system.
      2048 KB occupied by the log file.
     89040 KB available on disk.

      4096 bytes in each allocation unit.
     25599 total allocation units on disk.
     22260 allocation units available on disk.

C:\Windows\system32>

Peter, the CHKDSK log does show that it found the bitmap error and fixed it for your drive E:\

C:\Windows\system32>chkdsk E: /F /R
The type of the file system is NTFS.
Volume label is TB2-SSD-Bootkopia.

Stage 5: Looking for bad, free clusters ...
  12538436 free clusters processed.
Free space verification is complete.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

Have you tried to restore from the 2011 image since fixing the MFT bitmap error above?

Do you have a spare drive that you could test the restore to rather than restoring to your current RAID set?

Thanks Eagle eye ;-) But TB2-SSD-Bootkopia is not involver in any way in this backup or restore. Do you think it will work? Ok i will try it.

Good idea with a new drive.  I will try to recover it to another drive. If succeed, I'll make a new backup with 2016 and try to restore the Raid from there. Thanks.

Peter

Now on a different computer, My old one: I could not restore the old backup to a brand new, never used, regular SSD drive. Same happens, first two partitions (some system and recovery partitions) seamed to work well but at the beginning of the third partition the program just stops and got back to idle.

So with the two first partitions okay (as I believed) I made a file restore instead from the third partition. It went well even if it took 7 hours. Made a new image file of this SSD drive using Reflect which has never failed me for years, but will soon..... Wait, but backup was successful.

Tried to boot from the new SSD but nothing.

Tried to make a boot repair with help of my Win10 installation USB. It started "scanning your PC" and then it just restarted the computer without any warning. It booted again on the USB and suddenly the screen blinks and the SSD boots up normally. YES :-D

Removed the USB-pin and tried again, but nothing

Back with the USB-pin and the SSD booted up again... Tried this at least 5 times. Something in the USB helps the SSD booting.

Back to my new computer: Tried to make a recovery from the newly made Reflect image to my NVMe RAID but It failed halfway in the third partition, Error 5. I have not checked it up yet but I will. I tried to recover to yet another SSD but that failed the same way. I decided to make a clone disk instead directly from the SSD to the NVMe RAID and it worked with no errors.

Now booting from the NVMe RAID but it doesn't work. Ran the same boot repair as earlier from my Win10 installation USB but it just says "Can't repair you computer". It seams like the NVMe RAID drivers are missing as NOTHING of the diagnostic tools finds the NVMe RAID. And I have no clue how to add them. Many times I get a message saying "You drive is locked, please unlock it". How to unlock a drive?

Tried to boot from the SSD on my new computer with help of the Win 10 USB but it won't boot.

I will admit that i have not much knowledge about boot, MTF etc etc. But I'm sure I'm close to a solution as I could boot on the SSD on my old computer with help of my Win10 installation USB though. I just need some help to repair the "boot-system" I downloaded a few boot-repair-programs but I have no clue how they work and what to do.

I have spent 5 long days and nights trying to fix this, so im getting little exhausted :-D

Peter, one useful web site that may be of help with the boot issues is:

https://neosmart.net/wiki/category/guides/ 

They produce two utilities that I use myself, EasyBCD to manage and update the Windows Boot Configuration Database that is found on Windows Vista through 10 systems, and iReboot for easier switching between boot menu options.

See: Windows won’t start – Guide for Windows XP, Vista, 7, 8

Oh? Where is my post? I wrote a loooong post about the whole process with a lot of trail and errors today. Anyhow I got it working. Thanks Steve, you are great. You should have worked at the support instead of the ones I got hold of. Thanks again.

Peter, glad to hear you have got this working and am happy to have been able to help you!

On the Support side, that isn't an easy job as I can testify after 31 years doing it at IBM before I retired!