Win 8 PV corruption update

User discussion and information resource forum for Image products.
Post Reply
borate
Posts: 112
Joined: Thu Oct 27, 2011 9:51 pm

Win 8 PV corruption update

Post by borate »

Imaging W8 while it is in use still results in NTFS corruption when the image is restored.
If an image is made of the same partition, but while running W7, no corruption.

"Fast start up" is not enabled.
W8 PV was installed from scratch, not updated from W8 CPV.
W8 uses the same apps, same hardware (but some different drivers) than W7.
Both O/S are in AHCI mode.
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: Win 8 PV corruption update

Post by TeraByte Support »

there wouldn't be any corruption if your data isn't already corrupted and
you verified byte-for-byte the backup (meaning memory is good). It's
backing up the raw in-use sectors of the partition locked with either
PHYLock or VSS (you of course aren't ignoring or disabling locking I would
presume). If you're confusing an "in-use" message about data "may" be
corrupt because it want's to run chkdsk, then that's just the normal chkdsk
message, it means nothing.


"borate" wrote in message news:2549@public.image...

Imaging W8 while it is in use still results in NTFS corruption when the
image is restored.
If an image is made of the same partition, but while running W7, no
corruption.

"Fast start up" is not enabled.
W8 PV was installed from scratch, not updated from W8 CPV.
W8 uses the same apps, same hardware (but some different drivers) than W7.
Both O/S are in AHCI mode.

Brian K
Posts: 2214
Joined: Fri Aug 12, 2011 1:11 am
Location: NSW, Australia

Re: Win 8 PV corruption update

Post by Brian K »

Borate,

What do you mean by "corruption"? I backup and restore Win8 with IFW and there are no problems.
borate
Posts: 112
Joined: Thu Oct 27, 2011 9:51 pm

Re: Win 8 PV corruption update

Post by borate »

TeraByte Support wrote:
> There wouldn't be any corruption if your data isn't already corrupted and
> you verified byte-for-byte the backup (meaning memory is good). It's
> backing up the raw in-use sectors of the partition locked with either
> PHYLock or VSS (you of course aren't ignoring or disabling locking I would
> presume). If you're confusing an "in-use" message about data "may" be
> corrupt because it wants to run chkdsk, then that's just the normal chkdsk
> message, it means nothing.

There is no difference in how the BU is performed - just where it's performed - and
PHYLock is active. Nothing disabled. Not byte-for-byte. Same routine for a decade.

When the W8 drive is backed up from W7 it restores fine. Same data as when
using W8 to image its own O/S. But THAT doesn't go well; after restore the
drive is indeed "dirty" and will auto-run CHKDSK if I don't do so manually.

Corruption appears to occur at the very end of the restore; lots of drive activity,
a hang with a "completing backup" message. Finally, "successful restore" appears.

Imaging W7 C:\ partition while it is in use restores from W8 just fine. Imaging and
restoring a W7 partition made while using the W8 drive also succeeds.
borate
Posts: 112
Joined: Thu Oct 27, 2011 9:51 pm

Re: Win 8 PV corruption update

Post by borate »

Brian K wrote:
> Borate,
>
> What do you mean by "corruption"? I backup and restore Win8 with IFW and there are no problems.

While using W8, an image is made of the W8 partition (C:\) and stored on another drive.
When that image is restored the W8 NTFS is corrupted, requiring that CHKDSK be run. To restate...

Drive 0 (SSD) contains W7 on C:\
Drive 1 (SATA) contains W8 on C:\ and a data partition D:\

Image W7 to D:\ while in W7, then restore W7 while in W8. All is well.
Image W7 to D:\ while in W8, then restore W7 while in W8. All is well.

Image W8 to D:\ while in W7, then restore W8 while in W7. All is well.
Image W8 to D:\ while in W8, then restore W8 while in W7. NTFS drive 1 W8 partition will corrupt.
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: Win 8 PV corruption update

Post by TeraByte Support »

as mentioned, doesn't necessarily have to do with "corruption". MS may have
an in-use flag and if it finds it's on, it runs a chkdsk, the message that
shows when chkdsk is going to be run may be alarming, but it just means it's
going to run chkdsk.

"borate" wrote in message news:2554@public.image...

Brian K wrote:
> Borate,
>
> What do you mean by "corruption"? I backup and restore Win8 with IFW and
> there are no problems.

While using W8, an image is made of the W8 partition (C:\) and stored on
another drive.
When that image is restored the W8 NTFS is corrupted, requiring that CHKDSK
be run. To restate...

Drive 0 (SSD) contains W7 on C:\
Drive 1 (SATA) contains W8 on C:\ and a data partition D:\

Image W7 to D:\ while in W7, then restore W7 while in W8. All is well.
Image W7 to D:\ while in W8, then restore W7 while in W8. All is well.

Image W8 to D:\ while in W7, then restore W8 while in W7. All is well.
Image W8 to D:\ while in W8, then restore W8 while in W7. NTFS drive 1 W8
partition will corrupt.

TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: Win 8 PV corruption update

Post by TeraByte Support »

I also went ahead and installed Win8 and did a backup in Win8 restored using
IFD (in BIBM) after deleting and wiping it and restore no issue.

While testing W8, it's obvious and clear that the hybridboot causes data
corruption anytime you alter meta data on any partition visible to Win8 from
outside of Win8 (as hibernation does in general). Why anyone would design
hibernation resume to not remount file systems is beyond me, but that's what
they have been doing for a while, just becomes more a problem when shutdown
doesn't shutdown but hibernates.


Post Reply