[GUIDE] Scripted Yosemite/Mavericks Install on Gigabyte Mobos

[Sidewinder33]

Hey DD,

I've hit a bit of a weird snag when I try to install the bootloader on a fresh RAID setup,

 

Here is the console log of the error

###################### For disk2s3:

Copying stage0 MBR (boot0) and stage1 partition boot record (boot1h)
2+0 records in
2+0 records out
1024 bytes transferred in 0.000181 secs (5658718 bytes/sec)
#### Copying Boot file to /Volumes/Boot OSX
chmod: /Volumes/Boot OSX/boot: Not a directory
chown: /Volumes/Boot OSX/boot: Not a directory

mkdir: /Volumes/Boot OSX: Not a directory
mkdir: /Volumes/Boot OSX/Extra: Not a directory
mkdir: /Volumes/Boot OSX/Extra/Stored_Kexts: Not a directory
Copying contents of _Cham_2.0_RC4_Asere/Extra to /Volumes/Boot OSX/Extra
cp: /Volumes/Boot OSX/Extra: Not a directory

Bootloader install has failed!
Unable to install boot file in /Volumes/Boot OSX directory!
Current disk ID under test: disk2s3

 

It just started happening, I've been having issues setting my said back up after taking it apart to try out the new script. Any thoughts?

[knightprozac]

It just started happening, I've been having issues setting my said back up after taking it apart to try out the new script. Any thoughts?

Are you able to mount Boot OSX with the terminal using "diskutil mount disk2s3"?

[Sidewinder33]

Are you able to mount Boot OSX with the terminal using "diskutil mount disk2s3"?

 

Ya I can and the script pulls the helper partition up also.

 

Edit 1:

As a side not the old script doesn't install a bootloader either so its gotta be something in my system

 

Edit 2:

So I was going back through aquamacs guide to setting up a Striped RAID and I found something a bit odder, when I type

sudo su

in to terminal, I put in my password

 

get a return of

su: sorry

 

Any ideas sounds like a permissions issue now but I dont know why it would be messed up

 

 

EDIT:

Alright so I restored from a time machine backup and everything is back up and running on my backup boot disk, the raid is working but now for some reason I have two RAID options in the boot loader Macintosh Raid 1 and Macintosh Raid 2 But I only have the one Raid setup, I dont think its the helper partitions as those are still named Boot OSX 1 & 2, any thoughts on this double raid partition?

Added pics to kinda show what I mean. Does any one know if both helper partitions have to be used? If I set a default partition in the bootloader shouldn't I only need one helper partition?,

 

I have a theory that both helper partitions are seeing the Raid, and offering it up for boot using one or the other helper partitions.

[Windows04]

Mmm... Ok the super combo build cache can be made on one disk, but not on another... Maybe it's a stupid idea but well, who knows:

 

When I hadn't enough space on the RAID helper paritition, i just reformatted it to HFS+ and started over (so install the bootloader + install kexts) and the system could boot. Also the RAID helper partitions can have another name than Boot OSX.

 

I don't know if this is possible, but maybe you can put a reformat option in the script to reformat the RAID helper partitions? Or even better, when the script detects that extensions.mkext takes too much place, immediately reformat the partition and install the extensions.mkext...

 

Allright, just tell me if i'm asking too much from you, it is a great script though .

[digital_dreamer]

Yes

 

Yep. I'm switching my boot disks through the the bios (Running F13b). Something is definitely going on. I did a fresh install and still had the same problem after installing 10.6.3 and the exotic pkg. I tried reinstalling the bootloader (PCEFI 10.6) selecting no for preserving current files but it didn't fix the problem. I'm going to attempt to install the bootloader after doing my OS install and updates to see if this works, although this might be worrying for me to perform future updates.

 

If i set my first bootable drive (in Bios) to my RAID but then choose my Non-RAID backup drive in the bootloader then my machine will boot and use all of the user settings and setup from my RAID drive. I'm running 10.6.3 on both of these with the same kexts. This isn't optimal for me as I always like to have to completely independant bootable volumes to allow me to fix any problems that might come up.

 

I will report back on any progress.

So, were you not able to boot the RAID setup at all without the exotic pkg related crash? Or, get it to recognize the boot.plist strings?

 

Hey DD,

I've hit a bit of a weird snag when I try to install the bootloader on a fresh RAID setup,

 

Here is the console log of the error

###################### For disk2s3:

Copying stage0 MBR (boot0) and stage1 partition boot record (boot1h)
2+0 records in
2+0 records out
1024 bytes transferred in 0.000181 secs (5658718 bytes/sec)
#### Copying Boot file to /Volumes/Boot OSX
chmod: /Volumes/Boot OSX/boot: Not a directory
chown: /Volumes/Boot OSX/boot: Not a directory

mkdir: /Volumes/Boot OSX: Not a directory
mkdir: /Volumes/Boot OSX/Extra: Not a directory
mkdir: /Volumes/Boot OSX/Extra/Stored_Kexts: Not a directory
Copying contents of _Cham_2.0_RC4_Asere/Extra to /Volumes/Boot OSX/Extra
cp: /Volumes/Boot OSX/Extra: Not a directory

Bootloader install has failed!
Unable to install boot file in /Volumes/Boot OSX directory!
Current disk ID under test: disk2s3

 

It just started happening, I've been having issues setting my said back up after taking it apart to try out the new script. Any thoughts?

 

 

EDIT:

Alright so I restored from a time machine backup and everything is back up and running on my backup boot disk, the raid is working but now for some reason I have two RAID options in the boot loader Macintosh Raid 1 and Macintosh Raid 2 But I only have the one Raid setup, I dont think its the helper partitions as those are still named Boot OSX 1 & 2, any thoughts on this double raid partition?

Added pics to kinda show what I mean. Does any one know if both helper partitions have to be used? If I set a default partition in the bootloader shouldn't I only need one helper partition?,

 

I have a theory that both helper partitions are seeing the Raid, and offering it up for boot using one or the other helper partitions.

Okay. You may have a duplicate mount point in play here.

This is one of the issues I tried very hard to keep from happening, but given the number of volumes that must be mounted and unmounted, this issue can crop up.

 

First make sure any RAID helper partitions are unmounted from the desktop

Do a 'ls /volumes' in Terminal and will likely see the extra mount points - that is, pseudo volumes - they are not really volumes, but files that were created because the system thought that volume was mounted and ready to be written to. If one attempted to write to a "volume" that is not really mounted, it will create a mount point, or a duplicate mount point, in this case.

 

So, do the 'ls /Volumes' and take note of any names that are not really volumes and delete them.

BE CAREFUL HERE or a mistake will delete a valid volume!!!

So, if "Macintosh Raid 2" is listed in the 'ls /Volumes' output and you really don't have that volume mounted on the desktop, it's a multiple mount point and can be deleted.

sudo -s

rm -rf "/Volumes/Macintosh Raid 2"

 

Here are some things to be aware of:

1. The script is written so that all hidden volumes (EFI and RAID helper partitions) are unmounted during idle periods (i.e. waiting for a user response). The exceptions to this is when viewing partitions (obviously) and when check for current install target type (/EFI or /Extra) after you have selected a drive. This is so that if the user attempts to cancel the script, no hidden volumes are left unmounted, which can cause much trouble.

Because the volumes are characteristically using the same names ("EFI" or "Boot OSX"), an unmounted "BOOT OSX" volume may cause the script to think the correct partition is already mounted, even though it really belongs to a different disk/partition.

 

2. Always make sure you don't have any hidden volumes mounted prior to running the script.

(If you decide to cancel the script with viewing a EFI or RAID helper partition, you need to unmount them manually.)

I think I'm going to have to write that in and also figure out a way to determine if there are multiple mount points. I did have this scripted in a long time ago, but it was useless for EFI partitions after I found a way to get around it.

 

3. Note, too, the Mac Finder is not happy when these partitions get mounted and unmounted quickly in secession. This was especially the case in 10.6.2 - a big difference from 10.6.1. For some reason, if the script mounts a EFI or RAID helper partition, the Finder wants to do something with it (probably make it viewable on the desktop) and when you quickly unmount, that is, before the Finder is finished with it, you'll get a Finder crash (relaunch). This started with 10.6.2 and would happen all the time. Even adding a 2 second delay after a mount didn't fully remove this issue. However, I noticed that if I did some file copy on the volume, this undesirable behavior was nearly eliminated. It may be that the disk I/O delays the Finder's attention, I don't know. So, this is what the script does for the RAID helper partitions (the most sensitive).

 

All this was territory I was ushered in when writing for the EFI partition setup, but was able to get around it. Now, with RAID, I'm forced to deal with it again.

 

Watch out for hidden volumes that stay mounted and keep an eye on multiple mount points.

To the Terminal (or script) the multiple mount point may look exactly like a real volume, except much, much smaller, as it only has the files that were written to it during the mishap.

 

MAJ

[Sidewinder33]

No luck with the ls /volumes only the volumes I have show up I will just hide the partition in the boot.plist and be happy with it .

 

Sadly as I was messing with stuff, I mucked with something on my boot disk (I use my time machine disk to boot) but now I've got it back up and running, and all is well.

 

And so you know DD every now and then when working with a RAID drive selected the view the efi /raid partition options get messed up. It usually shows RAID, but after messing with plists and other misc things that take me away from the main menu. Going back away from the main menu and coming back typically fixes it.

 

One thing I did have a question on was the need for both boot.plist in the helper partitions, both in the extra folder and in the com.apple.boot.S/library/preferences/systemconfiguration/. I have them identical for safety purposes but was just curious if they both need to be in there.

[digital_dreamer]

No luck with the ls /volumes only the volumes I have show up I will just hide the partition in the boot.plist and be happy with it .

 

Sadly as I was messing with stuff, I mucked with something on my boot disk (I use my time machine disk to boot) but now I've got it back up and running, and all is well.

 

And so you know DD every now and then when working with a RAID drive selected the view the efi /raid partition options get messed up. It usually shows RAID, but after messing with plists and other misc things that take me away from the main menu. Going back away from the main menu and coming back typically fixes it.

 

One thing I did have a question on was the need for both boot.plist in the helper partitions, both in the extra folder and in the com.apple.boot.S/library/preferences/systemconfiguration/. I have them identical for safety purposes but was just curious if they both need to be in there.

Thanks for the heads up on the viewer. Not surprised about that one. Keeping the /Extra and /EFI flags straight was difficult. I'll keep an eye on that and see where it's coming from.

 

As for the other boot plist in the RAID helper. My experience has been that it gets updated from any changes on the root volume. If you add a flag in the plist on your root volume, it will get updated on the helper, too, but not immediately. Don't know what triggers it. I know if you make changes in the S/L/E, that will trigger a new boot cache in the helper, as well.

For a while I was trying to use the boot plist in C/L/P/S (there's a new one) for the RAID setup, but it kept getting replaced or altered by the OS, so I dropped that plan.

Don't really think it's needed for the bootloader to function. The only information it contains on the basic level is the root uuid, which, in this case, is the UUID of the helper partition, not the RAID device. You can't delete it successfully, either - I've tried.

 

I have another update attached. v4.5b2

• Fixed a permissions issue that can occur with the boot plist. This would create a unreadable boot plist which would cause the script to attempt writing the entire drive to the helper partition, because it couldn't get the name of the kernel. Ouch.

• Reversed order of RAID partition viewer so that the partition that gets modified and copied to the others is the first to be viewed.

• Rewrote the RAID copy section so that drag 'N drop changes to the partition would carry over properly.

• When changing from /EFI install to /Extra (or vice versa), any modified kernels will be uninstalled from the root volume, allowing one to start with a vanilla setup.

 

MAJ

 

EDIT: I was rereading Sidewinder33's comments..

Only one helper partition is needed at any one time, AFAIK. The only reason files are copied to the other one is so that one can choose one or the other. I haven't really tested this out, but if a user chose to set up only one helper partition, he would have to make sure that partition is the one selected by the bootloader, which could be error prone or confusing.

[knightprozac]

So, were you not able to boot the RAID setup at all without the exotic pkg related crash? Or, get it to recognize the boot.plist strings?

After playing around with things I've figured out that I can boot into my RAID install (I made a fresh one). The "Timeout" for the bootloader refuses to work. It just acts like there isn't one at all. After installing the exotic pkg I was unable to boot using Graphics Enabler (something I was able to do previously). I can boot fine if I use Aty_init or Evoenabler.

 

Sound has been driving me crazy lately but my problems with that started before using the new RAID script. In addition to the background squeal/buzz that I've always had through my speakers my sound is now choppy/cutting out when playing WoW.

 

[Edit]I suspected my update to f13b bios was causing issues for me with sound being choppy. I've downgraded to f12 and also had a look at what things were like without overclocking. Haven't had the choppy sound and the buzzing is also significantly quieter.

[ncsa]

DD - thanks for a great thread and fantastic work... finally moved from your 10.5.x script and this 10.6.x one is even easier.... I will be looking at the RAID option too.. cheers.

[digital_dreamer]

Another update:

• Fixed a bug where the script would lose track of RAID status when using the plist editor. This bug, originally referred to by Sidewinder33, would cause the "View partitions" routine to only view one partition, even in RAID mode.
  
• Implemented a routine to unmount any EFI or RAID helper partitions at the start of the script.
  
• Added ability to prevent automounting of EFI partitions by modifying the file system descriptor (/etc/fstab). Note that this change is non-destructive and will retain any modifications others have already made to the fstab file.
  

 

Any other bugs observed, please swing 'em by.

I think I'll try to implement a test for storage space error when copying to other RAID helper partitions. This would generally be due to boot cache space not fitting on a second RAID partition, because the second RAID partition may have the OS RAID support files, instead of the first.

Once I get the Boot disk portion done, it will be released on the front page.

 

Regards,

MAJ

[jhrfc]

Just Completed a fresh install with the new script, and asere bootloader, also using d00ds dsdt mods. I'm now using fewer kexts and a two hundred point increase in my geek bench score.

Keep up the good work.

Jon

[Sidewinder33]

Great work DD, I have finally gotten all my stuff set up and working the way I want it to.

 

Turns out the double mounting points was entirely my fault. I restored my Raid using a time machine back up (no big deal, and with the script its easy as all hell). The problem was I had called the new Raid the same name as my previous raid ie. my old setup was called Macintosh Raid, and the new Raid I had set up was called the same. I think that in the restoration process the comp didn't like the dual names and changed the name of the restore without actually changing the physical name of the raid. Odd but creating a raid with another name then restoring made the double name go away.

 

Other than my own dumb mistakes the script works great.

[Dajjal]

Hi guys does your sound Preferences & About mac look like this,when using the patched DSDT an files that CruiSAr suggested?In About mac i see 2 External Mic's,shouldn there be 1Mic & 1Line input?In preferences under input shouldn there also be Line in together with Digital in?Or is this how it suppose to be.I did not use any kext for sound and the AppleHDA was not changed to the patched version from 10.6.2.Onboard sound works (black 1/8 Jack) but i dont use it as i have external firewire,but i'll like to know that if need be everything is how it suppose to be.Thanks,Bless.

 

 

[RickyTan]

Hi guys does your sound Preferences & About mac look like this,when using the patched DSDT an files that CruiSAr suggested?In About mac i see 2 External Mic's,shouldn there be 1Mic & 1Line input?In preferences under input shouldn there also be Line in together with Digital in?Or is this how it suppose to be.I did not use any kext for sound and the AppleHDA was not changed to the patched version from 10.6.2.Onboard sound works (black 1/8 Jack) but i dont use it as i have external firewire,but i'll like to know that if need be everything is how it suppose to be.Thanks,Bless.

 

 

 

I see the exact results you do with the CrusAir method. I think it is a result of the patched DSDT. Everything functions properly, but the inputs and outputs are not 100% accurate.

[CruiSAr]

I see the exact results you do with the CrusAir method. I think it is a result of the patched DSDT. Everything functions properly, but the inputs and outputs are not 100% accurate.

Yes I know this and I stated it in the guide. For me it is pure cosmetics and since I only use the digital out I dont mind the way it looks that much. If it bothers you, you can load the 2 kexts that come with DD's script and you should be fine.

 

You can also apply the audio fixes in d00ds thread

[Dajjal]

Thanks for the reply's guys,i really did not see mention of the cosmetic part in the guide, my bad. .bless

[harutik_11]

Thanks a bunch guys

[torifile]

I had a working vanilla install of 10.6.1 on my x58-ud5 board (installed using the lifehacker method and a retail SL DVD) and I updated to 10.6.3 last night using software update. My machine boots but my graphics are stuck at 1024x768, no sound and no ethernet. Any ideas about how I can fix it? My video card is a Radeon 4890. TIA.

[dewby]

Ok so I just finished building my computer, the internals are as follows:

EX58-UD5

i7 930

6gb ddr3 Corsair TR3XG1600

1gb ddr3 GTS 250

---

I just finished installing snow leopard using the empire efi dvd. For some reason OSX is seeing my ram as 400mhz ram. I have reinstalled SL three times now, and it just won't recognize the 1600mhz ram. HELP ME!! PLEASE!!

 

--

*As a funny side note SL is installing easier than windows, for some reason my Windows 7 Pro key won't work, and XP keeps blue screening at install.

[digital_dreamer]

I had a working vanilla install of 10.6.1 on my x58-ud5 board (installed using the lifehacker method and a retail SL DVD) and I updated to 10.6.3 last night using software update. My machine boots but my graphics are stuck at 1024x768, no sound and no ethernet. Any ideas about how I can fix it? My video card is a Radeon 4890. TIA.

torifile,

You'll need to reinstall the modified kexts. Whether they go in /Extra or in System/Library/Extensions depends on your setup. Your graphics card probably needs a special installer for it, as well, like netkas' QE/CI for exotic cards.

 

Ok so I just finished building my computer, the internals are as follows:

EX58-UD5

i7 930

6gb ddr3 Corsair TR3XG1600

1gb ddr3 GTS 250

---

I just finished installing snow leopard using the empire efi dvd. For some reason OSX is seeing my ram as 400mhz ram. I have reinstalled SL three times now, and it just won't recognize the 1600mhz ram. HELP ME!! PLEASE!!

 

--

*As a funny side note SL is installing easier than windows, for some reason my Windows 7 Pro key won't work, and XP keeps blue screening at install.

That is just cosmetic. Your RAM is running at whatever your BIOS is set for.

To change the RAM speed that's displayed, you'll need to change two different files. One affects the "About this Mac" label and the other affects the System Profiler display.

Look it up on the forums.

 

regards,

MAJ

[dewby]

Another thing that I have noticed is that when I install a kext for my graphics card, it makes the computer lag up hella bad

[Sidewinder33]

Another thing that I have noticed is that when I install a kext for my graphics card, it makes the computer lag up hella bad

 

You shouldn't need any kext for your GPU. Graphics Enabler should work for you but if not injecting an efi string (using DD's script) is a good way to go.

 

To add it edit your plist and at the bottom there should be an option to add a device property, follow the steps and you should be good to go.

[AviEinZur]

Hi guys!

 

 

 

Secondly I've tried booting the Kalyway 10.5.1 disc which works up to the installer. Yay something works!!! It even appears to install ok too, and I've tried every single boot fix method I can find on the net to get the resulting disk to boot but again to no avail.

 

 

Hey Matt,

I'm no expert, as you can see in my signature i do ran into troubles too, but my advice is for you to shut down all enhanceing options of CPU in bios and try booting. for me it gave me the chance of booing in -x mode (safe boot) and installing SL from there.

my problem now is that SL also boots only in -x mode, otherwise i get a currupted screen right after succesfull boot. im guessing thats related to some more bios tweak and GPU...

 

Insanely Mac is like walking in the dark hopping for someone would turn the lights on, but eventually if you stay long enough you get used to it and start seeing by yourself...

 

hope it would help..

 

EDIT: problem solved

[MikeBuzzsaw]

Anyone running into problems of installing missing sync for blackberry?

[rgb]

Anyone running into problems of installing missing sync for blackberry?

kp when booting in 64bit mode