I'm starting non-system disk defragmentation.
Drive map looks like this:
But near the end, we can observe the following incorrect map:
Defragger v2.10.424(64-bit)
It was also observed in previous versions.
not a great deal of info to go on.
what sort of disk?, is it a solid state?, is it a partition?
first guess would be something as simple as a background running task or something as sexy as wear levelling.
Same thing here. It happens when defragmenting C:\$MFT. Sometimes it's just one messed up screen, other times it's more of them and it looks like it's just trashing all the data on the drive. Fortunately it seems to be only visual glitch. But it got me really worried for the first time.
Here it can be seen in action: http://web.hisoftware.cz/sob/tmp/defraggler-bug.avi (700kB)
Windows 7 x64, regular non-SSD disk.
firstly get the latest v2.11 in the off-chance it performs differently.
then run it with the Stop VSS when defragmenting NTFS volume and Use custom fragmentation settings ticked. in the latter go into Define and tick the boxes to exclude restore points and hibernation file.
are any other programs running while you are defragging; browsers, AV background scan, windows updates?
another thought, go to Settings, Boot Time Defrag and select Run Once.
but if your problem is just with $MFT, I'm not sure yet if Defraggler handles that file.
I do have the latest version, forgot to write that. Running processes, well yes, it's Windows and system drive, there's always something touching it. But nothing intensive. Other settings, maybe. Unfortunately, another thing about this is that it does not happen every time. So it's hard to tell if different settings really helped or if it just didn't happen regardless of them.
Anyway, it seems to be harmless, it just looks really strange. But something somewhere must be wrong. If you watched the video, it's like the whole content of the drive completely changed several times in just few seconds. And not randomly, there are those strangely regular patterns.
Running processes, well yes, it's Windows and system drive
Yes.
What about VSS - did you stop that as suggested ?
I did and the problem does not happen now. Unfortunately it does not say much, because neither it happens now with VSS running. So I can only keep the option checked and see what it does over time. If I don't see the problem for month or so, then it was probably the solution.
fingers crossed... as you say, time will tell.
I know from using DF myself that your drive map 'regular patterns' is also something i've seen before, but from memory, it may have been before a DF (which you'd expect)