Jump to content

Clover not recognising new install


Attica
 Share

17 posts in this topic

Recommended Posts

First off, sorry for another post in such a short amount of time. If a mod reads this, please either close or delete my previous thread. I've since decided to abandon the idea of retaining my old install.

 

So, fresh install via vanilla yosemite usb-installer, created with createinstallmedia. Another drive with clover (created with bootdiskutility) recognized the drive and was able to boot it without any modifications to the config. From what I can tell, the install succeeded, no errors or anything. After the process, the system tried to reboot. I had to manually reset the machine because it would just turn the display off but that's to be expected, isn't it?

 

However, when I now boot into clover, it does not recognise the new installation at all and I cannot continue.

Link to comment
Share on other sites

Sure;

 

Asus Z87-A, 8GB Ram

i7 4770

MSI GTX 760 OC

 

Here's a photo of the installation log. It stays like that the entire process and then (if you wait long enough) reboots by itself. Apparently I didn't wait long enough before, but the problem itself remains unchanged. Further, DiskUtility claims that there are about 400 mb worth of data on the drive. Shouldn't it be a few gigabytes, at least?

Link to comment
Share on other sites

Separate.

 

USB1 - Clover, made with BootDiskUtility + the base system, so I can use diskutility and all that.

USB2 - Vanilla installer, made with createinstallmedia.

 

Boot USB1, select USB2, install to hdd.

 

Just checked: checksum on installESD.dmg is valid, too.

Link to comment
Share on other sites

SSD on one port, an old spare hdd for testing on another. Doesn't seem to matter though, since I had the same issue yesterday when just the ssd was connected.

 

Just tried with mavericks. Exact same issue.

Also tried to use a partition on the hdd as install media. With the exception of the install going much faster - same issue.

 

When I still had the initial install (from my mbp), clover would recognise the drive though other issues made me give up on trying to fix that system. It appears to be install related, yet the installers don't seem to be corrupted and since I'm using createinstallmedia, there's not much to mess up on my side either.

Link to comment
Share on other sites

One thing those, ssd and motherboard sometimes(happen to me) they not work together, a differnet brand of ssd is not show to a particular mother, swap that ssd to other motherboard,it work show up great and vice vesa.

Other thing is I don't know how you make installer, assum 1 is name of the installer.

 

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

This work for me many times w/o any trouble. Of course you still need follow clover guide to finish for installer, configurate config.plist, fakesmc, HFSPlus file

Link to comment
Share on other sites

I do have a spare box but that one doesn't suppport uefi. I also think that this is a software related problem, as clover recognized the old install just fine. Can somebody clarify whether the install data is really just 400mb? If not, the problem lies with the inataller not installing the data correctly. That'd make sense since it never logs anything after the verification part.

Link to comment
Share on other sites

"The fresh install" meaning the installed system or the package that still needs to be unpacked? I'm talking about the latter. You know, first you install, then it reboots and finishes up the install. I'm interested in how much space the install takes up before the second part of the installation.

Link to comment
Share on other sites

Okay, you can officially label me an idiot. That's how it works? I mean, I was just about to post that I indeed got it to work but I had no idea why and so I just considered myself lucky.

I was under the impression that you first install, then boot from the drive to finalize the install. God, I feel stupid now.

 

In any case; it works. Writing this from my fresh yosemite install. Surprisingly easy, too. I still need to fix a few minor things like getting the network kext to load without the "without cache"-setting and audio but other than that, everythings fine.

 

Another quick question, if you don't mind: I'm getting quite a lot of messages in my console. Failed to do this, assertion of that. Nothing that strikes me as particularily game-breaking but is this normal? As far as I can recall, I didn't have that much stuff going on on my MBP.

 

Again, thanks for your help. 

Link to comment
Share on other sites

Just to update this thread; everything is up and running now. Haven't had any crashes, sleep works, too. :)

 

There's still quite a few errors/problems, from what I can tell by console output but I'm not sure whether or not they're related to my running OS X on  non-apple hardware or not. Quite a few of the messages do appear in the apple forums as well.

 

One rather annoying issue is that steam asks for permission (firewall) every time I start it. As far as I can tell, no other app does.

Link to comment
Share on other sites

 Share

×
×
  • Create New...