![]() That seems to work well in the great majority of cases. If you are simply converting the internal boot disk to APFS (or leaving it as HFS+, if a Fusion Drive or hard disk), then there should be no migration stage: High Sierra should install in place, and once complete all your previous settings, documents, etc., should remain. If you need to have access to both Sierra and High Sierra, you are better off running them on separate Macs. I will write more about the problems in an article for tomorrow, but there are problems with file systems, Startup Disk, probably with FSEvents which keeps forcing Time Machine to perform deep event scans or full backups, and more. ![]() Having spent a lot of time trying to create this with my iMac, my experience is that it is very difficult, and a long, slow way to pain and grief. Start up from the internal drive, and you might be running Sierra start from an external drive and you might be running High Sierra. It used to be that many Mac users, who needed to check their work with both the last and current releases of macOS, ran dual-boot systems. Dual-boot Sierra and High Sierra systems are a nightmare You could end up having to restore everything if the conversion goes wrong.Ģ. That seems to have generally gone smoothly on such simple systems, although there is a very real risk of problems and you must ensure that you have at least one really reliable backup. Upgrading a Mac’s internal SSD will – you have no option – convert that from its current HFS+ file system to Apple’s new APFS. The further your Mac departs from that, the more likely you are to hit problems. If you’re upgrading a recent MacBook Pro with an internal SSD and little else attached to it, then the upgrade should be a breeze. Having spent much of the last day installing and reinstalling High Sierra, I offer the following tips for anyone who might be tempted to upgrade.
0 Comments
Leave a Reply. |