meta data for this page

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
software:macosx [2021/10/10 13:21] – christiansoftware:macosx [2021/10/10 13:29] (current) – christian
Line 33: Line 33:
 ===== Updating/Sys Admin ===== ===== Updating/Sys Admin =====
  
-  * When trying to update my [[https://everymac.com/systems/apple/mac_mini/specs/mac-mini-core-2-duo-2.66-mid-2010-server-specs.html#macspecs2|MacMini mid-2010 version (Server)]] from Yosemite (10.10.5) to High Sierra (most recent version which runs on that hardware) the Installer reported that it was "Unable to unmount volume for repair" and rebooted into the old version. 
  
 +==== Updating a MacMini (2010, server) ====
 +
 +When trying to update my [[https://everymac.com/systems/apple/mac_mini/specs/mac-mini-core-2-duo-2.66-mid-2010-server-specs.html#macspecs2|MacMini mid-2010 version (Server)]] from Yosemite (10.10.5) to High Sierra (most recent version which runs on that hardware) the Installer reported that it was "Unable to unmount volume for repair" and rebooted into the old version.
 +
 +I had replaced the original disks with a 500 GB SSD from OWC and apparently there are issues with the High Sierra installer (by default the file system will be converted to AFPS from HFS+). There seem to be a few people running into the same issue.
 +
 +Some user on [[https://apple.stackexchange.com/questions/299976/cannot-upgrade-to-high-sierra-unable-to-unmount-volume-for-repair|the Apple Stackexchange]] reported a relatively lengthy routine to circumvent the issue for an iMac with Fusion Drive. On the Apple Support pages, [[https://discussions.apple.com/thread/8086126?answerId=32651341022#32651341022|a much shorter version]] was posted which amounts to issuing the following commands as ''sudo'' on the drive where the installer is run:
 +
 +<code bash>
 +sudo mv /.quota.ops.user /.quota.ops.user.orig 
 +sudo mv /.quota.user /.quota.user.orig
 +</code>
 +
 +(have changed/fixed? the filenames from the original post)
 +
 +After these files were moved out of the way, the installer seems to be running fine.