![]() ![]() The SSD is not APFS, unless the installer converted it automatically Since the system hasn't run anything but these installers since then, I have no reason to believe the system itself has reset the SIP. I did so successfully at the outset of all of this and I have not reset my PRAM or anything. I also attempted to install a patched HS onto an empty, internal 1TB HDD. ![]() Is there any point in running that command from Terminal from the installer boot drive? I haven’t even been able to get that far to run it. When I did the force rebuild, it told me there’s a command I should run from Terminal after booting into HighSierra. Re-ran both the macOS installer and the post install from that drive and also did the forced cache rebuild again. This time I used a LaCie 1TB, FireWire 800 external HDD. I next decided to try building a new boot drive w/ High Sierra and the patch, on the off chance either the original USB installer was corrupted somehow or perhaps USB 2.0 performance is slow enough to be causing some issues. I turned off the machine and let it sit for a few days and went back to my MacBook Pro while I researched and thought through what’s going on. It’s an SSD, so I can’t listen for any hard drive mechanical movements nor observe any other activity in the background.įollowing the instructions again, I rebooted into the boot USB, ran the post installer again, and this time opted for the Force Rebuild option for the caches. That said, subsequent attempts repeat these problems, so I assume it never gets past 95%. If it ever got any further than that 95%, I wouldn't know since the energy saver came on and turned off the display and wouldn't restore. I also on another attempt let it run overnight and then some - I'd estimate about 11 hours. I've let it run for four hours - occasionally poking the keyboard to keep energy saving off. The display goes into energy saving mode and will not come back up. And then the progress bar started moving to load the rest of the OS. It came up quickly with the password prompt (I run FileVault, so the SSD is encrypted). I then ran the patch's post-install and selected the default options for a 3,1 Mac Pro, and then rebooted into the SSD. I chalked it up to USB 2.0 on a 10-year-old machine being awfully slow by any modern standard, but I’m not so sure that’s the problem anymore. I was surprised that, start to finish, it took literally 34 hours to install. I was running El Capitan and opted to put in High Sierra patch in order to be able to run some newer software I couldn’t run on El Capitan.įollowing his website's instructions, I installed from a 32GB USB thumb drive. Running a 2 TB internal SSD via a PCIe controller (OWC). ![]() I'll include the specs at the bottom of this post. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |