Jump to content

wormyrocks

Members
  • Content count

    46
  • Joined

  • Last visited

About wormyrocks

  • Rank
    InsanelyMac Protégé
  1. Hi all - I abandoned my El Capitan install and decided to roll back to Yosemite, so I restored my OS SSD from a backup without a hitch and it can now boot fine. However, when I try to boot with my user data HDD (which contains only my home folder) plugged in, for some reason as soon as the BIOS splash screen passes, the screen goes black and it won't let me do anything at all. I've tried fiddling around with the BIOS settings to see if it's trying to boot from the data drive or something like that, since I know that at some point a recovery partition got installed on the hard drive, but to no avail. I've made sure that the boot order prioritizes the operating system on the SSD as well. No other SATA devices are plugged in except for the optical drive. I've tried the hard drive in a USB SATA interface with a different computer and I can view all my files, so it isn't corrupted or anything. Any help would be much appreciated; since I'm restoring to an earlier install I suspect that as soon as I figure out what is causing this I will be up and running again. Specs: i5-3570K GTX 560 GA-Z77M-D3H-MVP 128G SSD/1TB HDD Thanks in advance!
  2. Trouble upgrading to El Capitan

    After putting, alternatingly, AptIoFix and AptIoFix2 on the EFI installer partition, neither convinces the boot error message to change. For good measure, I made a USB drive with the OS X installer and put Clover on it, making sure the OsxAptioFixDrv patch was selected in the installation, and tried to boot from that... it still gave me the same error as the auxiliary EFI partition did. Kind of at a dead end now. Alternatively, I have no need to upgrade this machine to El Capitan - if anyone can help me troubleshoot the persistent network and sluggishness issue that the 10.10.5 upgrade brought, I'd be more than happy to just nuke the El Capitan EFI partition and stick with that.
  3. Trouble upgrading to El Capitan

    Thank you! How would I go about getting the driver installed on the EFI partition that the El Capitan installer creates?
  4. Hi all, I just installed the update for OS 10.10.5 from Apple, and the installation ostensibly completed successfully, but upon boot I am greeted with an extremely slow operating system. I believe the core problem is now with the networking - I can log into my local wi-fi, and Ethernet works, but the Internet connection cuts out intermittently regardless of whether it is wired or wireless (this never happened before) and Chrome, Safari, and any application that uses the Internet runs very, very slowly and crashes frequently upon launch. Additionally, Console is sending like 10 error messages per second, all of them related to Internet-connected services failing to work. Finally, iTunes hangs and crashes about 10 seconds after launch, regardless of whether wi-fi is turned on or off. This is the real dealbreaker here since I mostly use my desktop as a media server at this point. I decided that I might as well update to El Capitan and then fix all my problems then, but unfortunately my Mac was unable to connect to the App Store with the intermittent connection (I assume it's dropping many packets or something of that nature). So I downloaded the El Capitan installer on another machine, transferred it to my hack, and followed the instructions that can be found by searching a certain site I won't name for "Direct Update to OS X El Capitan Using Clover". Unfortunately, upon attempting to boot into the "Install Mac OS X" partition, I got the little round "no" sign, which verbose mode revealed to be an "OsxAptioFixDrv: requested memory exceeds our allocated relocation block" error. Google + common sense tells me that the next step would be to apply the OsxAptioFixDrv patch from Clover Configurator, to the "Install Mac OS X" EFI partition. However, although my Yosemite install is still functional, the aforementioned internet connectivity issues means that Clover Configurator cannot connect to the server to download said patch, and I can't for the life of me figure out a. where on the Internet I can download that patch and b. how I might be able to install such a patch manually. I figure the best thing to do would be to update to El Cap and then work from there, but if anyone knows what might be up with my Internet connectivity issues, help with that would be much appreciated as well. Thanks! Specs: i5-3570k, Zotac GTX 560, 8GB RAM, Gigabyte GA-Z77M-D3H-MVP
  5. Migrating Windows install to a new drive

    Setting the SATA mode to AHCI fixed things, everything works now!! Thanks again for all your help!
  6. Migrating Windows install to a new drive

    Update! So, I decided to go for broke, wipe my SSD and install Yosemite on it... I'm now more lost than before. I wiped the SSD with a GPT scheme and installed Yosemite from the Clover drive, set up exactly as described in the guide - the only difference being that I copied my existing config.plist and a few kexts (sound, Ethernet) besides FakeSMC. I then booted into the install to make sure that it worked, went through the OSX setup procedure, gazed upon an empty desktop from a fresh install, then booted from my Time Machine drive and restored everything. So far, so good. I booted into my desktop environment with only the solid-state plugged in; it seemed to have restored my partition, but since my user folder is on my Mac Files drive I couldn't actually log in. In any case, at this point it booted, so that means that the OS files on the solid-state drive were (at least mostly) shipshape. So I went to plug things back in. Here's where things get hairy. I realized that all my SATA3-capable drives had been plugged into SATA2 ports for the last three years, so I re-plugged them into my SATA3 ports. While I was doing so, I must have accidentally bridged the restart pin on my motherboard, because the machine booted and said that my BIOS settings had been erased. (By the way, my motherboard is a GA-Z77M-D3H-MVP with an i5-3570k). I changed the BIOS settings back according to an easily-googleable guide on a site whose name I won't mention and then tried to boot from the solid-state again, but booting halted and I got the big "circle with slash through it" sign in the middle of the boot sequence. I tried again with various boot options that I remembered having had an impact in the past (albeit on Chimera). Nothing. I went back to the SATA2 port. Same thing. Tried different cables and different SATA ports on the motherboard. Nothing. The system was booting from Clover (interestingly, only the Clover installed on the flash drive; it couldn't boot directly from the SSD) recognizing the drive, loading some files and then crashing. Here's where things get really weird. I decided to just wipe and start again, so I booted up from the flash drive and opened DU. DU could not recognize the solid-state drive. It completely did not acknowledge that it was even there. The BIOS disagreed; according to its boot drive options, it was completely aware of the SSD's presence and all its partitions. At this point you're probably thinking that I fried my solid-state drive with ESD. While I wouldn't rule it out at this point, I think it's unlikely. I have a SATA->USB interface adapter, and I used it to connect the solid-state to my roommate's laptop. It mounted just fine and I could access all my files. From the other laptop, I decided that my best bet was to wipe the disk again and plug it back into the desktop to try and reinstall the OS. I formatted and unmounted the drive without any problems and plugged it back into the desktop; Disk Utility still didn't see it, and as expected it had disappeared from the Clover boot screen as well. At this point, my best guess would be that the issue is some errant setting in the BIOS or the Clover settings that I forgot to turn on in order to allow the Yosemite install USB to recognize the internal hard drive. It's that or ESD-induced HW failure of the motherboard and/or the solid state, so I'm hoping against hope that it's the former. If it is hardware failure, it's a very weird one, because Clover as loaded from the flash drive could still mount and read the solid-state drive, just not boot all the way from it. I guess my next step now will be to check my other hard drives and see if they are okay/can be read by the Yosemite install. If need be I can wipe them since I'm fully backed up. But IIRC they had just been plugged in when I accidentally reset the motherboard so there's a chance they could have been damaged. Any advice would be greatly appreciated.. thanks.
  7. Migrating Windows install to a new drive

    Hmm, that is odd, because I have never cloned the contents of the SSD. But I suppose i will if I have to. I'm just terrified of losing my working installation, especially given how questionably reliable drive cloning is in my experience. I remember jumping through some hoops when I first set up the dual booting - like installing Windows first and then putting OS X on the secondary partition. Possibly that's why I can't reclaim the space on that partition. Well, I'm warming to the idea of wipe and refresh, but I figure I'll try the partition conversion before I go for broke, assuming that'll eventually help me reclaim the empty space. Does the first entry in post #359 of the thread you linked have the relevant instructions? Is there any chance of those instructions working given that they refer to starting with a hybrid drive rather than a pure MBR table? I'm also absolutely mystified by the fact that I have an EFI partition on /disk1. I've never booted off that drive, ever.
  8. Migrating Windows install to a new drive

    Well, that's the thing... I think it's actually the output for the solid state. GParted lists it as /dev/sda1, and it says that it has a 56 GiB capacity in the middle of the text. What constitutes installing an OS in UEFI mode? Does EFI require GPT to work properly? Also, weird problem: after deleting the old Windows partition, when I select my SSD for startup, the screen hangs for a few seconds and then kicks me back to Clover. When I select it again, it boots fine... but I always have to hit the boot drive twice in order to successfully get into the OS. I have absolutely no idea what could be causing this. Here is the output of diskutil list: ➜ ~ diskutil list /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *120.0 GB disk0 1: Apple_HFS MacSystem 60.1 GB disk0s1 /dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS MacFiles 999.9 GB disk1s2 /dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: FDisk_partition_scheme *1.0 TB disk2 1: Windows_NTFS Windows System 940.1 GB disk2s1 ➜ ~ And here is the fdisk output: Enter 'help' for information fdisk: 1> p Disk: /dev/disk0 geometry: 14593/255/63 [234441648 sectors] Offset: 0 Signature: 0xAA55 Starting Ending #: id cyl hd sec - cyl hd sec [ start - size] ------------------------------------------------------------------------ 1: AF 1023 254 63 - 1023 254 63 [ 2 - 117469176] HFS+ 2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 3: 00 0 0 0 - 0 0 0 [ 0 - 0] unused 4: 00 0 0 0 - 0 0 0 [ 0 - 0] unused Thanks again for all your help, it is much appreciated. Also, I should add, this is on top of a 100% clean installation of Clover. I installed it over Chameleon around when Yosemite came out and I was so shocked and happy that it worked the first time it booted that I didn't even learn how to install new kexts. I am sure there's a lot of stuff that I could be doing to optimize this machine that I'm not doing, but I don't really remember how to safely take care of a hackintosh (my build was over three years ago) and so now I'm terrified of screwing it up.
  9. Migrating Windows install to a new drive

    Okay, so I was able to remove the Windows partition with GParted, but neither it nor Disk Utility wants to let me resize my Mac partition. I get the following error message when poking about with Gdisk: https://www.dropbox.com/s/eisg520vqthaozk/IMG_20150625_183157.jpg?dl=0 What steps should I take to resize the partition? I'm happy to convert to GPT if it is relatively risk-free from my current state. Thanks again! Edit: Also, while I'm at it, would it be worth my while to convert my MBR Windows disk to GPT as well?
  10. Migrating Windows install to a new drive

    Thanks again - so it isn't an issue that the partition tables overlap? That just happens because I'm running my OS off the drive? I am writing gparted to a flash drive now; hopefully this should fix things. thanks!
  11. Migrating Windows install to a new drive

    Thank you! One last question before I run this; my laptop just got stolen so my hack is my primary machine at this point; it's backed up but I really don't want to go through the trouble of reinstalling everything if something goes wrong. I'm getting this message; is this what I should be expecting? Any other steps I should be taking? Warning: Devices opened with shared lock will not have their partition table automatically reloaded! Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: not present *************************************************************** Found invalid GPT and valid MBR; converting MBR to GPT format in memory. THIS OPERATION IS POTENTIALLY DESTRUCTIVE! Exit by typing 'q' if you don't want to convert your MBR partitions to GPT format! *************************************************************** Warning! Main partition table overlaps the first partition by 32 blocks! You will need to delete this partition or resize it in another utility. Warning! Secondary partition table overlaps the last partition by 33 blocks! You will need to delete this partition or resize it in another utility. Thanks again.
  12. Migrating Windows install to a new drive

    Before I go through with this, is it safe to recreate the partition table on the SSD on the Mac while I am booted into the operating system that resides on that partition table? Also, am I going to need to reinstall Clover following this procedure? Thanks!
  13. Migrating Windows install to a new drive

    Thank you! I disconnected the drives and performed the startup repair... now when booting to the new drive it tells me that "my copy of Windows is not genuine". Edit: reassigned the drive letter and now the machine acknowledges that it is genuine... a little bit of slowdown but I'm assuming that'll go away eventually. Or I'm just not used to booting from a hard drive. Edit: Okay, now that I've verified the install is working, I need to nuke the Windows System partition on my solid state... Disk Utility says it can't do it because the drive is MBR. Is there any way around wiping and restoring the solid-state drive with only one partition? I'm not sure if my OS X install will survive something like that...
  14. Migrating Windows install to a new drive

    The only problem is that Clover is located on the EFI block of the solid state drive. Should I try to boot to the install media straight from the BIOS boot menu? Will that work? Also, I no longer have the install disk. Is there a way for me to do it from within Windows?
  15. Hi all, After one too many "Your hard drive is running low on space" messages I decided that it was time to stop running my OS partitions off two halves of the same 128GB SSD. So I bought and installed a separate 1TB hard drive and cloned my Windows 7 install from a 60GB partition of my solid state drive onto the hard drive using Macrium Reflect. I've been able to boot into my Mac or Windows partitions over Clover, but now Clover presents me with two Windows boot drives (I'm expecting this, given that I have two supposedly identical Windows installs on separate drives). However, whichever one I pick boots me into the same Windows install; the one currently located on the SSD partition. The eventual intent is to nuke the Windows partition on the SSD in order to free up space for my OS X install that currently lives on the other half. I've tried unplugging the solid state drive to try and force the machine to boot from the new hard drive, but unfortunately it has the EFI partition on it and so Clover won't even start with it unplugged. I think I'm probably missing something in Clover settings that would allow me to boot into the remaining hard drive, but I can't for the life of me figure out what it is, especially because the new hard drive should in theory be an exact copy of the partition it's going to replace. If it matters, the machine had been running Chameleon-based bootloaders since 2012, but a few months after Yosemite came out I installed Clover over it, changing pretty much no settings, and it's been running reasonably smoothly ever since. So I'm running this on top of a pretty much stock Clover install. I'd appreciate any and all tips that people might be able to offer! I got really into the Hackintosh scene about three years ago, but I haven't kept up with the technology as it's advanced since I've been running a fairly stable machine for quite a while and every time I try to upgrade something I end up breaking it.
×