Boot Camp Partition Freeze
Hey guys. I'm trying to partition my HD on my 2.4 ghz MBP to install XP, however every time I click partition, it will go for a few minutes and then all of a sudden the screen dims from top to bottom and a message comes up in multiple languages forcing me to make a hard restart with the power button. I then have to boot from the Leopard cd to repair the disk bc it shows the 5 gigs deducted from my HD even though the partition failed. I have no problem repairing it, but why is this happening in the first place? I've searched the web on this and the only thing I could find was to do a complete erase and install. I really don't want to have to do that. Has this happened to any of you? Anyone know what I can do?
Thanks guys.
Thanks guys.
Comments
http://www.macosxhints.com/article.p...71101065229169
What I would do is clone the system you have to an external drive. Then partition using the method described and then clone it back to the Mac partition.
You don't need to use Bootcamp to start the installer for Windows either, it should boot from the disc directly.
I would aim for more than a 5GB partition though. XP takes up 2.5GB and your VM file takes up about 1.5GB leaving you 1GB to use for apps. I personally use 10GB and although I have run out of space on occasions, I find it to be a decent size.
Remember, you can use this space from the Mac side too so it's not wasted space so long as you format as MS-DOS.
I'm pretty po'ed about this. I haven't done anything to my computer out of the ordinary besides upgrade the RAM to 4 gb. Pretty crazy.
Thanks for the response. Can I clone my drive just by using my Time Machine backup drive?
If it mounts as a normal drive then you should be able to but it could take a while depending on what's on your system. On average it takes about 1 minute per GB. It's a lot to do with the number of files rather than size though. Typically systems have in excess of 200,000 files. The process generally speeds up as it goes on.
Time Machine is great for no wires, background backups but for a quick backup, a USB 2 or firewire drive will be so much quicker - 240MBits/s vs 75MBits/s, average real world speeds. You can leave it overnight or if you are out during the day so you don't have to wait on it.
Use Carbon Copy Cloner (free) or Superduper (free for cloning but not clone updating) to do the cloning. Check Leopard compatibility first. Superduper had some issue with Leopard but they might be fixed.
I'm pretty po'ed about this. I haven't done anything to my computer out of the ordinary besides upgrade the RAM to 4 gb. Pretty crazy.
Bootcamp isn't the best of tools. On every machine I used, I had the errors about not being able to partition and I had to a clone, erase, clone to get it to work. That was the beta version on Tiger though so I would have expected the Leopard one to work.
The grey screen you got was a kernel panic btw, if you check your /Library/logs/ folder (not the one in the users folder), there should be a panic.log file that may give some info about what went wrong.
If it mounts as a normal drive then you should be able to but it could take a while depending on what's on your system. On average it takes about 1 minute per GB. It's a lot to do with the number of files rather than size though. Typically systems have in excess of 200,000 files. The process generally speeds up as it goes on.
Time Machine is great for no wires, background backups but for a quick backup, a USB 2 or firewire drive will be so much quicker - 240MBits/s vs 75MBits/s, average real world speeds. You can leave it overnight or if you are out during the day so you don't have to wait on it.
Use Carbon Copy Cloner (free) or Superduper (free for cloning but not clone updating) to do the cloning. Check Leopard compatibility first. Superduper had some issue with Leopard but they might be fixed.
Bootcamp isn't the best of tools. On every machine I used, I had the errors about not being able to partition and I had to a clone, erase, clone to get it to work. That was the beta version on Tiger though so I would have expected the Leopard one to work.
The grey screen you got was a kernel panic btw, if you check your /Library/logs/ folder (not the one in the users folder), there should be a panic.log file that may give some info about what went wrong.
Thanks. I really appreciate your response.
Here is my panic.log
Fri Jun 15 17:57:50 2007
panic(cpu 0 caller 0x001A4A55): Unresolved kernel trap (CPU 0, Type 14=page fault), registers:
CR0: 0x8001003b, CR2: 0x3e8b5ec8, CR3: 0x0188e000, CR4: 0x000006e0
EAX: 0x00a8a800, EBX: 0x0040cbe1, ECX: 0x00a8a8a8, EDX: 0x0000a800
CR2: 0x3e8b5ec8, EBP: 0x25e93b58, ESI: 0x3e8b5ec8, EDI: 0x00000006
EFL: 0x00010002, EIP: 0x0037ee27, CS: 0x00000008, DS: 0x00000010
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x25e93888 : 0x128d08 (0x3cc224 0x25e938ac 0x131de5 0x0)
0x25e938c8 : 0x1a4a55 (0x3d2638 0x0 0xe 0x3d1e5c)
0x25e939d8 : 0x19aeb4 (0x25e939f0 0x0 0x25e93a08 0x131d98)
0x25e93b58 : 0x37f2ed (0x109380 0x3e433000 0x0 0xa)
0x25e93c18 : 0x1ac351 (0x3d35c8 0x1 0x0 0x120)
0x25e93c48 : 0x35eef3ce (0x35eef1ae 0x3 0x35f20160 0x0)
0x25e93ca8 : 0x35ee4446 (0x4467600 0x2 0x25e93c7c 0x4c26460)
0x25e93cc8 : 0x3abf47 (0x45e2d80 0x4b063c 0x3 0x4b0000)
0x25e93d08 : 0x3bb2f2 (0x4467600 0x3f21d4 0x44c0148 0x391c89)
0x25e93d48 : 0x394663 (0x44c6f00 0x4 0x1d 0x2)
0x25e93d88 : 0x394b99 (0x44c6f00 0x0 0x25e93dc8 0x0)
0x25e93da8 : 0x395a78 (0x44c6f00 0x43e2c00 0xb 0x1)
0x25e93de8 : 0x394bc2 (0x44c6f00 0x4637980 0x25e93e28 0x0)
0x25e93e08 : 0x395a78 (0x4637d00 0x43e2c00 0xb 0x1)
0x25e93e48 : 0x394bc2 (0x4637d00 0x4637c00 0x25e93e88 0x0)
0x25e93e68 : 0x395a78 (0x467f180 0x43e2c00 0xb 0x1) \tBacktrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x35ee3 000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35e79000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x35e8f000
Kernel version:
Darwin Kernel Version 8.9.4: Thu May 17 18:04:27 PDT 2007; root:xnu-792.20.12~1/RELEASE_I386
*********
-----------------------------
Does this tell you anything?
Thanks again,
Justin
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleACPIPlatform(1.0.10)@0x35ee3 000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x35e79000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x35e8f000
Does this tell you anything?
The most helpful part is the loaded modules but they only usually help when it's something that isn't related to what you thought it was. For example, if it was to do with a wireless driver or USB driver then you would unplug external devices. Given that you had a drive problem, an iokit panic is to be expected.
Apple have a technote on how to debug them:
http://developer.apple.com/technotes/tn2002/tn2063.html
Now we just need one to debug the technote.
Other people have come across the same issue in Leopard 10.5.2 so you shouldn't worry that it's a machine specific problem:
http://www.macwindows.com/bootcamp.html#021808f
Defragging like what was required under Tiger seems to be the way to go. A clone, format, clone is equivalent to a defrag. I prefer to do it that way because it means not leaving a defrag app running on the only working copy of the system, plus I've found defrag apps take a while and they don't always defrag fully.
But either way should work and iDefrag may be easier - plus you are backed up via Time Machine so it shouldn't be a worry if something goes wrong during defragging (unlikely to happen anyway).
The most helpful part is the loaded modules but they only usually help when it's something that isn't related to what you thought it was. For example, if it was to do with a wireless driver or USB driver then you would unplug external devices. Given that you had a drive problem, an iokit panic is to be expected.
Apple have a technote on how to debug them:
http://developer.apple.com/technotes/tn2002/tn2063.html
Now we just need one to debug the technote.
Other people have come across the same issue in Leopard 10.5.2 so you shouldn't worry that it's a machine specific problem:
http://www.macwindows.com/bootcamp.html#021808f
Defragging like what was required under Tiger seems to be the way to go. A clone, format, clone is equivalent to a defrag. I prefer to do it that way because it means not leaving a defrag app running on the only working copy of the system, plus I've found defrag apps take a while and they don't always defrag fully.
But either way should work and iDefrag may be easier - plus you are backed up via Time Machine so it shouldn't be a worry if something goes wrong during defragging (unlikely to happen anyway).
Well, I booted from my Time Machine backup drive (which is still running Tiger 10.4.10 btw, don't know if that's supposed to be the case) and ran iDefrag in "compact" mode on my main internal Leopard drive. It WORKED! I'm up and running on XP as type.
Thanks for the help!
You're always there when we need you.
Marvin,
You're always there when we need you.
+1