If anyone else has any information on this problem, please post what you know so the rest of us can benefit. Second, I don't want to get into a debate about whether or not the OSX system drive should or should not be defragmented. I come from the school of thought that says the deleting and writing of new files to the system drive will, over time, fragment a hard drive. The OS may delay that process with its own optimizations but all hard drives fragment over time when used as the system drive. Now, I purchased a copy of iDefrag originally for my iMac G5 and when I got my MBP, I installed it there as well. In December, iDefrag optimized my MBP's Macintosh HD without a problem. When I did it again in March, the MBP crashed and I had to do a reboot. When I tried it again, it hung part way through and went no further. I emailed Coriolis' tech support and they had me go through some troubleshooting procedures and last night, I was able to get iDefrag to properly defrag my system drive again. The solution was to enter a new boolean parameter in iDefrag's plist file called disableThermalMonitorCompletely and the program ran fine. I did purchase several other hard disk performance programs to see if they would report any problems as well. The programs I purchased was Drive Genius, Disk Warrior and Check it. None of these programs ever reported any problems with my system drive and I used them to verify the drive's disk structure as well as media surface since iDefrag's error logs showed corrupted disk sectors. No problems we ever found and as it turned out, that wasn't the issue. The problem is that for some reason, OSX isn't returning the temperature of the internal system drive properly. iDefrag keeps track of the drive temperature since it's working it so hard during optimization. At present, there are only one other report to Coriolis of this problem and disabling temperature monitoring has stopped iDefrag from crashing. Since I'm sure that more the two MBP owners use iDefrag, and if this was a problem with OSX, then there would be many more reports. So, it appears that the problem is most likely a problem with the hard drive temperature sensor. Coriolis has forwarded a report to Apple making them aware of the problem and has suggested that I do the same. I will contact Apple on this as well and since I have Applecare, I'm not too concerned about this. I must also point out that my MBP works just fine. ![]() I have partitioned my system hard drive with Boot Camp and am running XP Pro on it without any problems. I also have recent, valid backups of my system drive so if there is a sudden failure, my data loss will be minimal. What's going to happen with this? I suspect that this system drive will work fine until other, weird problems start cropping up or it will die suddenly (This sudden failure of the system drive did occur with my iMac right after I purchased it). Apple will replace it and my problem will go away, or I will, at a later date, decide I need a larger system hard drive and replace it myself. My MBP is a GREAT machine and this is just a little hiccup with the hard drive.įinally, if anyone has anything further to add about iDefrag or Apple MBP hard drives relating to this issue, the rest of us are all ears.First, I would like to say the Coriolis' iDefrag is a fine program and it works well on both my MBP and iMac G5. ![]() ![]() This posting is to share my experiences with iDefrag and my MBP and what has been determined to be the problem.
0 Comments
Leave a Reply. |