backup browsing instable
Acronis True Image 2017 on a Windows 10 Pro 64 PC
Hi,
I have created a backup a few weeks ago with the 2017 version.
After reinstalling my complete PC, I try to restore my files from there.
And it's working sometimes, but absoletley instable. I mean, I can see the folders, the files and everything I expected there, then I start copying some files.
One time (with a small folder) it works. But then I try a big one to a NAS drive => abort after 20% (with network error). Afterwards I try to copy the data to a local disk first. But all (backup) folders are empty now. I restarted the PC. The files are visible again. But after navigating to different folders in the backup, they are empty again. Restart again. Try to copy files to a local drive: abort after 90% ("interface not supported" in german). So I try to google for this issues and found the hint to disable the virus scanner, done, same issues.
Any ideas?
Regards,
Andreas
Hi Steve,
thx for your fast answer :)
- incremental backup of drivce C: and D: (not whole pc)
- clean install of win10 over usb (deleting the old partitions before)
- I've tried two different user folders (my documents)
- doubleclicked the corresponding .tib files in my backup folder (so over the explorer addon), selecting the last backup, then drive C: (which is empty now, but after a restart it has all folders). I didn't find the correct backup entry in my (new installed) ATI 2017...
- I've tried to copy the documents to a new location (right click "copy" and paste to the destination folder)
- I've created a new user (different name but same microsoft account)
Now it doesn't matter, which .tib I will open, the backup drive images with the date and so on are visible, the next level with the drives are visible, too. But all these drives are empty now. I have to restart the computer now. Then I will try to copy folders of drive D: (eleminating permission issues)...
Andreas
After restarting...
Folders are visible now, using drive D:, crash after about 50% with "Schnittstelle nicht unterstützt" (interface not supoorted), all .tib files are empty now (after the third level)...
Attached: Before - After
Andreas
Andreas, this sound like a strange problem when the backup contents disappear until you reboot the computer again!
Can you confirm that you have got ATIH 2017 build 5554 installed on your rebuilt Windows 10 computer?
Where are these backup image files stored? Are these on an external USB disk drive or on a network drive?
If on a USB drive, is this powered through the USB port or does it have its own power supply?
If on a Network drive, are you accessing this over WiFi or using an Ethernet cable?
Have you checked the integrity of the backup storage drive, i.e. run CHKDSK /F on the drive?
What was the reason that led to you needing to do a clean reinstall of Windows 10 on your computer? Is there any possibility of there being a hardware problem with your internal disk drive(s) or any other components?
Please look at KB 58783: Acronis True Image 2017: Files and Folders Are Not Shown When Browsing Backups in Windows Explorer as this may be relevant to the problem you are seeing.
If you have not yet created the Acronis bootable Rescue Media then I would recommend doing so and testing that you can boot your computer using this media, as this may offer an alternative approach to restoring your user data from your backup images, and do so outside of any influence of Windows and/or any security programs etc.
Acronis True Image Version 2017, Build 5554, yes. Activated.
The backup images are stored on an internal 2 TB harddisk via SATA.
CHKDSK on my backup drive: no error.
I didn't change my hardware setup (only upgrade the power supply, but this is driverless) , just reinstalled/cleaned up my computer (my gf got an own computer now ;))
Now I try the cleanup/reinstall procedure of ATIH2017...
Reinstalled, same issue, crash after ~60%, see image
Andreas
Andreas, some more questions...
Have you run CHKDSK /F against the drive where you are restoring this data to?
If possible, could you create an Acronis System Report and attach it to this forum topic - this will be created as a zip file and given you have done a clean install of ATIH 2017, shouldn't be too big to be uploaded. This will give us more information from the various log files plus also contains the System Event Logs etc.
Hi Steve,
Destination drive checked too without errors.
System Report attached...
Andreas
Andreas, thank you for the System Report information.
One problem I see from the disks.txt file is:
PS Speed IFace Hs-Bs-Tg Model
Num NT L9NO Size FSsize Free FS Type Label ABCHSV Error
---- ----- ---- ----- ----- ----- ------ --------------- ----------- ------ ----------
1- d(2) GPT 2.7T 1K SATA 0-0-0 WDC WD30EFRX-68AX9N0
MBR ------
GPTpri -----v
MSresr ------
-2 --FG 2.7T 2.7T 1.2T NTFS 07 NTFS, HPFS HD_DATA.... --e--V Kann Volume-Snapshot nicht erstellen
Partition 1-2: file system
FS: NTFS
File System Error 0x70021: Kann Volume-Snapshot nicht erstellen (Unable to create volume snapshot)
| line: 0x2cbdd167cbca9594
| Datei: k:\5554\resizer\generic\fs.cpp:224
| Funktion: resizer::FSProcessor::SetSnapshotBitmap
| line: 0x2cbdd167cbca9594, k:\5554\resizer\generic\fs.cpp:224, resizer::FSProcessor::SetSnapshotBitmap
| $module: ti_managers_vs_5554
|
| error 0x10c44e: Failed to set snapshot bitmap.
| line: 0x3fec04e376b89f00
| Datei: k:\5554\fdisk\win_snapshot.cpp:522
| Funktion: win_snapshot_volume::SetBitmap
| line: 0x3fec04e376b89f00, k:\5554\fdisk\win_snapshot.cpp:522, win_snapshot_volume::SetBitmap
| blocks: 0xaea64bfc
| $module: ti_managers_vs_5554
|
| error 0x9: Unbekannter Status.
| line: 0x2aacb7b2ab852ac
| Datei: k:\5554\fdisk\ver2\arch\windows\win_errors.cpp:40
| Funktion: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, k:\5554\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x32
| $module: ti_managers_vs_5554
|
| error 0xfff0: Die Anforderung wird nicht unterstützt
| line: 0xbd28fdbd64edb8f1
| Datei: k:\5554\common\error.cpp:307
| Funktion: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, k:\5554\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070032
| $module: ti_managers_vs_5554
FSSize: 5860268025 (2.7T)
BlockSize: 8 (4K)
BlockCount: 732533503 (2.7T)From the System Event Log.
Log Name: System
Source: Volsnap
Date: 04/02/2017 17:51:04
Event ID: 10
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: AJ_MAIN
Description: The shadow copy of volume C: took too long to install.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Volsnap" Guid="{cb017cd2-1f37-4e65-82bc-3e91f6a37559}" EventSourceName="volsnap" />
<EventID Qualifiers="49158">10</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-02-04T17:51:04.687681600Z" />
<EventRecordID>1667</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="224" />
<Channel>System</Channel>
<Computer>AJ_MAIN</Computer>
<Security />
</System>
<EventData>
<Data Name="DeviceName">
</Data>
<Data Name="VolumeName">C:</Data>
<Data Name="NTSTATUS">c0000120</Data>
<Data Name="SourceTag">183</Data>
<Data Name="SourceFileID">0x0001</Data>
<Data Name="SourceLine">9004</Data>
The above errors are the only things that stand out from the System Report files though there may be other things in there but unrelated to this topic.
I am not sure how snapshot is involved in your copying files & folders from your backup image via Windows Explorer but there is a sure way of eliminating this from being involved which is to boot from the Acronis Rescue Media and attempt to recover some of the same files & folders completely outside of Windows.
Another option you could try, is to Mount your backup file as a drive letter (if allowed) and then try the copy from the mounted drive. This may not be possible if this is a pure Files & Folders backup image.
Finally, you should consider opening a Support Case directly with Acronis Support for this issue and reference this forum topic so that the support team can see what has already been tried etc.
Hi Steve,
No, the error above comes from my try to make a backup to my new NAS drive.
For some reason, it fails the first time, but during my second try it works (but I've stopped the backup after a while).
One day later, I tried it again, and now I have to enter a user and password for my network share, even though it works without them yesterday (no authentication is needed for the shares).
Then I've tested the USB rescue media scenario: the booting over USB succeeded, but my try to call the restore menu (second menu item, I don't know anymore) results in a crash (segmentation fault). Then I tried ATIH2016, same instability while reading the .tib files. And I've copied them to another drive before.
I'm frustated now, my system seems to be stable (no crash in all other programs atm), and was it definitely before my reinstall of windows 10.
The hardware is new...
I will continue to check my system, making stress tests, trying other backup programs and so on.
Thank you for your support, Steve!
Andreas
Andreas, please see post: 122489: Bootable media - seg fault when clicking restore disks and in particular the final update in post #5 from Ekaterina about the segmentation fault issue which was declared as fixed in the 2017 version!
If you are seeing this with the 2017 Rescue Media, then you should open a Support Case to report this.