Closed samspade21 closed 5 years ago
I had this same issue (and I am still investigating the cause), but downgrading restor to v1.6 resolved the issue for me.
in my experience, if I tried to image it with anything less than 10.13.6 I got this issue.. Only thing that worked for me was to use a build based on 17G2112 build and not the 17G65 Build of 10.13.6. Hopefully this helps
On Aug 14, 2018, at 10:53 PM, Dustin Davis notifications@github.com wrote:
I had this same issue (and I am still investigating the cause), but downgrading restor to v1.6 resolved the issue for me.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/restor/issues/45#issuecomment-413078652, or mute the thread https://github.com/notifications/unsubscribe-auth/AC9b571tr8SwEgxaA026olOkIrj-wwwzks5uQ40mgaJpZM4V9MFZ.
When using v1.7 does the bundled and cached version of the helper tool match?
md5 /Applications/Restor.app/Contents/Library/LaunchServices/com.google.corp.restord /Library/PrivilegedHelperTools/com.google.corp.restord
If not, or just because, you can try deleting the cached version.
sudo rm /Library/PrivilegedHelperTools/com.google.corp.restord
@tburgin Above step to remove cached version worked. Using 1.7 was able to:
Using v1.6 and image 10.13.6 17G65 also did not work
Thanks for the heads up and hope this help on next release
Completely removing the helper tool solved this stuck at "Starting..." issue for me as well.
When using Restor on a MacBook Pro (13-inch, 2018, 4 TBT3) or a MacBook Pro (15-inch, 2018) trying to restore an APFS image (10.13.6 for example), Resor sits at a "Starting..." prompt. This is using multiple different machines running Restor, all running 10.13.4 or 10.13.6. Using Disk Utility to blow away the drive and restart does not make a difference. Happy to send any log files, please let me know which ones would be most beneficial.