Voodooprojects
Chameleon => General Discussion => Topic started by: rimmi2002 on September 04, 2010, 06:49:18 PM
-
I had a perfect working retail install of Snow Leopard and Win7. I have reinstalled Win 7 multiple times and had to do it one more time. I did it and used by USB stick to boot into OSX to restore chameleon as boot loader. In the past it has never been a problem. Now however the chameleon instructions were not working. I noticed that my MAC DISK is no longer GUID Parition. It is now Fdisk? How did it loose it's GUID TABLE?
Attached below is a screen shot from diskutility with my attempt at using fdisk440 and it failing. OSX disk is Disk 1.Please advise if there is any way to reverse this. THanks.
About the only thing I did different this time compared to last time was that I installed Acronisc true image back up home plus on win7 and made a copy of the my win7 parition. I am not sure if that messed things up or something else, but I am not sure how a GUID parition changed to a Fdisk. Makes no sense to me.
Any help will be appreciated. tHanks.
-
You're not even doing it right. You're not even running fdisk440. cd to your i386 folder of chameleon and type
./fdisk440 -f boot0 -u -y /dev/rdisk1
EDIT: One more thing, there is no such thing as a Fdisk Partition. There is only GPT and MBR (Someone correct me if i'm wrong again)
-
EDIT: One more thing, there is no such thing as a Fdisk Partition. There is only GPT and MBR (Someone correct me if i'm wrong again)
Zane, i think it's a Unix (or apple) naming for MBR partitioning scheme, since fdisk is a Unix tool to edit this type of scheme.
If you do "diskutil list" on one of those you'll see:
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *320.1 GB disk1
There's probably a better explanation.
As for rimmi2002's problem, beats me :P but yes, the commands are screwed.
-
You're not even doing it right. You're not even running fdisk440. cd to your i386 folder of chameleon and type
./fdisk440 -f boot0 -u -y /dev/rdisk1
EDIT: One more thing, there is no such thing as a Fdisk Partition. There is only GPT and MBR (Someone correct me if i'm wrong again)
I can try CDing into the directory, but I have done it this way before (multiple times) and it's worked fine. What I did was type cd then (space) and dragged the fdisk440 file to terminal and then wrote the rest of the commands so it should be the right path. I'll go home today and cd into the directory and then try it.
Now I wrote Its a F_Disk_parition_scheme. The disk in question is Disk 1 in my picture above. I did a retail SL install on Disk1 with GUID partition Tables. Not sure what happened, but now that partition shows up a MBR Disk and Disk1S1 which previously was the EFI parition now had a random name "0xEE" and it is not mounted in diskutlity and when I right click on it and ask it to mount nothing happens.
I can boot into SL fine from my USB stick. I am confused how my GPT Disk turned into a MBR without any data loss? Makes no sense. Today I'll go home and try to also repair the boot sector with windows 7 repair disk and see how that goes. Very confused to what caused this.
-
Alrite things are fixed. You were right cding into the folder got fdisk to work. Wierd it use to work fine before when I dragged the file...maybe it was because of the change in disk structure. Thanks for your help. Really apprecaite it.
Also I got my disk structure built back to normal using gdisk and help from this post. http://www.insanelymac.com/forum/index.php?showtopic=231025 (http://www.insanelymac.com/forum/index.php?showtopic=231025)
Attached is a picture of the fixed disk structure. I had removed all disk to work on this one. So now I problematic disk is disk0 and the only one showing.
This is an odd-ball problem so I thought might as well put up the complete solution incase anyone else has it. Thanks for your help.
-
Rimmi2002,
I see that you solved the problem, nice :)
This is what i was a bout to post:you can drag fdisk440 like you mention, but you need to cd into the dir were boot0, boot1h, etc... are, so fdisk can find them.
About the partition scheme changing, now that you pointed the EFI partition type changed things get more clear :P
Something changed the type of the EFI partition to 0xEE, Protective MBR (check here (http://developer.apple.com/mac/library/technotes/tn2006/tn2166.html#SECPROTECTIVEMBR)). That's why the device it's seen as a fdisk partition scheme. You can change the partition type back, though i don't know if it will solve the problem and i'm not sure what tool to use?? Will try to check this... bbl.
So, "GPT fdisk" did the job.. nice to know. It was probably Acronis the culprit of the situation; as far as i can remember has no (or had no) GPT support. Thanks for posting back.