jerbare
16th March 2006, 10:13 PM
[edit - title is supposed to be OVERRIDES, heh...]
I was beginning to start working on a solution for attempting to boot Windows XP off of an external disk instead of burning discs. I dumped a copy of the xom.efi file on my the external to play with, loaded up the EFI console and selected it to boot from. I saw some nice debug output from it and it froze due to no floppy.img being present...
No worries, so I boot back in to Mac OS X.
Woops, there go all of my extra partitions! I had 4 regular partitions (5 counting the EFI partition). Looks like xom.efi writes an MBR to the internal disk, regardless of where you boot it from... The problem is that there are more than the 4 primary partitions that an FDISK partition scheme can handle... Understandable...
So I go to Disk Utility. It only saw the main Mac OS X partition. I open up a console and check out the status of gpt:
sudo gpt -r show /dev/disk0
Good deal. With GPT you dont have much to worry about, because it actually has a primary and a secondary backup of the partition table - one at the beginning and one at the end.
So I figure I'll boot off of the Installer DVD, ensure thats the case and zero out the first 512 bytes on the hard drive. They shouldn't mean squat from the GUID Partition Scheme according to the spec. If the first 512 bytes of the disk are empty, I figured Mac OS X would check for the GPT, and recognize the disk... So I pop open a terminal and decide to zero out the first 512 bytes...
dd if=/dev/zero of=/dev/rdisk0 bs=512 count=1
Sure enough, as SOON as I hit enter I think 'Hmm... I should have probably wrote a backup of that to the Firewire disk...'
Quit the terminal, open Disk Utility. No partitions - the disk is empty.
Okay, figure it will take a reboot for the kernel to reinitialize the disk and scan for the GPT in either location...
WRONG.
It appears Apple is writing SOMETHING to the first 512 bytes of the disk in order to flag Mac OS X that the disk is GPT. Sure enough I have some data fairly useful data on the disk I would VERY MUCH like to NOT LOSE. Heh... Silly me...
I checked the status of gpt again after all of this, and it VERY MUCH appears to show the partition tables intact. The disk looks fine. However, Disk Utility nor /dev show any partitions for disk0.
Can somebody who hasn't run xom.efi on their intel Mac do me a BIG favor and hook me up with the first 512 bytes of their HD? It should be pretty simple, and I'm not sure if you'll be able to write to the same HD - but an external or USB jump drive should work.
This is a 20" iMac Core Duo with the 250gb - but I'm willing to try anything...
Just boot off of the Install Disk and open up Terminal from the menu. Run this after finding a place to write to:
dd if=/dev/rdisk0 of=/Volumes/SOMETHING/help.bin bs=512 count=1
This is going to read the first 512 bytes off the GPT disk and write them to a file called help.bin. If you can then hook me up with this I would greatly appreciate it.
I was beginning to start working on a solution for attempting to boot Windows XP off of an external disk instead of burning discs. I dumped a copy of the xom.efi file on my the external to play with, loaded up the EFI console and selected it to boot from. I saw some nice debug output from it and it froze due to no floppy.img being present...
No worries, so I boot back in to Mac OS X.
Woops, there go all of my extra partitions! I had 4 regular partitions (5 counting the EFI partition). Looks like xom.efi writes an MBR to the internal disk, regardless of where you boot it from... The problem is that there are more than the 4 primary partitions that an FDISK partition scheme can handle... Understandable...
So I go to Disk Utility. It only saw the main Mac OS X partition. I open up a console and check out the status of gpt:
sudo gpt -r show /dev/disk0
Good deal. With GPT you dont have much to worry about, because it actually has a primary and a secondary backup of the partition table - one at the beginning and one at the end.
So I figure I'll boot off of the Installer DVD, ensure thats the case and zero out the first 512 bytes on the hard drive. They shouldn't mean squat from the GUID Partition Scheme according to the spec. If the first 512 bytes of the disk are empty, I figured Mac OS X would check for the GPT, and recognize the disk... So I pop open a terminal and decide to zero out the first 512 bytes...
dd if=/dev/zero of=/dev/rdisk0 bs=512 count=1
Sure enough, as SOON as I hit enter I think 'Hmm... I should have probably wrote a backup of that to the Firewire disk...'
Quit the terminal, open Disk Utility. No partitions - the disk is empty.
Okay, figure it will take a reboot for the kernel to reinitialize the disk and scan for the GPT in either location...
WRONG.
It appears Apple is writing SOMETHING to the first 512 bytes of the disk in order to flag Mac OS X that the disk is GPT. Sure enough I have some data fairly useful data on the disk I would VERY MUCH like to NOT LOSE. Heh... Silly me...
I checked the status of gpt again after all of this, and it VERY MUCH appears to show the partition tables intact. The disk looks fine. However, Disk Utility nor /dev show any partitions for disk0.
Can somebody who hasn't run xom.efi on their intel Mac do me a BIG favor and hook me up with the first 512 bytes of their HD? It should be pretty simple, and I'm not sure if you'll be able to write to the same HD - but an external or USB jump drive should work.
This is a 20" iMac Core Duo with the 250gb - but I'm willing to try anything...
Just boot off of the Install Disk and open up Terminal from the menu. Run this after finding a place to write to:
dd if=/dev/rdisk0 of=/Volumes/SOMETHING/help.bin bs=512 count=1
This is going to read the first 512 bytes off the GPT disk and write them to a file called help.bin. If you can then hook me up with this I would greatly appreciate it.