I ran defraggler a few times, but it always spent a long, long time. I thought this may be normal so I let it run. I now understand that my hard drive has a corrupted sector, and I think Defraggler was treating it as a normal one. Allowing Defraggler to run like this very nearly caused me to have to re-install my operating system.
Until this issue is addressed I simply can't allow myself to defraggle my hard drive.
There have been a couple of releases since the version I was using. I don't suppose that the issue has been sorted?
I ran defraggler a few times, but it always spent a long, long time. I thought this may be normal so I let it run. I now understand that my hard drive has a corrupted sector, and I think Defraggler was treating it as a normal one. Allowing Defraggler to run like this very nearly caused me to have to re-install my operating system.
Until this issue is addressed I simply can't allow myself to defraggle my hard drive.
There have been a couple of releases since the version I was using. I don't suppose that the issue has been sorted?
I would like to join to your question.
I had the same problem since version dfsetup109.exe or dfsetup108.exe.
Since then every time I perform a defrag for my disk, I have to do check disk completely for the drive otherwise it will not be detected on the next boot time ( chkdsk /f /v /r /i /c ).
Can anyone for Piriform have a solution for this issue ????
I don't know, but I think it would be a good idea (especially since I believe the bad sectors are already marked by check disk). Otherwise the de-fragmenter will attempt to write to these sectors.
The issue you have described is unlikely to be caused by Defraggler. For moving the files Defraggler uses Windows API calls and what is more important all data about the disk is taken from the operating system, so it is perfectly safe to use. The problem of bad clusters is handled by Windows and it is transparent for Defraggler. So as long as NTFS itself is aware of the bad cluster there will be no problems.
It is a very good practice though, to run chkdsk before the defrag. Especially if you have a faulty disk or you perform risky activities such as powering off the machine while it is working.
The issue you have described is unlikely to be caused by Defraggler. For moving the files Defraggler uses Windows API calls and what is more important all data about the disk is taken from the operating system, so it is perfectly safe to use. The problem of bad clusters is handled by Windows and it is transparent for Defraggler. So as long as NTFS itself is aware of the bad cluster there will be no problems.
It is a very good practice though, to run chkdsk before the defrag. Especially if you have a faulty disk or you perform risky activities such as powering off the machine while it is working.