November 23, 20178 yr 11 hours ago, John_M said: It isn't there by default with either High Sierra 10.13.1 or Sierra 10.12.6. Something must have installed it there on your Mac. By default there is a symlink called /usr/lib/libssl.dylib which points to libssl.0.9.8.dylib in the same folder. On a fresh macOS installation there is no /usr/local/ssl folder and no /usr/local/opt folder either. It goes without saying that I get the same error message, too. That is entirely possible i have been running the same migrated osx to osx.... to macos to macos for about 10 years.
November 23, 20178 yr On 11/9/2017 at 5:43 AM, disruptorx said: I think I stuffed up my installation , luckily I backed up the USB.. However when I try to run the MacOS version it gives an error . On 11/21/2017 at 11:03 PM, Can0nfan said: I have downloaded this for MacOS and am on 10.13.1 (High Sierra) I cannot get it to run i get same error as @disruptorx 23 hours ago, John_M said: It isn't there by default with either High Sierra 10.13.1 or Sierra 10.12.6. Something must have installed it there on your Mac. By default there is a symlink called /usr/lib/libssl.dylib which points to libssl.0.9.8.dylib in the same folder. On a fresh macOS installation there is no /usr/local/ssl folder and no /usr/local/opt folder either. It goes without saying that I get the same error message, too. I updated the unRAID USB Creator for macOS which should fix the libssl dependency path on all OS versions. The link to the new version is the same, see the first post in this thread for the url. Also, macOS gatekeeper shouldn't complain that it's from a unidentified developer any more with this new version.
November 23, 20178 yr 1 hour ago, eschultz said: I updated the unRAID USB Creator for macOS which should fix the libssl dependency path on all OS versions. The link to the new version is the same, see the first post in this thread for the url. Also, macOS gatekeeper shouldn't complain that it's from a unidentified developer any more with this new version. The macOS application now launches but I get the following error when I try to quit it: It looks as though it's trying to store it's persistent data to an invalid path. /var/root does exist but it is owned by root:wheel and has mode 750 and therefore isn't accessible to ordinary (including admin-privileged) users. The macOS standard would be to store such data at ~/Library/Saved Application State/com.limetech.unRAIDUC.savedState/window_1.data if its purpose is to allow the application to persist across an OS reboot. If the application simply wants to store information between one launch and the next it would be more appropriate to put it in a folder such as ~/Library/Application Support/com.limetech.unRAIDUC/
November 23, 20178 yr 1 hour ago, John_M said: The macOS application now launches but I get the following error when I try to quit it: It looks as though it's trying to store it's persistent data to an invalid path. /var/root does exist but it is owned by root:wheel and has mode 750 and therefore isn't accessible to ordinary (including admin-privileged) users. The macOS standard would be to store such data at ~/Library/Saved Application State/com.limetech.unRAIDUC.savedState/window_1.data if its purpose is to allow the application to persist across an OS reboot. If the application simply wants to store information between one launch and the next it would be more appropriate to put it in a folder such as ~/Library/Application Support/com.limetech.unRAIDUC/ I just tried it and did not have the same issue.
November 24, 20178 yr OK. Here's what happens when I start from scratch. I download the application and install it into the /Applications folder. Then I launch the application and it opens a dialogue box with a password request so that it can make changes (presumably a requirement for it to be able to write to a USB flash device). I enter my password and click OK. The dialogue box closes and the main window opens and I see a second lime icon appear on the Dock. The original icon, if I right-click on it, shows "Application not responding"; the new one is associated with the new window. In the main window the options seem to work - I can click the Customize button, etc. If I click the Close button I get "unRAIDUC quit unexpectedly". If I click "Ignore" I get the error message, mentioned above. This is on a MacBook Pro running macOS Sierra 10.12.6. Now, if I switch to a MacBook running macOS High Sierra 10.13.1 and download a fresh copy of the application it behaves in exactly the same way, up to the point when I click on the Close button of the main window and get the "unRAIDUC quit unexpectedly". If I click "Ignore" I get a different error message: However, once I've clicked OK to close the application and then relaunched it, it works from then on with High Sierra. So it seems the initial launch is problematic but subsequent launches work ok.
December 22, 20178 yr Worked like a champ on Windows 10. Created USB drives with this utility all with the latest bleeding edge stuff.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.