GPT Test Test Error. Here we go Again!!

[osxfr33k]

I am unable to install Chameleon onto the root of this New Seagate 750GB Drive.  I can only get Chameleon to Boot if I install it onto the EFI partition.

What can I do to get this to work off the Root of the drive?


osxfr33ks-MacBook-Pro:~ osxfr33k$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI                         209.7 MB   disk0s1
   2:                  Apple_HFS L1                      349.6 GB   disk0s2
   3:                  Apple_HFS L2                      150.1 GB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *750.2 GB   disk1
   1:                        EFI                         209.7 MB   disk1s1
   2:                  Apple_HFS LION1                   375.1 GB   disk1s2
   3:                  Apple_HFS LION2                   374.6 GB   disk1s3

Lion1 is the drive I am trying to install Chameleon onto its root.  Only works installed on EFI.


Asus G74SX not much in the way of Bios settings.  AHCI is enabled.

Lion 10.7.2

Thanks

[Gringo Vermelho]

What's "root of the drive"? Do you mean the root of your system partition?

[osxfr33k]

Yes as you said where Chameleon normal default is correct.

[Gringo Vermelho]

It sounds like you are using an installer? There is no "Chameleon normal default".

Remove the file "boot" from your EFI partition and try installing Chameleon to your system partition manually.
Make your own boot CD so that you can still boot if you mess up.

Follow the links in my signature.

[osxfr33k]

I should have been more specific in my original post.  Not only have I tired the Chameleon installer "Chameleon-2.1svn-r1618.pkg"  I have also done a manual install still will not boot.

I have the second hard drive I can use to boot the other if it screws up.  Something going on with this 750GB drive or maybe because I have two drives in this Asus Laptop?

I had this problem once before and the only way I could resolve it was to install Chameleon onto the EFI then remove the boot file then install it onto the non EFI portion if you will.

Maybe I need to remove the other drive and try this again?

What I mean by normal default is the STANDARD choice on the installer which is the default.  Just a question of semantics.  Sorry.

[Blackosx]

Hi osxfr33k

Can you maybe try the latest package installer (rev1684) from buildbot, then post the resulting installer log? The installer has changed a lot since rev1618.

Regards

[osxfr33k]

I also forgot to mention that initially I did use Chameleon Wizard but BuildBot was down for a while so I had to use both the r1618 installer and manual methods.

Still no go:

boot0:  GPT
boot0:  test
boot0:  done
boot1:  error


Where is the Chameleon Wizard install log kept?  I could not find it in /var/log

I never use the Chameleon Wizard application options for Boot0hfs and Boot0md,  only boot0 and below that choice Update with boot1h ticked.  I did try Boot0hfs and that did not work.  I did not try Boot0md.

Thanks


EDITED:

System Log:

Code: [Select]

Nov  8 16:31:59 Davids-MacBook-Pro Chameleon Wizard[210]: Buildbot Xcode 4.0.1 latest rev: 1565
Nov  8 16:31:59 Davids-MacBook-Pro Chameleon Wizard[210]: Buildbot Xcode 4.1   latest rev: 1684
Nov  8 16:31:59 Davids-MacBook-Pro Chameleon Wizard[210]: Using Buildbot Xcode 4.1
Nov  8 16:32:13 Davids-MacBook-Pro login[226]: USER_PROCESS: 226 ttys000
Nov  8 16:35:15 Davids-MacBook-Pro authexec[294]: executing /Applications/Chameleon Wizard.app/Contents/Resources/fdisk
Nov  8 16:35:15 Davids-MacBook-Pro authexec[295]: executing /bin/dd
Nov  8 16:35:15 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records in
Nov  8 16:35:15 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records out
Nov  8 16:35:15 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 1024 bytes transferred in 0.001684 secs (608094 bytes/sec)
Nov  8 16:35:15 Davids-MacBook-Pro authexec[296]: executing /bin/cp
Nov  8 16:35:15 Davids-MacBook-Pro authexec[297]: executing /usr/bin/chflags
Nov  8 16:35:15 Davids-MacBook-Pro authexec[298]: executing /usr/sbin/chown
Nov  8 16:35:15 Davids-MacBook-Pro authexec[299]: executing /bin/chmod
Nov  8 16:35:15 Davids-MacBook-Pro authexec[300]: executing /usr/bin/chflags
Nov  8 16:35:17 Davids-MacBook-Pro firmwaresyncd[49]: /sbin/fsck_msdos exited with 8
Nov  8 16:35:17 Davids-MacBook-Pro firmwaresyncd[49]: Command /sbin/fsck_msdos output: ** /dev/disk0s1
        Invalid BS_jmpBoot in boot block: fa31c0
Nov  8 16:35:56 Davids-MacBook-Pro authexec[317]: executing /Applications/Chameleon Wizard.app/Contents/Resources/fdisk
Nov  8 16:35:56 Davids-MacBook-Pro authexec[318]: executing /bin/dd
Nov  8 16:35:56 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records in
Nov  8 16:35:56 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records out
Nov  8 16:35:56 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 1024 bytes transferred in 0.001095 secs (935112 bytes/sec)
Nov  8 16:35:56 Davids-MacBook-Pro authexec[319]: executing /bin/cp
Nov  8 16:35:56 Davids-MacBook-Pro authexec[320]: executing /usr/bin/chflags
Nov  8 16:35:56 Davids-MacBook-Pro authexec[321]: executing /usr/sbin/chown
Nov  8 16:35:56 Davids-MacBook-Pro authexec[322]: executing /bin/chmod
Nov  8 16:35:56 Davids-MacBook-Pro authexec[323]: executing /usr/bin/chflags
Nov  8 16:35:56 Davids-MacBook-Pro authexec[324]: executing /usr/sbin/chown
Nov  8 16:35:56 Davids-MacBook-Pro authexec[325]: executing /bin/chmod
Nov  8 16:35:56 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: fdisk: /dev/disk0: Permission denied
Nov  8 16:36:13 Davids-MacBook-Pro authexec[338]: executing /bin/dd
Nov  8 16:36:13 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records in
Nov  8 16:36:13 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 2+0 records out
Nov  8 16:36:13 Davids-MacBook-Pro [0x0-0x12012].janek202.Chameleon-Wizard[210]: 1024 bytes transferred in 0.001062 secs (964294 bytes/sec)
Nov  8 16:36:13 Davids-MacBook-Pro authexec[339]: executing /bin/cp
Nov  8 16:36:13 Davids-MacBook-Pro authexec[340]: executing /usr/bin/chflags
Nov  8 16:36:13 Davids-MacBook-Pro authexec[341]: executing /usr/sbin/chown
Nov  8 16:36:13 Davids-MacBook-Pro authexec[342]: executing /bin/chmod
Nov  8 16:36:13 Davids-MacBook-Pro authexec[343]: executing /usr/bin/chflags
Nov  8 16:36:21 Davids-MacBook-Pro login[226]: DEAD_PROCESS: 226 ttys000
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.launchd.peruser.501[135] (com.apple.talagent[150]): Exited: Killed: 9
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.launchd.peruser.501[135] (com.apple.mdworker.pool.0[166]): Exited: Terminated: 15
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.launchd.peruser.501[135] (com.apple.mdworker.pool.1[240]): Exited: Terminated: 15
Nov  8 16:36:25 Davids-MacBook-Pro loginwindow[44]: DEAD_PROCESS: 44 console
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: 2011-11-08 16:36:25.117 com.apple.dock.extra[349:1707] Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: 2011-11-08 16:36:25.118 com.apple.dock.extra[349:1707] Could not connect the action buttonPressed: to target of class NSApplication

Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: 2011-11-08 16:36:25.119 com.apple.dock.extra[349:1707] Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro com.apple.dock.extra[349]: 2011-11-08 16:36:25.120 com.apple.dock.extra[349:1707] Could not connect the action buttonPressed: to target of class NSApplication
Nov  8 16:36:25 Davids-MacBook-Pro airportd[351]: _doAutoJoin: Already associated to “GOH-Guest”. Bailing on auto-join.
Nov  8 16:36:25 Davids-MacBook-Pro shutdown[353]: reboot by osxfr33k:
Nov  8 16:36:25 Davids-MacBook-Pro shutdown[353]: SHUTDOWN_TIME: 1320791785 513772
Mod Edit: Placed the posted log in to code tags.

[Blackosx]

Hi osxfr33k

Ah.. I see you've used Chameleon Wizard... That's a separate application and not what I was asking you to use.

I was referring to the open source package installer which you can download from the voodooproject's buildbot. Here's the link:
Download r1684 package installer.

After running the installer, you will have a file named Chameleon_Installer_Log.txt saved at the root of the selected drive. If you could attach that here then I can see what it contains.

But from what you posted above about receiving the boot1:  error, I would say that's the result of removing the boot file from your EFI system partition. Running the installer I've linked to above will either attempt to fix any problem you have with multiple Chameleon installations, or hopefully tell you what the problem is.

[osxfr33k]

Here is the log.  Still not working?  Only other thing I can think to do is format the drive with Disk Utility and then install chameleon then CCC the other drive back onto the 750 GB drive.  I wonder if there is some non dos hidden partition that is not getting wiped when formated with Disk Util?  I think I read this in some post a while back to try and use a Linux Util such as Gparted or Linux fdisk to initialize it that way possibly wiping out any such hidden sectors etc?

I  am just guessing here.

boot0:  GPT
boot0:  test
boot0:  test
boot0:  test
boot0:  test
boot0:  GPT
boot0:  test
boot0:  test
boot0:  test
boot0:  error

Hold on I see something unusual in the log maybe something I mentioned above?  Maybe Not?

*1: EE 1023 254  63 - 1023 254  63 [         1 - 1465149167] <Unknown ID>      <<  WHat does this mean?

[Blackosx]

Thanks for running the test osxfr33k.

However, I am now unsure of your problem and you are unfortunately back to where you started.
My knowledge doesn't go as far as understanding the in's and out's of boot0 and so I can't comment on why you see the test messages followed by error. I am sure Zef or dmazar could debug it for you 

There might well be more info on that issue in previous posts in this forum. I haven't searched as yet, though I guess you will have before posting this question in the first place?

One thing I notice in the log file you posted, is there was no record of the scripts finding a previous stage 1 loader on /dev/disk1 which I thought it would as you say you've previously installed Chameleon to the EFI system partition of disk1?

*1: EE 1023 254  63 - 1023 254  63 [         1 - 1465149167] <Unknown ID>      <<  WHat does this mean?

Thats normal for the EFI system partition. I have the same on my iMac.

[r0m30]

Is this possibly another issue with advanced format drives?  When you say new, is the drive newly purchased? 

Try doing a dd from /dev/rdisk1s2 to a file in /tmp and see if the boot1 code "stuck" 

[osxfr33k]

Relatively new Laptop G74SX.  I had bought three versions of this in the past 3 months.  One from Best buy which had a lower resolution screen then one from TigerDirect then found out my work was going to pitch in and buy it.  Each one of the drives seem to have this issue installing chameleon, so I had to place one of my 500GB purchased Seagate drives from Newegg.

The Advanced Formate Drive is this the "Generation one Advanced Format, 4K sector technology"?

Can you give me the exact string to run in terminal I can try this now.  IF this is what you say it is then how can I fix this issue?  Re-initialize it with Linux Fdisk or Gparted for example?

Is there a link on how to fix this if this is one of those NEWLY advanced formated drives or is the work around as I have it now install Chameleon to the EFI?  It works fine that way but rather not have it like that since it not really supported that way?

[Blackosx]

If your disk does use the 4K sectors then it won't work for now. See issue #129
Otherwise it might be worth trying out dmazar's debug version of boot0md so you can find out what's happening. See here

Can you give me the exact string to run in terminal I can try this now.

You can dump your partition boot sector to a text file by using the following command:

Code: [Select]

sudo dd if=/dev/rdisk1s2 count=2 of=partitionbootsectorJust replace rdisk1s2 with whatever value is appropriate for your system at the time.

[r0m30]

The Advanced Formate Drive is this the "Generation one Advanced Format, 4K sector technology"?

I believe that is what they call 512e.  Until Chameleon is updated to recognize AF disks you'll have to try and find an older disk.

[osxfr33k]

Thanks for the help. It boots up fine if I install Chameleon into the EFI just have to have the Extra folder there otherwise the Themes won't load.

I can deal with that until there is a fix.

Thanks Again!!