** UPDATE: ** NTFS corruption

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

** UPDATE: ** NTFS corruption

Post by borate »

Original post...
Curious. Using IFW on an SSD Vertex drive, a restore is made to a partition on another SATA drive.
The restore is successful but the NTFS file system on the SATA is corrupted, necessitating a CHKDSK /f.
-0-0-

After many hours experimenting with Win 8 it is now running as well as might be expected of a pre-release:
SFC clean, few event errors, generally good response. Still, NTFS corrupts after restore. Here's the pattern...

SSD drive 0 has Win 7 on one of its two partitions
SATA drive 1 has Win 8 on one of its two partitions

When Win 8 is imaged while the PC is running Win 7 on drive 0 and the image is later restored to drive 1, all is well.
Not the case when the image has been created while running Windows 8 on drive 1...

Prior to imaging W8 from its own drive, CHKNTFS shows that the partition is not dirty.
After imaging and validating, still not dirty.
After restore (done while running W7 on the other drive), dirty.

If it makes any difference, the image is stored on the other partition of the SATA, Windows 8 drive.

Seeing the "W8 Corruption" post from TeraByte, I should mention that on this installation there is no "enable hybrid boot"
choice in the shutdown options section. There IS a "hibernate" option, which is unchecked. And under SLEEP, in the power
options, the "hybrid sleep" box had been changed to NO prior to the experiment described above.
Last edited by borate on Sun Apr 01, 2012 4:21 am, edited 10 times in total.
Brian K
Posts: 2214
Joined: Fri Aug 12, 2011 1:11 am
Location: NSW, Australia

Re: NTFS corruption

Post by Brian K »

the NTFS file system on the SATA is corrupted.
Borate, can you give us more details. Are you using the first Win8 Developer Preview? Or the one released in the last week or two?
borate
Posts: 112
Joined: Thu Oct 27, 2011 9:51 pm

Re: NTFS corruption

Post by borate »

Hi Brian.
This would be the latest release - build 8250 Consumer Preview evaluation.

The problem likely occurs at the tail end of the restore: IFW reports "closing" which is a term usually never seen.
The disk thrashes for about five-seconds then the process completes ... and the NTFS system is corrupt.

Some months ago there was a bug in Vertex-PLUS firmware that repeatedly corrupted THAT SSD, but none since
a firmware update. Back then the SATA drive would occasionally corrupt as well. Likely not related to this issue.

In a few months we'll see if BETA Win 8 exhibits the same behavior on the SATA.
DrTeeth
Posts: 1289
Joined: Fri Aug 12, 2011 6:58 pm

Re: NTFS corruption

Post by DrTeeth »

On Fri, 9 Mar 2012 20:34:42 PST, just as I was about to take a herb,
borate disturbed my reverie and wrote:

>... and the NTFS system is corrupt.
The is one issue that I have noticed across all computers here. They
all have multiple hard disks and multiple partitions. On the first
boot after win 8 is installed (even when booting to another version of
windows) all the partitions on all the other hard disks go through a
chkdsk /f on boot. This 'may' be connected to your finding.
--

Cheers

DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose to dance
in the puddles (Jewish proverb).
borate
Posts: 112
Joined: Thu Oct 27, 2011 9:51 pm

Re: NTFS corruption

Post by borate »

DrTeeth wrote:On Fri, 9 Mar 2012 20:34:42 PST, just as I was about to take a bath, borate pulled the stopper and wrote:

>... and the NTFS system is corrupt.
DrTeeth wrote:The is one issue that I have noticed across all computers here. They all have multiple hard disks and multiple partitions.
On the first boot after win 8 is installed (even when booting to another version of windows) all the partitions on all the
other hard disks go through a chkdsk /f on boot. This 'may' be connected to your finding.
Indeed. If the file system is 'dirty' a relatively speedy chkdsk runs automatically here. But I have observed in the past that this may not fix all faults.
As an example, once, after chkdsk allegedly did its thing on the SSD drive, the O/S ran okay yet most start menu shortcuts were missing.

Win 8 was over-installed, retaining the installed apps, then re-imaged using the stable W7 SSD drive and restored twice. NO corruption either time.

Had the images been created using the SATA instead, running in Windows 8, perhaps results would have been different.
System file checker (SFC) reports corrupted W8 O/S files which, according to a Microsoft tech, is no big deal. Still, that might have some relevancy here.
TeraByte Support
Posts: 3598
Joined: Thu May 05, 2011 10:37 pm

Re: NTFS corruption

Post by TeraByte Support »

If you backed up a system requiring chkdsk /f then it will also require it
on the restore. Also, if it was marked dirty at the time of the backup, it
will do a chkdsk /f on boot. Also, a hibernated system being backed up can
cause issues as well. For Win8, you'd be best to turn off gimmicks like
"hybrid boot" (found in power settings) to ensure a clean power down and not
just hibernating parts and leaving open potential for corruption (until the
MS can ensure everyone that changes to file system between boots won't
corrupt them.).

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

Curious. Using IFW on an SSD Vertex drive, a restore is made to a partition
on another SATA drive.
The restore is successful but the NTFS file system on the SATA is corrupted,
necessitating a CHKDSK /f.

Possibly related: The partition being restored contains the Alpha Windows 8
Consumer PV release.
A test restore of XP that months ago was made from the
[i:1s3li71r]same[/i:1s3li71r] SATA partition did not corrupt the files.

DrTeeth
Posts: 1289
Joined: Fri Aug 12, 2011 6:58 pm

Re: ** UPDATE: ** NTFS corruption

Post by DrTeeth »

Sorry for adding to an old thread, but I have found similar behaviour when using hibernate on my main PC - which has Win 7 x64, Vista x64 and XP (x86) on it (amongst other non-wondows OSs). I have started using hibernate and find chkdsk running quite often on a reboot - no errors found yet unlike with Win 8.

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

Re: ** UPDATE: ** NTFS corruption

Post by TeraByte Support »

yes, the way windows comes out of hibernation is dangerous, which is why
Win8 with the fast boot (or whatever they are calling the gimmick today) is
dangerous. They should flush all data to disk on hibernate, dismount the
file system, then upon resume, the dismounted files system is remounted.
You can use bootnow with the /hibernate option to ensure you don't boot in
to another OS when hibernated and using BootIt.

This thread should probably be in bootit, not image.

"DrTeeth" wrote in message news:2762@public.image...

Sorry for adding to an old thread, but I have found similar behaviour when
using hibernate on my main PC - which has Win 7 x64, Vista x64 and XP (x86)
on it (amongst other non-wondows OSs). I have started using hibernate and
find chkdsk running quite often on a reboot - no errors found yet unlike
with Win 8.

DrT

Post Reply