serious issue with Write Changed Sectors Only enabled

[giulia]

Hi
today i restored an w8.1 Image created 10 days ago with the settings "Write Changed Sectors Only" with image for windows 2.90 (w8.1 winpe based ) and when i rebboted my windows 8.1 crashed , it start to boot after it blocked with an error
0xc000021a
i had to restore the image again without Write Changed Sectors Only , it works now

i got this error ->https://neosmart.net/wiki/wp-content/up ... -8-8-1.png

i know the last version 2.97

are there some bug fixed between 2.90 to 2.97 related to "Write Changed Sectors Only"


thanks

[TeraByte Support]

No, it wouldn't have anything to do with that option itself, there is no real difference restoring with or without that option except it reads the sectors and only writes those that don't already contain a match on the data. Could be something like the need to use the "update boot partition" option.

However, if the drive isn't designed to be reliable, it could cause a problem and you shouldn't use that option. That would occur if the drive returns data in trimmed sectors instead of zeros. Trim is used to tell the drive it doesn't need to read back data before writing new data. If it didn't return zeros consistently and data matched, but then data written to that native block later, it could alter the data (probably to zeros) in other logical sectors. But that would be a flaw in the device, not in the implementation of the option in the program. If you had a drive that did that, then don't use that option.



"giulia" wrote in message news:9829@public.image...

Hi
today i restored an w8.1 Image created 10 days ago with the settings "Write
Changed Sectors Only" with image for windows 2.90 (w8.1 winpe based ) and
when i rebboted my windows 8.1 crashed , it start to boot after it blocked
with an error
0xc000021a
i had to restore the image again without Write Changed Sectors Only , it
works now

i got this
error ->https://neosmart.net/wiki/wp-content/uploads/sites/5/2014/10/0xC000021A-windows-8-8-1.png

i know the last version 2.97

are there some bug fixed between 2.90 to 2.97 related to "Write Changed
Sectors Only"


thanks

[giulia]

TeraByte Support wrote:
> No, it wouldn't have anything to do with that option itself, there is no real
> difference restoring with or without that option except it reads the sectors and only
> writes those that don't already contain a match on the data. Could be something like
> the need to use the "update boot partition" option.
>
> However, if the drive isn't designed to be reliable, it could cause a problem and you
> shouldn't use that option. That would occur if the drive returns data in trimmed
> sectors instead of zeros. Trim is used to tell the drive it doesn't need to read
> back data before writing new data. If it didn't return zeros consistently and data
> matched, but then data written to that native block later, it could alter the data
> (probably to zeros) in other logical sectors. But that would be a flaw in the
> device, not in the implementation of the option in the program. If you had a drive
> that did that, then don't use that option.
>
>
>
> "giulia" wrote in message news:9829@public.image...
>
i did check my drive with several tools , and smart and it's perfect
the drive is a samsung 840 , is there a list of "reliable" drivers ?
i have samsung 840 evo and 850 too

does it matter if i use image for windows or for linux or dos according to " However, if the drive isn't designed to be reliable, it could cause a problem and you
> shouldn't use that option. That would occur if the drive returns data in trimmed
> sectors instead of zeros. Trim is used to tell the drive it doesn't need to read
> back data before writing new data. " ?

or is there a option to try if the drive is "reliable for example check that the restore data is perfect? enbble Validate or VALIDATE byte for byte could be usefull to use with Write Changed Sectors Only and "drive isn't designed to be reliable"

thanks

[TeraByte Support]

It means if the drive read of sector n which is trimmed then that sector
data should remain on any read until it is specifically overwritten. In
short, if the drive supports DRAT (Deterministic read after TRIM) then you
can use that option, if it doesn't, you shouldn't use it. We can look to
disable that option or report that isn't support in an update.

"giulia" wrote in message news:9845@public.image...

TeraByte Support wrote:
> No, it wouldn't have anything to do with that option itself, there is no
> real
> difference restoring with or without that option except it reads the
> sectors and only
> writes those that don't already contain a match on the data. Could be
> something like
> the need to use the "update boot partition" option.
>
> However, if the drive isn't designed to be reliable, it could cause a
> problem and you
> shouldn't use that option. That would occur if the drive returns data in
> trimmed
> sectors instead of zeros. Trim is used to tell the drive it doesn't need
> to read
> back data before writing new data. If it didn't return zeros consistently
> and data
> matched, but then data written to that native block later, it could alter
> the data
> (probably to zeros) in other logical sectors. But that would be a flaw in
> the
> device, not in the implementation of the option in the program. If you
> had a drive
> that did that, then don't use that option.
>
>
>
> "giulia" wrote in message news:9829@public.image...
>
i did check my drive with several tools , and smart and it's perfect
the drive is a samsung 840 , is there a list of "reliable" drivers ?
i have samsung 840 evo and 850 too

does it matter if i use image for windows or for linux or dos according to
" However, if the drive isn't designed to be reliable, it could cause a
problem and you
> shouldn't use that option. That would occur if the drive returns data in
> trimmed
> sectors instead of zeros. Trim is used to tell the drive it doesn't need
> to read
> back data before writing new data. " ?

or is there a option to try if the drive is "reliable for example check
that the restore data is perfect? enbble Validate or VALIDATE byte for byte
could be usefull to use with Write Changed Sectors Only and "drive isn't
designed to be reliable"

thanks

[giulia]

TeraByte Support wrote:
> It means if the drive read of sector n which is trimmed then that sector
> data should remain on any read until it is specifically overwritten. In
> short, if the drive supports DRAT (Deterministic read after TRIM) then you
>
> can use that option, if it doesn't, you shouldn't use it. We can look to
>
> disable that option or report that isn't support in an update.
>
> "giulia" wrote in message news:9845@public.image...
>
> TeraByte Support wrote:
> > No, it wouldn't have anything to do with that option itself, there is no
>
> > real
> > difference restoring with or without that option except it reads the
> > sectors and only
> > writes those that don't already contain a match on the data. Could be
> > something like
> > the need to use the "update boot partition" option.
> >
> > However, if the drive isn't designed to be reliable, it could cause a
> > problem and you
> > shouldn't use that option. That would occur if the drive returns data
> in
> > trimmed
> > sectors instead of zeros. Trim is used to tell the drive it doesn't
> need
> > to read
> > back data before writing new data. If it didn't return zeros
> consistently
> > and data
> > matched, but then data written to that native block later, it could alter
>
Hi ,today a friend of mine restored an image Write Changed Sectors Only ,his os boots (w7) but i has mft errors

could this utility TRIMcheck help ?
why don't add to image for windows or linux a simple test to know if the drive supports
1) Non-deterministic Trim
2) Deterministic Trim (DRAT)
3) Deterministic Read Zero after Trim (DZAT)

would really great and safe!!!

[TeraByte Support]

"giulia" wrote in message news:9852@public.image...

TeraByte Support wrote:
> It means if the drive read of sector n which is trimmed then that sector
> data should remain on any read until it is specifically overwritten. In
> short, if the drive supports DRAT (Deterministic read after TRIM) then you
> can use that option, if it doesn't, you shouldn't use it. We can look to
> disable that option or report that isn't support in an update.
>

> Hi ,today a friend of mine restored an image Write Changed Sectors Only
> ,his os boots (w7) but i has mft errors

That doesn't mean much if there were MFT errors before the backup. Restore
without that option and you'll know if there is a difference.

What drive? Same one, then that may indicate it doesn't support DRAT which
mean's it's not a reliable by design.

[giulia]

TeraByte Support wrote:
> "giulia" wrote in message news:9852@public.image...
>
> TeraByte Support wrote:
> > It means if the drive read of sector n which is trimmed then that sector
> > data should remain on any read until it is specifically overwritten. In
> > short, if the drive supports DRAT (Deterministic read after TRIM) then
> you
> > can use that option, if it doesn't, you shouldn't use it. We can look
> to
> > disable that option or report that isn't support in an update.
> >
>
> > Hi ,today a friend of mine restored an image Write Changed Sectors Only
>
> > ,his os boots (w7) but i has mft errors
>
> That doesn't mean much if there were MFT errors before the backup. Restore
>
> without that option and you'll know if there is a difference.
>
> What drive? Same one, then that may indicate it doesn't support DRAT which
>
> mean's it's not a reliable by design.

yes but the utility can show if the drive supports DRAT
could be added such features ?
a feature in image for windows to test if the drive supports DRAT ?
thanks

[TeraByte Support]

> We can look to disable that option or report that isn't support in an
> update.


"giulia" wrote in message news:9859@public.image...

TeraByte Support wrote:
> "giulia" wrote in message news:9852@public.image...
>
> TeraByte Support wrote:
> > It means if the drive read of sector n which is trimmed then that sector
> > data should remain on any read until it is specifically overwritten. In
> > short, if the drive supports DRAT (Deterministic read after TRIM) then
> you
> > can use that option, if it doesn't, you shouldn't use it. We can look
> to
> > disable that option or report that isn't support in an update.
> >
>
> > Hi ,today a friend of mine restored an image Write Changed Sectors Only
>
> > ,his os boots (w7) but i has mft errors
>
> That doesn't mean much if there were MFT errors before the backup.
> Restore
>
> without that option and you'll know if there is a difference.
>
> What drive? Same one, then that may indicate it doesn't support DRAT
> which
>
> mean's it's not a reliable by design.

yes but the utility can show if the drive supports DRAT
could be added such features ?
a feature in image for windows to test if the drive supports DRAT ?
thanks

[giulia]

TeraByte Support wrote:
> > We can look to disable that option or report that isn't support in an
> > update.

Hi
would be greatif image for windows , linux could do a short test to detect if the drive support DRAT
or included in image for w/l ,the drives that support drat

[TeraByte Support]

That's what this means:
> We can look to disable that option or report that isn't support in an
> update.

"giulia" wrote in message news:9875@public.image...

TeraByte Support wrote:
> > We can look to disable that option or report that isn't support in an
> > update.

Hi
would be greatif image for windows , linux could do a short test to detect
if the drive support DRAT
or included in image for w/l ,the drives that support drat