Physical (rotating platter) hard drive defragmentation sessions can cause the drive being defragmented to become excessively hot, this is an undeniable fact. for larger and heavily fragmented drives, a complete defragmentation and/or optimization could take hours, subjecting the drive to long periods of excessive overheating, resulting in S.M.A.R.T. warnings and early drive failure. Why is it that drive defragmentation applications do not have such a simple yet important cool down feature?
Incorporate default settings that stop drive read/write activities after a set amount of defragment (or optimization) time, 15 minutes for example. After the default defrag time interval, there would be a cool down period, let's say 5 minutes. After the cool down period defragmentation would continue for another 15 minutes. This defrag/cool down cycle would continue until the defragmentation (or optimization) process has completed. It would be desirable to have user configurable settings for both the active defrag time as well as the cool down time.
Another option might be to have the application stop drive read/write activities when the hard drive S.M.A.R.T. temperature reaches a certain level, then resume when the drive temperature drops below a target temperature. This defrag/cool down cycle would continue until the defragmentation (or optimization) process has completed. it would be desirable to have user configurable settings for both the peak (cutoff) temperature as well as the cool down target temperature.
UltraDefrag seems to be a thought out, well designed utility, I would think that adding such a unique and vital cool down feature to your defragment application would make it more appealing to customers.
Any thoughts, feedback, or suggestions are most welcome.
Thanks for considering,