Not to belabor the issue, and irrespective of what is to blame, has no way been discovered to overcome the "NTFS is dirty" flag that forces a chkdsk when an IFW image of Windows 8 that was made from within that O/S is later restored?
This behavior has been noted by other IFW users in postings to MS-related forums. The system here is hardly esoteric: ASUS P8P67LE/Intel 2600K with two drives: Win 7 on one and Win 8 on the other. Dual boot. Windows 7 has no problem when W7 images that were created while it was running are restored.
"Fast start up (boot)" is not enabled, per the Terabyte "sticky." Disabling "hybrid sleep" has also been tested, as have both IFW 32- and 64-bit. The fault persists - repeatable every time - as it has been in all Win 8 incarnations - CPV through RTM.
The Win 8 "dirty" issue
Re: The Win 8 "dirty" issue
borate,
I don't get that issue. How are you multi-booting? With BIBM? Are you using limited primaries or unlimited? Are both OS hidden from each other? Sorry if these questions have been asked before.
I don't get that issue. How are you multi-booting? With BIBM? Are you using limited primaries or unlimited? Are both OS hidden from each other? Sorry if these questions have been asked before.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: The Win 8 "dirty" issue
not reproducible - lot's of backup/restore of w8 - but the dirty flag itself
isn't much of a problem - it would just run chkdsk. If you're seeing
corruption, it's definitely related to something else, maybe you may have a
some caching software installed that is causing a problem for you? Things
like "RapidBoot HDD Accelerator" may cause problems.
"borate" wrote in message news:3922@public.image...
Not to belabor the issue, and irrespective of what is to blame, has no way
been discovered to overcome the "NTFS is dirty" flag that forces a chkdsk
when an IFW image of Windows 8 that was made from within that O/S is later
restored?
This behavior has been noted by other IFW users in postings to MS-related
forums. The system here is hardly esoteric: ASUS P8P67LE/Intel 2600K with
two drives: Win 7 on one and Win 8 on the other. Dual boot. Windows 7 has
no problem when W7 images that were created while it was running are
restored.
"Fast start up (boot)" is not enabled, per the Terabyte "sticky." Disabling
"hybrid sleep" has also been tested, as have both IFW 32- and 64-bit. The
fault persists - repeatable every time - as it has been in all Win 8
incarnations - CPV through RTM.
isn't much of a problem - it would just run chkdsk. If you're seeing
corruption, it's definitely related to something else, maybe you may have a
some caching software installed that is causing a problem for you? Things
like "RapidBoot HDD Accelerator" may cause problems.
"borate" wrote in message news:3922@public.image...
Not to belabor the issue, and irrespective of what is to blame, has no way
been discovered to overcome the "NTFS is dirty" flag that forces a chkdsk
when an IFW image of Windows 8 that was made from within that O/S is later
restored?
This behavior has been noted by other IFW users in postings to MS-related
forums. The system here is hardly esoteric: ASUS P8P67LE/Intel 2600K with
two drives: Win 7 on one and Win 8 on the other. Dual boot. Windows 7 has
no problem when W7 images that were created while it was running are
restored.
"Fast start up (boot)" is not enabled, per the Terabyte "sticky." Disabling
"hybrid sleep" has also been tested, as have both IFW 32- and 64-bit. The
fault persists - repeatable every time - as it has been in all Win 8
incarnations - CPV through RTM.
Re: The Win 8 "dirty" issue
Brian K wrote:
> borate,
>
> I don't get that issue. How are you multi-booting? With BIBM? Are you using limited primaries or unlimited? Are both OS hidden from each other?
Perhaps "multi-booting" in the traditional sense is not accurate. Excuse my ignorance.
When Win 8 was installed on a SATA drive, it created a boot choice menu which is set to default to Win 7 (SSD drive). Or it can be manually toggled to boot into the Win 8 drive instead.
Nothing is hidden. Both drives/operating systems fully see each other's files. When Win 7 is running it is C: and Win 8 files show up under J. When Win 8 is running it is C:, Win 7's files become J:
Each O/S is a primary, visible partition. On the Win 7 drive there is also a system partition, nothing more. A data partition on the Win 8 drive is D when that O/S runs. When in Win 7 it becomes K:
Prior to the advent of Win 8, XP ran on one drive, Win 7 on the other and each had two partitions. When XP was C: and D:, Win 7 was J: and K:. When Win 7 was in use, it was just the opposite.
At that time there was no multi-boot menu; if I wanted to override the default I simply used F8 and selected the desired drive. No corruption or "dirty" flags were ever seen with that set up.
> borate,
>
> I don't get that issue. How are you multi-booting? With BIBM? Are you using limited primaries or unlimited? Are both OS hidden from each other?
Perhaps "multi-booting" in the traditional sense is not accurate. Excuse my ignorance.
When Win 8 was installed on a SATA drive, it created a boot choice menu which is set to default to Win 7 (SSD drive). Or it can be manually toggled to boot into the Win 8 drive instead.
Nothing is hidden. Both drives/operating systems fully see each other's files. When Win 7 is running it is C: and Win 8 files show up under J. When Win 8 is running it is C:, Win 7's files become J:
Each O/S is a primary, visible partition. On the Win 7 drive there is also a system partition, nothing more. A data partition on the Win 8 drive is D when that O/S runs. When in Win 7 it becomes K:
Prior to the advent of Win 8, XP ran on one drive, Win 7 on the other and each had two partitions. When XP was C: and D:, Win 7 was J: and K:. When Win 7 was in use, it was just the opposite.
At that time there was no multi-boot menu; if I wanted to override the default I simply used F8 and selected the desired drive. No corruption or "dirty" flags were ever seen with that set up.
Last edited by borate on Fri Nov 30, 2012 7:59 pm, edited 1 time in total.
Re: The Win 8 "dirty" issue
No caching software here. The extensive corruption noted in earlier posts has not been seen in some time. Just the "dirty" flag. When chkdsk runs, relatively quickly but still taking about five minutes, no errors are shown.
TeraByte Support wrote:
> Not reproducible - lots of backup/restore of w8 - but the dirty flag itself isn't much of a problem - it would just run chkdsk. If you're seeing corruption, it's definitely related to something else, maybe you may have a
> some caching software installed that is causing a problem for you? Things like "RapidBoot HDD Accelerator" may cause problems.
>
>> "borate" wrote in message news:3922@public.image...
>>
>> Not to belabor the issue, and irrespective of what is to blame, has no way been discovered to overcome the "NTFS is dirty" flag that forces a chkdsk when an IFW image of Windows 8 that was made from within that O/S
>> is later restored?
>>
>> This behavior has been noted by other IFW users in postings to MS-related forums. The system here is hardly esoteric: ASUS P8P67LE/Intel 2600K with two drives: Win 7 on one and Win 8 on the other. Dual boot.
>> Windows 7 has no problem when W7 images that were created while it was running are restored.
>>
>> "Fast start up (boot)" is not enabled, per the Terabyte "sticky." Disabling "hybrid sleep" has also been tested, as have both IFW 32- and 64-bit. The fault persists - repeatable every time - as it has been in all Win 8 incarnations -
>> CPV through RTM.
TeraByte Support wrote:
> Not reproducible - lots of backup/restore of w8 - but the dirty flag itself isn't much of a problem - it would just run chkdsk. If you're seeing corruption, it's definitely related to something else, maybe you may have a
> some caching software installed that is causing a problem for you? Things like "RapidBoot HDD Accelerator" may cause problems.
>
>> "borate" wrote in message news:3922@public.image...
>>
>> Not to belabor the issue, and irrespective of what is to blame, has no way been discovered to overcome the "NTFS is dirty" flag that forces a chkdsk when an IFW image of Windows 8 that was made from within that O/S
>> is later restored?
>>
>> This behavior has been noted by other IFW users in postings to MS-related forums. The system here is hardly esoteric: ASUS P8P67LE/Intel 2600K with two drives: Win 7 on one and Win 8 on the other. Dual boot.
>> Windows 7 has no problem when W7 images that were created while it was running are restored.
>>
>> "Fast start up (boot)" is not enabled, per the Terabyte "sticky." Disabling "hybrid sleep" has also been tested, as have both IFW 32- and 64-bit. The fault persists - repeatable every time - as it has been in all Win 8 incarnations -
>> CPV through RTM.
Re: The Win 8 "dirty" issue
borate,
Maybe that is our difference. You are using the Microsoft Way of multi-booting. Strange things can happen when OS see each other.
http://www.goodells.net/multiboot/principles.shtml
Most of us here avoid it like the plague.
Maybe that is our difference. You are using the Microsoft Way of multi-booting. Strange things can happen when OS see each other.
http://www.goodells.net/multiboot/principles.shtml
Most of us here avoid it like the plague.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: The Win 8 "dirty" issue
The dirty flag itself wouldn't be unexpected in some cases - did you change
the max wait time or the write free time? Is it waiting until the max time
or before then? same thing if using VSS ?
"borate" wrote in message news:3929@public.image...
No caching software here. The extensive corruption noted in earlier posts
has not been seen in some time. Just the "dirty" flag. When chkdsk runs,
relatively quickly but still taking about five minutes, no errors are shown.
the max wait time or the write free time? Is it waiting until the max time
or before then? same thing if using VSS ?
"borate" wrote in message news:3929@public.image...
No caching software here. The extensive corruption noted in earlier posts
has not been seen in some time. Just the "dirty" flag. When chkdsk runs,
relatively quickly but still taking about five minutes, no errors are shown.
Re: The Win 8 "dirty" issue
Brian K wrote:
> borate,
>
> Maybe that is our difference. You are using the Microsoft Way of multi-booting. Strange things can happen when OS see each other.
>
> http://www.goodells.net/multiboot/principles.shtml
>
> Most of us here avoid it like the plague.
Could be the cause. Still, as noted, when XP and W7 "saw" one another there was no problem ... until Win 8 replaced XP.
> borate,
>
> Maybe that is our difference. You are using the Microsoft Way of multi-booting. Strange things can happen when OS see each other.
>
> http://www.goodells.net/multiboot/principles.shtml
>
> Most of us here avoid it like the plague.
Could be the cause. Still, as noted, when XP and W7 "saw" one another there was no problem ... until Win 8 replaced XP.
Re: The Win 8 "dirty" issue
>> "borate" wrote in message news:3929@public.image...
>>
>> No caching software here. The extensive corruption noted in earlier posts has not been seen in some time. Just the "dirty" flag. When chkdsk runs,
>> relatively quickly but still taking about five minutes, no errors are shown.
> TeraByte Support wrote:
> The dirty flag itself wouldn't be unexpected in some cases - did you change the max wait time or the write free time?
> Is it waiting until the max time or before then? same thing if using VSS?
Nothing was changed. All IFW setttings are the defaults.
>>
>> No caching software here. The extensive corruption noted in earlier posts has not been seen in some time. Just the "dirty" flag. When chkdsk runs,
>> relatively quickly but still taking about five minutes, no errors are shown.
> TeraByte Support wrote:
> The dirty flag itself wouldn't be unexpected in some cases - did you change the max wait time or the write free time?
> Is it waiting until the max time or before then? same thing if using VSS?
Nothing was changed. All IFW setttings are the defaults.
Re: The Win 8 "dirty" issue
On Fri, 30 Nov 2012 13:29:28 PST, just as I was about to take a herb,
borate disturbed my reverie and wrote:
>Still, as noted, when XP and W7 "saw" one another there was no problem
IIRC, one's restore points would delete the others in that situation.
It is a VERY bad thing to let windows installs see each other - all
sorts of spooky stuff can happen. I have common data partitions that
all OSs can access, but none can see any other unless I need it to for
some specific reason.
--
Cheers
DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).
borate disturbed my reverie and wrote:
>Still, as noted, when XP and W7 "saw" one another there was no problem
IIRC, one's restore points would delete the others in that situation.
It is a VERY bad thing to let windows installs see each other - all
sorts of spooky stuff can happen. I have common data partitions that
all OSs can access, but none can see any other unless I need it to for
some specific reason.
--
Cheers
DrT
______________________________
We may not be able to prevent the stormy times in
our lives; but we can always choose whether or not
to dance in the puddles (Jewish proverb).