![]() ![]() ![]() Running Verify disk indeed indicates it is now clean. Verify Disk indicates that I *do* have errors on the drive – so I run Repair Disk and fix the errors. So out comes the Mac OSX disk and boot into Disk Utility. After I look for a few pages beyond the first few pages, I start to see mentions of “Repair Disk” and “fsck -fy” – then it dawned on me – that long pause when it was partitioning might have been a disk check. So that was *not* the problem – I had about 150GB free and empty and perfectly defrayed at the end of my 200GB drive and yet:Īargh. It automatically gets cleaned up when it boots back into Mac OS/X. Then I went into iDefrag in normal Mac OS mode, and the file was not there. Then I looked at the files using the iDefrag UI and they were: So back to defrag and when I redefragged again the files were still there. I was distracted by a little red herring of a band of “red fragmented” files that were left at the end of the drive and I guessed that they might be the problem. I did have to adjust the minimum temperature to restart the process to 52 degrees so the drive ranges between 52 and 55 degrees – but with the fan going, I don’t think it stopped for heat after I put the fan behind my iMac.Īfter defrag completed, I reboot and tried to create the Windows partition using Boot Camp Assistant and again after a long period of time, I got the The drive heated up and so I aimed a fan at the back of my iMac to keep it cool. So I rebooted into defrag mode and did a full defray. It nicely does not need to make a boot disk. So I messed around for a while and decided to by the latest iDefrag2. So I popped the iDefrag disk and booted – it worked, but not all of the options seemed functional. I even had a boot disk that I had saved from long ago in 2007. It turns out I had purchased iDefrag 1.x back in 2007 and throught it was a pretty cool product – I like nice clean disk space with files that have all their data in one place so I like defraggers. ![]() I did some goggling and came up with this discussion forum: At this point, I wish I tried booting my OSX drive and running verify/repair and see if that fixes the problem. Urg, I just had a partition there – and so there was plenty of free space. When I got to the part where it was going to re-create the Windows partition, using Boot Camp Assistant and after it took a long time with no explanation of what it was doing I got the following dreaded message:īootcamp Partition Error: “Files cannot be moved” This just does not work (per lots of forum posts) so I properly indicated that I had all of the drivers. My first problem is that I followed directions and selected:ĭownload Windows support software for this Mac Then I wanted to re-create the Windows Partition in Boot Camp Assistant. So first I deleted the Windows Partition in Boot Camp Assistant, worked perfectly. That seemed like the most upright thing to do. My first instinct wanted to simply insert the Windows 7 disk and reboot and install a fresh install on the existing partition – some day when I am bored, I might try that and see what goes wrong – but this time I figured I would delete and recreate the partition through Boot Camp Assistant on the MacOS side. Live and Learn Moment: I should also have rebooted off my Snow Leopard drive, run disk utility and repair/verify my iMac boot partition before starting. But of course you know that once you open things up, things can go wrong and it always takes longer than you expect.įirst of course, back up the user data from Windows Vista and get TimeMachine up-to-date in case it all fails. ![]() The Windows Vista was just too unreliable and I heard a lot of good things about Windows 7. The time had finally come for me to switch my BootCamp partition on my iMac to Windows 7. ![]()
0 Comments
Leave a Reply. |