IFL boot recovery for W10 image

[Brian K]

borate, I'm sorry you didn't stick with the restore. Out of thousands of TeraByte restores I've never seen a failure.

[TeraByte Support]

borate wrote:
> Made it all the way through the restore, but same error:
> Partition reduction failed. (1/2/49) The target partition will be deleted.


That means exactly what it reads, the partition needs to be resized smaller, either because you choose a scaled restore, or needed to fit the smaller area/drive, but the partition itself has some issues that chkdsk /f needs to fix (existed before the image was created). So restore without scaling (original drive layout).

[borate]

Yes, Brian. Like you, have seen no outright failure through many years of IFW use. An anomaly with the file system occasionally, but little more.

An earlier restore attempt on this unit failed, but that was attributed to the presence of an old W8.1 image in the recovery partition - perhaps.
So the box was reformatted, W10 HOME installed, and a few programs loaded. Then the image was created. Not long before the attempted restore, CHKDSK had been run, and reported no problems.

it would be instructional to learn specially what setting might have overcome the error: "partition reduction failed. (1/2/49) The target partition will be deleted." Default settings were used.

[Brian K]

borate,

As that OS has been removed from the drive it's going to be difficult to determine what happened to your restore. Can you tell us about the partitions on that previous drive and how you did the image backup and restore.

[borate]

Indeed, it's after the fact now.

No drive change; reformatted months ago. The O/S was reinstalled, ridding the laptop of the old 8/8.1 partitions, with back up written shortly thereafter from within the active system (C:\).

Then, after things went awry last week and restore was attempted repeatedly without success, the drive was reformatted again (as shown in the graphic). And the O/S was installed afresh.

Can't be certain, but as these operations were essentially the same - same drive/same O/S - one might wager that the partitions would be identical. The sole difference that I recall was that the most recent formatting assigned a drive letter D:\ to the recovery partition, which wasn't the case initially.

But, say that there was a partitioning change between image creation and restore. Is there a setting or parameter that could have been utilized to overcome the failure?

The built-in W10 imaging utility copies both C:\ and the SYSTEM RESERVED partition, something I've never done with IFW. Is that wise, and if so should SYSTEM be incorporated in a single creation or imaged separately?

[Brian K]

borate wrote:

> The built-in W10 imaging utility copies both C:\ and the SYSTEM RESERVED
> partition, something I've never done with IFW. Is that wise, and if so
> should SYSTEM be incorporated in a single creation or imaged separately?

I think your previous issue will remain a mystery. When backing up it is advisable to select HD 0 in iFW and get an Entire Drive image. All 3 partitions should be backed up.

[borate]

Good advice, Brian. I'll go that route next time. Ciao.

[TeraByte Support]

it was resizing smaller to fit and dirty so resize aborted.

"Brian K" wrote in message news:14026@public.image...

borate wrote:

> The built-in W10 imaging utility copies both C:\ and the SYSTEM RESERVED
> partition, something I've never done with IFW. Is that wise, and if so
> should SYSTEM be incorporated in a single creation or imaged separately?

I think your previous issue will remain a mystery. When backing up it is
advisable to select HD 0 in iFW and get an Entire Drive image. All 3
partitions should be backed up.

[mjnelson99]

When I Image Win 10, there are 4 partitions-3 very small and C:.
Are they all needed? I don't know. I would rather have them as a
precaution though.
Mary

On 7/15/2017 9:42 PM, borate wrote:
> Indeed, it's after the fact now.
>
> No drive change; reformatted months ago. The O/S was reinstalled, ridding the laptop of the old 8/8.1 partitions, with back up written shortly thereafter from within the active system (C:\).
>
> Then, after things went awry last week and restore was attempted repeatedly without success, the drive was reformatted again (as shown in the graphic). And the O/S was installed afresh.
>
> Can't be certain, but as these operations were essentially the same - same drive/same O/S - one might wager that the partitions would be identical. The sole difference that I recall was that the most recent formatting assigned a drive letter D:\ to the recovery partition, which wasn't the case initially.
>
> But, say that there was a partitioning change between image creation and restore. Is there a setting or parameter that could have been utilized to overcome the failure?
>
> The built-in W10 imaging utility copies both C:\ and the SYSTEM RESERVED partition, something I've never done with IFW. Is that wise, and if so should SYSTEM be incorporated in a single creation or imaged separately?
>
>