You don't have to do a restore to see if it is excluded. Use TBWinPE, IFL or IFD. Is Write Changed Sectors Only in your Options? I don't understand why you are worried. You don't have to select Write Changed Sectors Only if you don't want to.
Brian , i haven't still updated to 2.97a so i can't know it i would like to use Write Changed Sectors Only ,so i wait to have the update PS. would be interesting if some users post their ssd and if the program detect them as able to use drat feature
mantra, I suspect "Write Changed Sectors Only" will be missing (or greyed out) in your Options list. SSD which don't support DRAT will be prevented from choosing "Write Changed Sectors Only".
I just installed a 128 GB SanDisk SSD in my test computer. It will experience lots of writes as several different OS images will be restored daily. I've noticed a "Write Changed Sectors Only" restore is faster than a standard restore. It completes in 70% of the time of the standard restore.
hi but the option is the Write Changed Sectors option in the gereral preferences or in the restore preferences in 2.97a?
hi Brian update image for windows 2.97a and for linux but the terabyte support is a joke well for the drive that gave me everytime issue using Write Changed Sectors is present and so for terabyte team it should work for the 850 Evo , i know it support drat(i recevied an email ) Write Changed Sectors is not present ,i can't enable , for terabyte team it doesn't support drat , the drive never get an error using Write Changed Sectors with 2.97 about 840 Evo , with the old firmware for terabyte it supports drat , with the last firmware https://www.wilderssecurity.com/thre...low-down-with-time.377593/page-2#post-2503951 is not present so disabled
mantra, That is confusing. Can you post your findings in the TeraByte Forum? There must be something other than DRAT that is blocking Write Changed Sectors Only.
I'm not sure this is applicable, but... as I've mentioned in another post, there are (3) different types of TRIM supported among SSD devices... DRAT (Deterministic READ after TRIM <same data all the time but not the original and not ZERO>), DZAT (Deterministic ZERO after TRIM <always set to ZERO data value after TRIM>) and non-Deterministic TRIM (different data value every time but never the original data). This information is offered any application who uses the Windows DEVICE DISCOVERY API. Possibly IFW is only supporting DZAT or DRAT but not both...?? It's a tough job for IFW since I don't believe it uses the FileSystem information (I'm not sure about this) to determine where the changes actually are... I think it compares data blocks. If that's the case then WRITE CHANGED SECTORs could be a TOUGH job for IFW with SSDs. Thinking about it, though... if it is using DATA (allocated in the FileSystem) for the comparison for changes rather than the FileSystem itself, it should still be able to work OK (not enough coffee yet so this may be spoken in an early morning fog )
hi nope , i'm tired of terabyte forum seem they don't like if i report issues and they are not very eloquent Brian , do you what i was thinking? why don't you write (when you have time) a tutorial about bibm and multiboot (pinned in this forum) for example , install several os on the same disk or install another os (w10) on a disk with a main os installed(with w8.1 installed )
Hi TheRollbackFrog do you use image for windows/linux ? Write Changed Sectors Only always enabled? sadly i guess it's the only software that have such feature,isn't it thanks
Sorry, Mantra... I haven't used it for anything other than FULL partition images since I started using a SSD as my main System disk.
Mantra, I think Peter is referring to Macrium's RAPID DATA RESTORE feature in v6 which only restores CHANGED SECTORS from image to image... exactly what AX64 has been trying to do for almost 2-1/2 years.
Hi mantra, samsung 800 series have been found to have problems with trim command https://github.com/torvalds/linux/commit/9a9324d3969678d44b330e1230ad2c8ae67acf81 instead of being pissed off with terabyteunlimited, you should be thankfull that "write changed sectors" is disabled for your drives. Panagiotis
Agreed. Samsung SSDs (EVO series) use inferior TLC NAND. They are good at marketing, so a lot of people buy their SSDs. I believe in Terabyte Unlimited's judgement. In general, I don't think using "write changed sectors only" option is good for SSDs. For now the best bet is to use whole disk image backup/resotre on SSDs.
I also use Entire Drive image/restores on my test SSD. Write Changed Sectors Only is used for restores on my SSDs but if you are only going to do occasional restores it will make no difference to the lifespan of the SSD. I'm more concerned with the SSD in my test computer. When using Write Changed Sectors Only there are only a few hundred MB of Writes each day. Not using Write Changed Sectors Only results in 100 GB of writes each day. That is a big difference. Write Changed Sectors Only makes no difference to restore times when restoring a full image. When restoring a differential image, Write Changed Sectors Only is faster than not using it. Not massively but enough to notice. mantra, I thought TeraByte Support handled your issue well. They released an IFW update especially for your situation. As Panagiotis indicated, having Write Changed Sectors Only disabled in your Options is to your advantage as your SSD can't cope with Write Changed Sectors Only. You can run TRIM from your IFL boot disk. It works on partitions and unallocated free space.
hi but is there an image program that can check if the restoring process writes data correctly ? i mean for example a drive could be faulty ,or the restore data could be write not correcly thanks @TheRollbackFrog and @pandlouk for the information @TheRollbackFrog would like to test such feature and compare with terabyte @Brian K , hi from where can i run trim? from partition tools?
Validate Byte-for-Byte does this. From Work with Partitions (Partition Work) on the IFL gui. You will need a BIBM serial number.
Hi Brian really? i will try to test it with 2.77 (not a) with Write Changed Sectors Only to see if it works in the terabyt forum they say it's unless validate byte for byte may i ask you why should i use trim from image for linux or bibm ? thanks Brian always present!
TRIM in IFL.... Just an observation in view of Panagiotis' comment: I'd expect your Write Changed Sectors Only restore will fail on Validate Byte-for-Byte.
Really like the WinPE builder. It even support the latest Windows ADK 10 (Install ADK 10 and manually select the path in the settings section of the builder, otherwise it will default to whatever lower ADK version you have installed ( 8.1, 8, etc.). Also, I like the ability to adjust the resolution and dpi of the WinPE media.