Jump to content

OS X installation on separate HDD (and windows on another)


20 posts in this topic

Recommended Posts

I have Dell XPS L501x laptop, currently running Mavericks. I will be upgrading to Yosemite (will use Clover) and also doing some system upgrades. Since my laptop is old (2010), it has BIOS (and no UEFI support)

 

My current config: i7 740 (first gen Intel proccy), 4GB RAM, 500GB SATA HDD, nvdia 435m graphics card. 

 

- I want to replace HDD with SSD (Samsung Pro 840, 256GB)

- Remove optical drive. Add the HDD here with the caddy

- Replace RAMs with 2x4GB

 

I need multiboot system. Currently both OS X and Windows are installed on same HDD. Now I am thinking to install  OS X on SSD, Windows on HDD. Is that the right way/suggested way to do it? OR shall I install both on SSD? I often read that it's better to install different OS on different partitions, but why so? 

 

Secondly, can anyone give me some instructions or point me to relevant guide? I am not asking for entire tutorial, just brief points will do. Thank you :)

i did something similar with ubuntu and windows 7 on a non UEFI system.

 

i would prefer 2 hdd. if one goes down you have the other to boot.

 

drive order should not matter if you tell the bios which one to boot first as long as its windows.

 

i installed ubuntu on the second drive without the windows drive installed. then reconnected the drive, booted windows and added the ubuntu drive to the boot screen with EasyBCD because my windows drive was first.

 

when you boot Clover, it should show you all the connect devices (USB, HDD, HD Partitions) you could just choose which drive to boot from there.

this is how it works on my UEFI mobo. not sure how Clover works on BIOS machines.

@avin7000,

 

I have an older Dell XPS M1530 laptop, made the transition to Clover a year ago and haven't looked back. 

 

The best way to start is to install Clover on a FAT32 USB stick and experiment with various boot settings in its config.plist.  This way, your hard disk with chameleon is untouched.  Once you find the settings that successfully boot the computer, you can then install to your HD's EFI partition and easily copy Clover's settings over.

 

Also have a look at my posts in the Dell DSDT laptop thread eg here and here for some pointers.  I have converted 3 rigs over to Clover & 2 are old BIOS computers:

 

  1. GA-P55A-UD3/Intel i5-750/ATI 5770
  2. Dell XPS m1530/Intel T9300/nVidia 8600GT
  3. GA-B75M-D3H/i3 3225/Intel HD4000

 

With regard to dual booting, it doesn't really matter whether you install Windows on the same or separate drives but I found it is best to keep all drives partitioned GUID (GPT) and install Windows in UEFI mode via Clover installed in the EFI System Partition.  Even though you have a legacy BIOS, CloverEFI provides a full (U)EFI environment to boot a UEFI Windows Installer USB see Summary of Steps Installing UEFI Windows 7 X64 on internal GPT HD.

 

Useful resources

Clover wiki

Clover Instructions @Insanelymac

Sample Configurations

Clover Configurator

 

Good Luck!

@fusion71au you have given an amazing info, thank you very much! I couldn't find caddy, so as of now I will be installing both OS on my SSD.

 

Here's what I have decided to do:

1. Install Clover to a USB, figure out configuration that works. 

2. Once #1 is done, remove HDD and replace it with SSD

3. Install OS X and Windows (UEFI)

 

I need some clarifications with step 3. Usually, I would use OS X installer, partition the drive and then install Windows and then OS X. 

 

Is it the same way with Clover too? 

1. Boot into OS X installer

2. Format the SSD, with GUID (GPT)

3. Reboot and put in Windows disc

4. Install Windows

5. Boot with OS X installer and install OS X

6. OS X is installed, boot into OS X and install Clover

 

Sounds right? 

 

Lastly, I have all my config.plist, kexts etc saved and I know which all kernel flags are required. Can I make use of them again?  

@avin7000,

 

Your basic plan looks OK but in your step 3,

Reboot computer via Clover on your OS X Installer, then insert your UEFI Windows Installer ---> at Clover's Main Menu, select "Boot UEFI External"/bootx64.efi---> install Windows etc.

 

What I usually do is install OSX and Clover onto the hard drive first (leaving some free space for Windows at the end of the drive).  That way, you can boot via Clover on the target hard drive, then insert the UEFI Windows Installer USB/DVD ---> at Clover's Main Menu, select "Boot UEFI External"/bootx64.efi

 

You can of course reuse the config files that successfully worked on your OS X Installer when you install Clover on the hard drive - config.plist, kexts, DSDT etc.

 

Take home message is that you can't directly boot the UEFI Windows install media without Clover's (U)EFI "translation layer".

 

I hope that's not too confusing for you :).

That's great!

 

If it boots, its good enough ("if it isn't broken, don't fix it" :)) - the common mistake that new users make is to tinker too much with settings they don't or only half understand. 

 

To start with, a minimalist config is best using Clover's defaults.  Make changes/tweaks one at a time after reading what each setting does.

 

I had a look at your config.plist in the Clover General Discussion thread and the only change I would make is to NOT hide bootx64.efi, since you'll need to select bootx64.efi to start your UEFI Windows installer ie

 

remove

<key>Hide</key>
<array>
<string>\EFI\BOOT\BOOTX64.EFI</string>

Also, I remembered I made a post some time ago for creating a dual UEFI Windows 7/Mavericks Installer with Clover installed in its EFI - link post#66.  For Yosemite, just change step 5ii)

sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/OSX --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --no interaction

to

sudo /Applications/Install\ OS\ X\ Yosemite.app/Contents/Resources/createinstallmedia --volume /Volumes/OSX --applicationpath /Applications/Install\ OS\ X\ Yosemite.app --no interaction

Good Luck!

Also, I remembered I made a post some time ago for creating a dual UEFI Windows 7/Mavericks Installer with Clover installed in its EFI - link post#66

Good Luck!

Woot! A single pen drive to install OS X, Win and Linux! Amazing tutorial!

 

and I will remove the part which hides bootx64.efi and report back.

I have ran into multiple issues when I created installation media. I created 3 partitions (OSX, WIN81, UBUNTU) on GUID.

 

1. The installation screen wouldn't appear at all. Screen went blank after 'DSMOS arrived'. I know that Apple changed gfx management since 10.9.3, so I added nv_disable=1 flag and now I can boot into installation media. (On my current Mavericks system, I have added board id to AppleGraphicsControl.kext. I guess I have to do similar fix after Yosemite installation as well?)

 

2. Keyboard and trackpad are not working (but they work if I use same USB to boot into already installed Mavericks). I have external USB mouse and keyboard, shall I proceed installation using these and install kexts later? I use Rehabman's Voodoo kexts on my Mavericks currently.

 

3. I don't understand how to get into Windows installation at all. I have removed that part which hides boot64x.efi from config.plist. And I have made sure that boot64x.efi file exists in /EFI/boot/ as suggested:

 

k3oWitV.png

 

4. I see two drives called WIN81, why so?. Both 2nd and 3rd drive says 'Boot Microsoft EFI boot menu from WIN81'

 

5. I don't see 'bootx64.efi' anywhere at all! 2nd drive boot menu and 3rd drive boot menu

 

6. Lastly, how should I format my target drive, SSD? GUID table (Or MBR?), OS X Journaled for Yosemite and what kind of partition for Windows? NTFS? Or leave this partition blank and let it format by Windows installation?

@avin7000,

 

1+2.  Yes to your first 2 questions.  The "createinstallmedia" method relies on booting off kernelcache (no S/L/E folder on installer) so if kext injection of VoodooPS2Controller from /EFI/CLOVER/Kexts/Other and patching of Graphics by Clover doesn't work, leave it for the post install (or use the "BaseSystem.dmg" method to create an installer).

 

3.  If you don't see "Boot UEFI External from WIN81"/bootx64.efi entry, it must still be hidden from the Clover Menu.  Remove all custom entries under the GUI section of config.plist and just leave auto scanning ie

<key>Scan</key>
<true/>

4.  What you are seeing are not "drives" but loader entries from the Microsoft folder in the WIN81 partition ie one for cdboot.efi and bootmgr.efi.

 

5.  Bootx64.efi=Renamed Bootmgfw.efi in the /efi/boot folder must still be hidden if you don't see an entry "Boot UEFI External from WIN81"/bootx64.efi - see 3 above

 

6.  Target SSD should be formatted GUID HFS+ Journaled for Yosemite.  Just leave free space at the end for Windows - you can create an NTFS partition during Windows install.

 

NB If you use OSX  Disk Utility to add a FAT partition, it will convert the drive from GPT to hybrid mbr ---> prevent install of UEFI Windows.

I tried removing as you instructed, still I don't see Windows bootx64efi. Currently my GUI part is:

 

<key>GUI</key>
<dict>
<key>Language</key>
<string>en:0</string>
<key>Scan</key>
<true/>
</dict>

My entire config file:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>ACPI</key>
	<dict>
		<key>DSDT</key>
		<dict>
			<key>Debug</key>
			<false/>
			<key>DropOEM_DSM</key>
			<false/>
			<key>Name</key>
			<string>DSDT.aml</string>
			<key>ReuseFFFF</key>
			<false/>
		</dict>
		<key>SSDT</key>
		<dict>
			<key>DropOem</key>
			<false/>
			<key>Generate</key>
			<dict>
				<key>CStates</key>
				<true/>
				<key>PStates</key>
				<true/>
			</dict>
		</dict>
	</dict>
	<key>Boot</key>
	<dict>
		<key>Arguments</key>
		<string>-v dart=0 nv_disable=1 kext-dev-mode=1</string>
		<key>DefaultVolume</key>
		<string>MacHDD</string>
		<key>Legacy</key>
		<string>PBR</string>
		<key>Log</key>
		<false/>
		<key>Secure</key>
		<false/>
		<key>Timeout</key>
		<integer>10</integer>
		<key>XMPDetection</key>
		<false/>
	</dict>
	<key>Devices</key>
	<dict>
		<key>Audio</key>
		<dict>
			<key>Inject</key>
			<string>1</string>
		</dict>
		<key>FakeID</key>
		<dict>
			<key>ATI</key>
			<string>0x0</string>
			<key>IMEI</key>
			<string>0x0</string>
			<key>IntelGFX</key>
			<string>0x0</string>
			<key>LAN</key>
			<string>0x0</string>
			<key>NVidia</key>
			<string>0x0</string>
			<key>SATA</key>
			<string>0x0</string>
			<key>WIFI</key>
			<string>0x0</string>
			<key>XHCI</key>
			<string>0x0</string>
		</dict>
		<key>USB</key>
		<dict>
			<key>FixOwnership</key>
			<false/>
			<key>Inject</key>
			<false/>
		</dict>
	</dict>
	<key>DisableDrivers</key>
	<array>
		<string>Nothing</string>
	</array>
	<key>GUI</key>
	<dict>
		<key>Language</key>
		<string>en:0</string>
		<key>Scan</key>
		<true/>
	</dict>
	<key>Graphics</key>
	<dict>
		<key>Inject</key>
		<dict>
			<key>ATI</key>
			<false/>
			<key>Intel</key>
			<false/>
			<key>NVidia</key>
			<true/>
		</dict>
	</dict>
	<key>KernelAndKextPatches</key>
	<dict>
		<key>AppleRTC</key>
		<true/>
		<key>AsusAICPUPM</key>
		<true/>
		<key>KernelPm</key>
		<true/>
		<key>KextsToPatch</key>
		<array>
			<dict>
				<key>Comment</key>
				<string>External icons patch</string>
				<key>Find</key>
				<data>
				RXh0ZXJuYWw=
				</data>
				<key>Name</key>
				<string>AppleAHCIPort</string>
				<key>Replace</key>
				<data>
				SW50ZXJuYWw=
				</data>
			</dict>
		</array>
	</dict>
	<key>SMBIOS</key>
	<dict>
		<key>Trust</key>
		<false/>
	</dict>
	<key>SystemParameters</key>
	<dict>
		<key>InjectKexts</key>
		<string>Detect</string>
		<key>InjectSystemID</key>
		<true/>
		<key>NoCaches</key>
		<false/>
	</dict>
</dict>
</plist>

@avin7000,

 

Strange, the "Boot UEFI External from WIN"/bootx64.efi entry shows up on my USB installer....

 

We'll try another approach: 

1.  Rename cdboot.efi in WIN81/efi/microsoft/boot folder to cdboot.BAK

2.  Copy bootmgfw.efi into WIN81/efi/microsoft/boot

 

post-846696-0-42354800-1418288879_thumb.png

 

3. Reboot the computer with the Installer USB and select "Boot Microsoft EFI boot menu from WIN81", then press <spacebar>

 

post-846696-0-52813400-1418288999_thumb.png

 

4.  Select "Run bootmgfw.efi" and then press <spacebar> ---> should now boot into the UEFI Windows Installer!

 

post-846696-0-34464000-1418289116_thumb.png

_________________________________________________________________________________________________

 

Edit 12/12/14

It looks like @tuxuser has a similar machine to you and has already posted his Clover config files & kexts in the Dell L501x/L701x thread.  Also @whitegerry in post#435.

 

Disable USB Emulation in BIOS to get VoodooPS2Controller.kext working.

 

Audio kexts usually need to be installed in /S/L/E due to other kext dependencies.  For Yosemite, any patched kexts (including patched AppleHDA) will have invalid signatures so you will need to boot with kext-dev-mode=1 kernel flag.

Since Windows can be installed anytime, I went ahead and installed Yosemite

 

1. I read couple of guides which said installer will reboot and I should start it again and it will resume the installation. But nothing such thing happened. Yosemite and recovery HD both were installed in one go.

 

2. Once Yosemite started, I setup the account. After I got into the system, none of the Keats were working, audio, Ethernet etc

 

3. I rebooted and Ethernet is now working. But audio is not :-/

 

4. I checked in EFI folder and kexts actually exists.

 

5. Note that I have not installed clover on my system yet. Only booting from installation media.

Back to windows

 

@fusion - copying that bootmgfw.efi worked. I am doing test installations and I confirm UEFI windows works fine.

 

Boot menu displays following options:

post-702463-0-12332700-1418901657_thumb.jpg

 

options of "Boot from Microsoft EFI Boot Menu from EFI":

post-702463-0-64510400-1418901688_thumb.jpg

 

I hope this is normal and expected.

 

And when i try to boot from 'Windows from legacy HD5' I get following error:

post-702463-0-72344000-1418901731_thumb.jpg

 

So every time I have to use first option from menu I guess? And hide this option of legacy hd boot? How?

@avin7000,

 

All your entries are normal and look good :)!

 

For UEFI Windows, you only need to select bootmgfw.efi to start it. 

 

Re Hiding unneccessary legacy entries and the "UEFI Internal" entry, here's what I use:

<key>GUI</key>
    <dict>
        <key>Custom</key>
        <dict>
            <key>Entries</key>
            <array>
                <dict>
                    <key>FullTitle</key>
                    <string>UEFI Internal</string>
                    <key>Hidden</key>
                    <true/>
                    <key>InjectKexts</key>
                    <false/>
                    <key>NoCaches</key>
                    <false/>
                    <key>Type</key>
                    <string>Other</string>
                </dict>
            </array>
        </dict>
        <key>Scan</key>
        <dict>
            <key>Entries</key>
            <true/>
            <key>Legacy</key>
            <false/>
            <key>Tool</key>
            <false/>
        </dict>   
    </dict>



---->you should see only the OSX, Recovery Partition and Windows to boot from ;).

 

More info on the GUI and hiding entries from the Clover Wiki.

I have some doubt regarding clover config options.

1. 'Install for UEFI booting only' -- I should not select this since I have legacy bios
2. 'Install Clover in the ESP':

  • Do not select this for test pen drive, which is in MBR 
  • Select this for installation USB drive (which is on GPT)
  • Select this for HDD (which is on GPT)

Am I right? 

 

3. What does 'Install RC scripts on target volume' do? 

@avin7000,

 

To answer your questions:

 

1.  Correct.  'Install for UEFI booting only' is for machines with UEFI BIOS

2.  Correct.  ESP = EFI System Partition:  exists only on GPT formatted drive.

3.  This option enables installation of Clover's launchd scripts, necessary to save NVRAM variables on legacy machines that don't have real (hardware) NVRAM ---> saved to NVRAM.plist file on disk.  I would recommend checking this since NVRAM is required for proper iMessage/Facetime functioning (MLB/ROM vars are saved to NVRAM).

×
×
  • Create New...