Sunday morning is when I plug an HDD into the dock on my NAS and copy my drive images made in the wee hours from my NAS (where Robocopy had duplicated them from my daily driver) to the first of the two HDDs for offline storage. The images from my dual boot daily driver were there, but my NAS image (normally created by Task Scheduler) was not.
So to speed up the process, I decided to just run IFW on my NAS for the image transfer, and troubleshoot the reason it was missing later. But I got a failure on the byte-for-byte verification. So I opened an elevated Command Prompt, ran
dism /online /cleanup-image /restorehealth
dism /online /cleanup-image /startcomponentcleanup /resetbase
one at a time, then sfc /scannow. Everything was successful, no corrupt files found.
Tried again for a NAS image, same failure. I opened Samsung Magician just to check the mSATA SSD status, and it is still good, only 12.4 TB written. After a few minutes of contemplation, knowing that IFW uses a bit of RAM on the verification process, I asked myself what else is using RAM concurrently? Samsung Magician Rapid Status uses a portion of RAM for caching to create Rapid Status.
On a whim, I disabled Rapid Status, tried creating an IFW image again, and it completed successfully. I may run some comparison tests later on this week, but I think I’ve found my issue.
