Direkt zum Inhalt

True image clone stuck at 15 seconds remaining.

Thread needs solution

Acronis true image recovery cd clone has been stuck on 15 seconds remaining step 6 of 7 for about 7 hours.

It has been copying sector by sector between two 3tb Toshiba hard drives. 

What should I ddo Has it crashed or is this a known problem?

0 Users found this helpful

Acronis is notoriously unreliable when giving time estimates.

Did you want to clone sector by sector, or did Acronis decide that was what was needed. If the latter, ATI would have selected sector by sector mode because it discovered problem(s) with the source drive. If that is the case it may be dealing with the part of the HDD that has issues causing the sector by sector cloning to be necessary.

Ian

IanL-S wrote:

Acronis is notoriously unreliable when giving time estimates.

Did you want to clone sector by sector, or did Acronis decide that was what was needed. If the latter, ATI would have selected sector by sector mode because it discovered problem(s) with the source drive. If that is the case it may be dealing with the part of the HDD that has issues causing the sector by sector cloning to be necessary.

Ian

At first it said do a a automatic clone but when I went back to double check I had selected the correct drives it said to do a sector by sector clone. 

Hi Joe, this suggest that there is a problem with the source disk.

I am uncertain about what you should do next.

It would help if we knew exactly what the problem is.

Some more information may assist in formulating what to do next.

  1. It the drive being cloned the one with operating system on it; if so what version and build is it - for example Windows 10 x64 build 1903.
  2. Is the clone being done from within Window or using recovery media. If the latter, what sort of recovery media (USB stick or DVD), and what recovery environment (WinRE, WinPE or Linux). These are discussed in the user guide 12.1.1 Acronis Media Builder. As you will see it is most likely that you have created WinRE recovery media.

Ian

It is getting close to the switch over between users in my part of the world (Australia) and those in Europe and North America, so while I may not be able to respond until tomorrow there are other knowledgeable users who will be able to offer assistance. Edit: Not a formal switchover, just that users in different part of the world frequent the forum at different times determined by their location, if they are night-owls, or if like me they are retired and tend to frequent the forum during daylight hours.

IanL-S wrote:

Hi Joe, this suggest that there is a problem with the source disk.

I am uncertain about what you should do next.

It would help if we knew exactly what the problem is.

Some more information may assist in formulating what to do next.

  1. It the drive being cloned the one with operating system on it; if so what version and build is it - for example Windows 10 x64 build 1903.
  2. Is the clone being done from within Window or using recovery media. If the latter, what sort of recovery media (USB stick or DVD), and what recovery environment (WinRE, WinPE or Linux). These are discussed in the user guide 12.1.1 Acronis Media Builder. As you will see it is most likely that you have created WinRE recovery media.

Ian

It is getting close to the switch over between users in my part of the world (Australia) and those in Europe and North America, so while I may not be able to respond until tomorrow there are other knowledgeable users who will be able to offer assistance. Edit: Not a formal switchover, just that users in different part of the world frequent the forum at different times determined by their location, if they are night-owls, or if like me they are retired and tend to frequent the forum during daylight hours.

It is a Synology raid drive cloned with the recovery cd. 

It is a Synology raid drive cloned with the recovery cd. 

Do you know what exact file system is in use on the Synology drive, and is this a single drive or a RAID array with multiple drives?

My understanding from my own Synology NAS is that it is using a Linux type file system but I have never dug deep into the works to confirm which one?

The point here is that Acronis may default to using sector-by-sector mode with non-native Windows file systems, and this in turn means a whole lot more data is being copied, cloned etc than if only the used data aspect of the drive were involved.

There have been open topics in the forums dealing with how Acronis works with Linux EXT4 file systems where certain settings were needed to get Acronis to correctly recognise the drive and not use sector by sector mode.

See forum topic: EXT4 partition backup (Linux).

Steve Smith wrote:

It is a Synology raid drive cloned with the recovery cd. 

Do you know what exact file system is in use on the Synology drive, and is this a single drive or a RAID array with multiple drives?

My understanding from my own Synology NAS is that it is using a Linux type file system but I have never dug deep into the works to confirm which one?

The point here is that Acronis may default to using sector-by-sector mode with non-native Windows file systems, and this in turn means a whole lot more data is being copied, cloned etc than if only the used data aspect of the drive were involved.

There have been open topics in the forums dealing with how Acronis works with Linux EXT4 file systems where certain settings were needed to get Acronis to correctly recognise the drive and not use sector by sector mode.

See forum topic: EXT4 partition backup (Linu

I think Synology used gpt.

I have stopped the acronis and an trying it with easyus in windows which is also doing sector by sector I did notice however that acronis had only copied over about 3gb in 13 hours? 

Joe, see webpage: Which file system should I use to create a volume?

This suggests that either EXT4 or BTRFS is used by Synology depending on the NAS model.

I didn't think Acronis supports cloning of RAID or dynamic disks.

For the mention of the 2x 3TB drives, if the clone defaulted to sector by sector and if these are not RAIDED, you probably need to run chkdsk /f /r on both of them. S ctor by sector is only enforced when bad sectors are identified in the disk

https://kb.acronis.com/content/56634