![]() ![]() The ideal setup would be to actually unplug your main drive, followed by trying to boot from your backup drive, but if you are unable to do this (e.g. To make sure your backup drive is indeed bootable you should test this out. Step 1.3: Confirm your backup drive is bootable Don't copy things over before you make absolutely certain your configuration works properly, or things will go bad if you ever need to boot from the backup drive of course. You should do this every time you have made changes/updates to your Clover/boot configuration that are confirmed to be working, to ensure you will always have a working bootable backup. To do this, mount both your main drive's EFI partition as-well as your backup drive's, and simply copy the EFI folder over. To ensure your backup drive is also fully bootable, you need to copy your working Clover configuration over as-well. Step 1.2: Copying over your EFI partition Fortunately pretty much every single motherboard supports booting from USB these days, so you should be fine there. macOS has no trouble booting from external drives, so long as your hardware supports this. Note: This is also entirely possible by using an external (USB) hard drive. The SuperDuper! screen after finishing cloning my main drive over to a backup drive. However, for me using one of these tools has a few benefits that make it easier to use, and if you decide to purchase either of them they can even ensure more up-to-date backups by letting you schedule them automatically. You can also use CarbonCop圜loner, or if you're comfortable with the command-line even dd will do the trick. Every now and then I use SuperDuper! to clone my entire main drive over, and do this every time before doing a macOS update. In my case I have an internal 500GB 7200rpm hard drive that I use as a clone of my main Samsung EVO 960 500GB SSD. This way if you ever make an oopsy on your main drive, you can use the secondary drive to boot right back up, fix whatever is broken, and reboot back from your main drive. The absolute best way to ensure you're never kicked out of your Hack, losing many hours of productivity (or fun) having to try to get things to work again, is to have a secondary hard drive (or SSD) that is bootable. ![]() If you don't already have a bootable backup drive, you might want to start with this now. While these steps are not required, I do think it's a good method as it ensures your Hack is as up-to-date as can be. I take the opportunity to also update Clover and any Kexts that might have an update. This guide will cover the steps I usually take when updating my Hackintosh. Please check out the article if you came here looking information on upgrading to Catalina. I have written up a few thoughts regarding upgrading to Catalina. Update: This process still works perfectly up to and including 10.14.6, the recent-most version as of this update (). The former is important as newer updates often come with bug fixes, security updates and more good things, and the latter is to give the community as a whole a chance to check out any and all new versions to see if something perhaps more drastic has changed, requiring some additional work. using the Vanilla method, relying on as few custom Kexts as possible, and properly setting up things like your USB ports), it is always recommended to both keep your machine as up-to-date as possible, and at the same time not jumping on new updates day-one. Though this is much less of an issue if you have properly set up your Hackintosh (e.g. Even if there's some update when you have OS up and running on next boot it will update OS without digging through UEFI GUI to select proper file.One of the possible challenges with using a Hackintosh is having to deal with OS updates. It's "dirty" solution but I think it might work. If it's not, it will say no map/file to execute and continue to next step where you call regular boot.efi as usual. If it's there, it will start upgrade process (most of the time it's 2nd phase) and ignore rest of the script. In short, boot process would go like this:Ĭall install efi file from MacOS Install map on destination drive. If it's not install phase, it will show error but continue to next boot image you specify (that exists). If there's install phase, it will boot file and continue with update/upgrade. You can even place calls to specific boot.efi images (Install phase, normal phase). I didn't check in depth what steps does your program do, but from my point of view you could incorporate steps (at some point after initial MacOS install step - when everything is created on virtual drive) to mount EFI partition, copy needed drivers and script, restart and let the script take over. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |