TeraByte Unlimited

hi

i have restored several images with the option /wco on several different ssd (write changed sector only)

i used image for windows (last version) winpe based on w8.1 and w10 and image for linux

after the restore the drive did not boot correctly , they crash on boot

i found this issue with sandisk , samsung ,intel 750

could please the team investigate about it?

seeing terabyte is one of the most trustworthy and reliable software around ,the team should investigate about it
there is software (i'm not talking about macrium) that had a very similar approach without issues

thanks

So restoring without /wco works fine?

what version? some drives can't use that option and later versions won't
allow that option.

"giulia" wrote in message news:[email protected]...

hi

i have restored several images with the option /wco on several different ssd
(write changed sector only)

i used image for windows (last version) winpe based on w8.1 and w10 and
image for linux

after the restore the drive did not boot correctly , they crash on boot

i found this issue with sandisk , samsung ,intel 750

could please the team investigate about it?

seeing terabyte is one of the most trustworthy and reliable software around
,the team should investigate about it
there is software (i'm not talking about macrium) that had a very similar
approach without issues

thanks

TeraByte Support wrote:
> what version? some drives can't use that option and later versions won't
>
> allow that option.
>
> "giulia" wrote in message news:[email protected]...
>
> hi
>
> i have restored several images with the option /wco on several different
> ssd
> (write changed sector only)
>
> i used image for windows (last version) winpe based on w8.1 and w10 and
> image for linux
>
> after the restore the drive did not boot correctly , they crash on boot
>
> i found this issue with sandisk , samsung ,intel 750
>
> could please the team investigate about it?
>
> seeing terabyte is one of the most trustworthy and reliable software around
>
> ,the team should investigate about it
> there is software (i'm not talking about macrium) that had a very similar
> approach without issues
>
> thanks
hi
tha last version of course Version 2.98 ifw & ifL , haven't tried image for dos
quote-> some drives can't use that option and later versions won't ,
i know it , but image for windows and linux consider these drives (the drives i have tested) compatible with /wco and enable the option /wco
but after the restore with this option , the result is a disaster

Brian K wrote:
> So restoring without /wco works fine?
hi Brian
yes without /wco the restore work 100%

Then don't use it. If it can't communicate with the drive, the default to
maintain backwards compatibility and compatibly with virtual drives is to
use what the user wants. We can think about changing it, but you can also
see if there is a difference between regular windows install and your pe
disk, if the pe environment doesn't support what is needed to get the
information, then that is the reason.

"giulia" wrote in message news:[email protected]...

TeraByte Support wrote:
> what version? some drives can't use that option and later versions won't
>
> allow that option.
>
> "giulia" wrote in message news:[email protected]...
>
> hi
>
> i have restored several images with the option /wco on several different
> ssd
> (write changed sector only)
>
> i used image for windows (last version) winpe based on w8.1 and w10 and
> image for linux
>
> after the restore the drive did not boot correctly , they crash on boot
>
> i found this issue with sandisk , samsung ,intel 750
>
> could please the team investigate about it?
>
> seeing terabyte is one of the most trustworthy and reliable software
> around
>
> ,the team should investigate about it
> there is software (i'm not talking about macrium) that had a very similar
> approach without issues
>
> thanks
hi
tha last version of course Version 2.98 ifw & ifL , haven't tried image for
dos
quote-> some drives can't use that option and later versions won't ,
i know it , but image for windows and linux consider these drives (the
drives i have tested) compatible with /wco and enable the option /wco
but after the restore with this option , the result is a disaster

we just change the default to no with a way to make the default yes so non
issue going forward.


"TeraByte Support" wrote in message news:[email protected]...

Then don't use it. If it can't communicate with the drive, the default to
maintain backwards compatibility and compatibly with virtual drives is to
use what the user wants. We can think about changing it, but you can also
see if there is a difference between regular windows install and your pe
disk, if the pe environment doesn't support what is needed to get the
information, then that is the reason.

"giulia" wrote in message news:[email protected]...

TeraByte Support wrote:
> what version? some drives can't use that option and later versions won't
>
> allow that option.
>
> "giulia" wrote in message news:[email protected]...
>
> hi
>
> i have restored several images with the option /wco on several different
> ssd
> (write changed sector only)
>
> i used image for windows (last version) winpe based on w8.1 and w10 and
> image for linux
>
> after the restore the drive did not boot correctly , they crash on boot
>
> i found this issue with sandisk , samsung ,intel 750
>
> could please the team investigate about it?
>
> seeing terabyte is one of the most trustworthy and reliable software
> around
>
> ,the team should investigate about it
> there is software (i'm not talking about macrium) that had a very similar
> approach without issues
>
> thanks
hi
tha last version of course Version 2.98 ifw & ifL , haven't tried image for
dos
quote-> some drives can't use that option and later versions won't ,
i know it , but image for windows and linux consider these drives (the
drives i have tested) compatible with /wco and enable the option /wco
but after the restore with this option , the result is a disaster

I'm confused. Even if "Write Changed Sectors Only" is available as an option, that doesn't necessarily mean the drive supports the option? I assumed (probably incorrectly) that recent SSDs supported the option.

TeraByte Support wrote:
> we just change the default to no with a way to make the default yes so non
>
> issue going forward.
>
>
> "TeraByte Support" wrote in message news:[email protected]...
>
> Then don't use it. If it can't communicate with the drive, the default
> to
> maintain backwards compatibility and compatibly with virtual drives is to
> use what the user wants. We can think about changing it, but you can also
> see if there is a difference between regular windows install and your pe
> disk, if the pe environment doesn't support what is needed to get the
> information, then that is the reason.

hi
i understand but why don't you (the team ) investigate and test it on several different ssd brands and models?

The drive either supports DRAT or doesn't. It has to ask the drive to find
out, if your environment (OS version, OS type) doesn't have what is required
to talk to it, then it won't get an answer. The normal environments it's
run in should support returning the data. Note that the change to not
allowing it unless it does talk to it will now mean users with non-ATA or
very old IDE drives will also need to use the new global option /wcoa make
it available.


"giulia" wrote in message news:[email protected]...

TeraByte Support wrote:
> we just change the default to no with a way to make the default yes so non
>
> issue going forward.
>
>
> "TeraByte Support" wrote in message news:[email protected]...
>
> Then don't use it. If it can't communicate with the drive, the default
> to
> maintain backwards compatibility and compatibly with virtual drives is to
> use what the user wants. We can think about changing it, but you can also
> see if there is a difference between regular windows install and your pe
> disk, if the pe environment doesn't support what is needed to get the
> information, then that is the reason.

hi
i understand but why don't you (the team ) investigate and test it on
several different ssd brands and models?