Create-Recovery-Partition-Installer
Create-Recovery-Partition-Installer copied to clipboard
Corrupt Recovery Partition created from 10.12.5
Creating a recover partition installer using the 10.12.5 version of "install Sierra.app" results in a working installer, but when installed the partition created seems to be corrupt. When I run diskutil list the created partition that should be Recovery HD has no name, and can't be mounted even using diskutil mount readOnly command.
Hello Chris, I come across the same issue in any macOS 10.12 version, this is due to SIP and not the tool itself.
Curious. It worked for me under 10.12.4... :-(
strange, I successfully created a 10.12.5 recovery HD this morning. installer creates working recovery HD's, not seeing the issues mentioned here at all.
When I install a 10.12.5 Recovery partition created by this app it creates a partition with no name and FileVault fails to enable.
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500.3 GB disk0
1: EFI 209.7 MB disk0s1
2: Apple_HFS Macintosh HD 499.4 GB disk0s2
3: Apple_Boot 650.0 MB disk0s3
Also having issues with 10.12.5 getting a lot of permission errors Running it as an admin
Checking /Applications/Install macOS Sierra.app…
2017-07-11 10:32:54.053 hdiutil[73185:1313106] kCFURLVolumeIsAutomountedKey missing for file:///private/tmp/DSNetworkRepository/: Error Domain=NSCocoaErrorDomain Code=257 "The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it." UserInfo={NSURL=file:///private/tmp/DSNetworkRepository/, NSFilePath=/private/tmp/DSNetworkRepository, NSUnderlyingError=0x7faad8603ba0 {Error Domain=NSPOSIXErrorDomain Code=13 "Permission denied"}}
hdiutil: attach failed - Resource busy
Found Mac OS X 10.12.5 16F73 © 1983-2017 Apple Inc..
2017-07-11 10:32:55.333 cocoaDialog[73201:1313140] kCFURLVolumeIsAutomountedKey missing for file://localhost/private/tmp/DSNetworkRepository/: The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it.
2017-07-11 10:32:55.346 cocoaDialog[73201:1313142] kCFURLVolumeIsAutomountedKey missing for file://localhost/private/tmp/DSNetworkRepository/: The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it.
2017-07-11 10:32:55.388 cocoaDialog[73201:1313209] kCFURLVolumeIsAutomountedKey missing for file://localhost/private/tmp/DSNetworkRepository/: The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it.
2017-07-11 10:32:55.390 cocoaDialog[73201:1313209] kCFURLVolumeIsAutomountedKey missing for file://localhost/private/tmp/DSNetworkRepository/: The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it.
2017-07-11 10:32:55.392 cocoaDialog[73201:1313209] kCFURLVolumeIsAutomountedKey missing for file://localhost/private/tmp/DSNetworkRepository/: The file “DSNetworkRepository” couldn’t be opened because you don’t have permission to view it.
Cancelled!
I had the same problem as @damacguy and @mcclint680 but was able to get it to work by disabling SIP first. Had to reboot into recovery using Internet recovery though because of course I did not have a recovery partition!
FileVault works now too.
I don't think it's SIP. I created an installer using this machine with SIP enabled and running 10.12.5, and installed the recovery partition on it using that installer. If it was 10.12.5 or SIP, this wouldn't have worked.
I was able to get it to work on 10.12.6 only after I disabled SIP, thanks @kane-c for the tip.
Wondering if the difference between @elvisizer and @kane-c's results is related to CoreStorage/Fusion drives.. what kind of hardware are you all running on?
Mid 2015 MBP with stock SSD.
encrypted SSD, so it is a core storage LV. still never seen what Kane's running into.
On Thu, Oct 19, 2017 at 3:33 PM, Kane [email protected] wrote:
Mid 2015 MBP with stock SSD.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/MagerValp/Create-Recovery-Partition-Installer/issues/7#issuecomment-338056545, or mute the thread https://github.com/notifications/unsubscribe-auth/ABCMD8ZHtIVt5xP1sOWIhGcHJJ0W26gCks5st84ogaJpZM4NgvA1 .
I'm trying to create a recovery partition on a 10.13.6 (High Sierra) system. I've disabled system integrity permission, and run the installer script as root (to get it to run). The recovery partition has not been created. However here what I believe are the core details from the installer log.
Sep 2 17:56:06 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition populateBooter:verifyType:verifyMinSize:clearMode:copierForRecoveryFiles:hostOSXForBootRootFiles:statusReportingDisk:percentBegin:percentEnd:]: inPartitionUDS=0x70000590d520=disk0s4 inVfyType/MinSize=Apple_Boot/650002432 inClearMode=Format inRecCopier=0x7ffc34e08760 inBRHostMP=/ inStatusDisk=0x7ffc34e176b8=disk0s2=Macintosh HD inPct=63..87 Sep 2 17:56:06 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition populateBooter:verifyType:verifyMinSize:clearMode:copierForRecoveryFiles:hostOSXForBootRootFiles:statusReportingDisk:percentBegin:percentEnd:]: retErr=-69771 Sep 2 17:56:06 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition ensureBooter:storage:phyUDS:logUDS:phyREF:logREF:copierForRecoveryFiles:hostOSXForBootRootFiles:recBSD:percentBegin:percentEnd:]: retErr=-69771 outDisk=(null) Sep 2 17:56:06 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition ensureRecoveryPartitionForVolume:]: at exit; err=-69771 Sep 2 17:56:06 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition ensureRecoveryPartitionForVolume:]: output recoveryDiskBSD=(null) physicalDonorBSD=disk0s2 Sep 2 17:56:07 iMac diskmanagementd[208]: diskmanagement: [DMToolRecoveryPartition ensureRecoveryPartitionForVolume:] Sep 2 17:56:07 iMac installd[329]: ./postflight: ->-[Local dmAsyncProgressForDisk:barberPole:percent:]Error (async): The target disk is too small for this operation (-69771) Sep 2 17:56:07 iMac installd[329]: ./postflight: : del callback: DADR=0x7f915b516bc0=disk0 pole/pct=0/53.500000
It's a 500GB HDD. And only has the OS on it. So target disk too small is wrong. Something is confused. I need to look at the script for postflight.
- David