A different way of looking at what was done. Starting with... [MSR][20000][20000][20000][40000] Code: [MSR][10000] 10000 [20000][20000][40000] resize 2 [MSR][10000] 10000 [20000][20000][15000] 25000 resize 5 [MSR][10000] 10000 [20000][20000] 25000 [15000] slide 5 to right [MSR][10000][20000] 10000 [20000] 25000 [15000] slide 3 to left [MSR][10000][20000] 10000 [40000] 500 [15000] resize 4 [MSR][10000][20000] 15000 [40000][15000] slide 4 to right [MSR][10000][35000][40000][15000] resize 3
Right?!? Using the below, my imaging speeds have improved by 3x. Why this isn't default I'll never know. PerfOpt=1 IOBS=262144 IOCacheFlags=0
@n8chavez - well the Terabyte Support staff themselves STATED that using those tweaks on many Systems cause them to be slower, in fact slower on most of the machines they've tested (probably reason it's not DEFAULT). Be careful... PS: you mentioned on the IFW Forum that it was PerfOpt=0 that gave you the 3x... did =1 do the same, and do you even know what that option does ?
Of course I do. PerfOpt=0 disables caching. Poor little froggy. How easily you underestimate. From the ifw manual: /po:n or PerfOpt=n This option is used to manually control various file caching options of Image for Windows and Windows itself. The settings can have an impact on the overall performance and can be used to fix some driver-based problems as well. The values for n can be as follows and combined using addition: 0 Disable default cache 0 Disable default cache settings used by Image for Windows 1 Disable Windows cache on writes 2 Disable Windows cache on reads 16 Disable write cache on removable drives (only applies if 257 not used) 32 Use smallest alignment 64 Image for Windows will determine if write cache is disabled on removable drives (only applies if 257 not used) 128 Use overlapped IO 257 Use Windows cache on writes 514 Use Windows cache on reads 1028 Use small write cache on backup 2056 Use small write cache on restore 4096 Direct to disk (no disk caching)
In my main computer, the third set of options speed up my backups by 10 to 20%. The same options have no effect in my second computer.
[OPTIONS] PerfOpt=0 IOBS=262144 IOCacheFlags=0 You need to try all three from the TeraByte post to see if any work for you.
My mate has a Dell computer with 2 Hard Drives and a M.2 NVMe PCIe drive. It is a MBR system. A Win8.1 image (from another computer) was restored to the M.2 drive. After some messing around it booted into Windows. He then tried to install Win11 to a partition on the the M.2 drive. The Microsoft installer said he couldn't use that partition. There was a 0x.... code. He tried another partition. Same error. Any thoughts so far?
If the W11 installation media was built as an UEFI-only installer, maybe the W8.1 was an MBR configuration when restored. If so, any attempted UEFI install of W11 might fail if made to a partition on a Legacy-MBR disk (the M.2 that W8.1 is installed on)... just a guess.
TRF, thanks for the reply. More info. The original computer was a UEFI system with Win10. Around 5 years old and his daughter's computer. The M.2 and 2 HDs were GPT disks. My mate wanted a MBR system. The Win8.1 on his other computer was in a MBR system. An entire drive image was created of the M.2 drive. To be used later. All partitions on the M.2 drive were deleted and the drive was converted to a MBR disk. An 80 GB NTFS partition was created for the future Win11. On the M.2 drive. BootIt Bare Metal was installed to be ready for a future multi-boot. The 2 HDs remained as GPT disks. The UFD contained Win11 Iot Enterprise LTSC. Created with Rufus in MBR mode. As I mentioned, the Win11 installer would not allow the NTFS partition to be be used for the Win11 install. We looked up the 0x... error and someone said try the install with the 2 HDs disconnected. We tried that and Win11 installed and ran well. After 30 minutes of playing with Win11, the 2 HDs were reconnected. Win11 failed to boot. The immediate error was something like "Disk error. Press Ctrl, Alt, Del to restart". Unfortunately, I didn't take notes as I was overconfident everything would be fixed in ten minutes. 5 hours later it was fixed. The 2 HDs were disconnected and Win11 booted. The 2 HDs were reconnected and Win11 failed to boot. The 2 HDs were disconnected and another Win11 was installed, same situation. Thoughts?
I was able to install Win10 and have it run while the 2 HDs were connected. But Win11 wouldn't boot while the 2 HDs were connected. Sorry, no notes and I only remember some of what happened.
At this stage I was considering hardware issues. In the BIOS, the SATA Controller was in RAID mode. A favourite of Dell. AHCI drivers were installed into the offline Win11. The SATA controller was changed to AHCI mode. The problem was fixed. Win11 now booted with the 2 HDs connected. It took a long time to get the answer. Next, my mate's daughter wanted her OS on the M.2 drive too. Her Win10 had been installed in UEFI mode and the computer was now a MBR system. We had a image of the 4 Win10 partitions. MSR, ESP, Win10, RE. The Win10 partition (only) was restored to the M.2 drive. It failed to boot, as expected. AHCI drivers were installed and a BCD was created in the offline Win10 partition. Using TBOSDT. Remember, the Win10 ESP previously contained the BCD in her UEFI system. Win10 now booted. The current OS are... Win8.1 Two Win11 Win10 All running nicely from the M.2 drive.
Great job, Brian... good sleuthing! To this date I don't know why DELL is so hung up on baseline RAID configurations, they cause more probs than they're worth. Time for a mug of good brew
Wow.. wow..wow Getting very granular The way The Terabyte suite can be used in the right hands !! Such a fantastic tool !!
