-
Notifications
You must be signed in to change notification settings - Fork 618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clover Package doesn't work on Catalina #6
Comments
I have the same issue |
Same here.
|
Same here. |
Same here!! |
Same here |
I have the same issue. It does not seem to be version specific. |
Same here |
Can install but the system crashes. It's also made my system very slow |
Sir you are the cause of the error. "Cannot install without ensuring the file system is read-write" means you did not accepted a pre install action that require you to interact into the GUI directly. |
It shows the error shown in the screenshot: https://user-images.githubusercontent.com/220623/66786465-b0ee4100-eee0-11e9-96c2-312c2831f27d.png
No, it's the error that is reported AFTER having entered Administrator credentials. In a nutshell, the installer is unable to get read/write access even if you enter the appropriate credentials of an Administrator account in the dialog shown in the first screenshot: https://user-images.githubusercontent.com/220623/66786460-adf35080-eee0-11e9-9de0-f2352b0d3dc0.png |
Can you post the install log? Just after the error go to menu->Window->Install log |
Sure the install will fail if you run the package from the command line. no way |
So here the log after I entered my administrator account credentials successfully: Oct 19 11:21:37 iMac Installer[58510]: Package Authoring Error: has an unsupported MIME type: image/data Translation in english would be: Oct 19 11:21:58 iMac Installer[58510]: Installation checks failed. Oh oh, same error than the one provided by the user who tried with command line (with sudo and ensuring the FS was mounted read/write before starting the "sudo installer" command) ! Surprising, isn't it ? ;) |
Bruh, Do you think that I didn’t try it through the UI? Right click open, put admin credentials, get same error on EULA screen? |
no surprise if it fails from the command line because there is a check that abort the installation if you did not accept it: `function checkFileSystemIsWritable()
so there is no way you can skip it (i.e. even if the file system was already writable). A failure after giving a correct administrative account name/password can be a bug instead. But the try-catch block should print 'mount -uw / succeded.' when succeded or
|
This bothered you? Simply is not possible from the command line, ad it was the only things visible from your message. Any way from your log, this time I can see an comprehensive and illuminating |
Yes |
Yes |
Ok thanks, that is clear. Usually administrative account show the name while guests or non administrative accounts require to fill both user name and password, why I asked. some other questions: |
I gave you the whole log from the Installer, so I guess no ;)
I'm running the installer from the root filesystem.
I'm trying to install Clover while booted in Catalina from my main SSD (with previous clover). There is no Catalina installation partition or app (nothing in /Applications). |
I found this article on Apple's website that may be useful. |
Returning to this issue .. the bottom line is that the Clover installer seems dysfunctional when used from a Mac running Catalina in that you cannot reach the "click 'Continue' twice" step of the Clover instructions because the installer aborts before offering that option. I presume, since I don't know the intervals of the process, that the Clover installer always checks if it can write to the root volume, even if the user has no intention of doing that (the more common target of the install being a USB stick), when it finds it can't do that it aborts. Apple's article, referenced above, points to the reason for the failure, which is nice to know but doesn't lead to any resolution. So, my questions are: .. is this impacting all Catalina users or only some ? .. can this 'writable root volume' check be avoided ? My personal solution is to use a pre-Catalina Mac when needing to use the Clover installer to set up USB sticks, hardly an optimal solution. |
I just pulled the Clover repo and as @vectorsigma72 notes, the key to this lies in the Installer "Distribution" script in the function Seems like the failure side of that test, instead of making efforts to make root writeable (which can't be successful in Catalina), should work a little harder and look for other writable (bootable?) volumes. Sadly, the last time I messed with Installer scripts was in the Mac System 7 days, so maybe someone with modern Installer skills could do that (or something better). |
Same issue here. Any fix in sight?? |
A fast, but unsatisfactory, fix would be to set |
Thanks gavineadie - Unfortunately I am not very familiar with how to edit the script. Im a film editor just trying to build a hackintosh haha. Any chance you could either share your new package or share some knowledge? thanks! |
As a stranger to this product, I feel reluctant to step in. I don't recommend patching the file in the installer, if it's even possible, because it'll get changed back on the next upgrade. I built the entire installer from scratch but I'm a programmer and familiar with the tools and processes required. I expect this will be fixed soon in a better way than my patch. |
Definitely understand. Appreciate the extra info though! 18 days an no fix though... not exactly holding my breath haha |
Maybe, it's time to move /EFI-Backup folder to somewhere, such as /usr/local/EFI-Backup or ~/EFI-Backup... |
Have the same issue. Any chance for an update? |
This is not an issue of where things are put, it is merely checking that "/" can be mounted writable. If it's not (and it is not in Catalina), the Installer immediately aborts, making the issue of where anything gets put beside the point. |
@gavineadie The purpose of checking "/" is writable is to create /EFI-Backup. |
.. but, if your intention is to create "/Volumes/USB/EFI_Backup", and not touch "/" at all (a not-uncommon usage), the Installer script always aborts before you get to chose the install volume because it prematurely checks the success of |
No. RC Scripts needs that, the Clover preference file needs that as well, and so on. The system knows this and wont start the package because potentially can install in /. |
Hmm that's odd. It seems only confined to the latest version of Clover 5099. I was able to install Clover version 5089 on USB stick with Catalina installer in it. I was able to install it but got a black screen through. |
A similar thing happens when I use Clover.app to install to a removable USB device. It says this:
|
I cloned the repo, did a checkout on the 5100 tag, and hard coded checkFileSystemIsWritable to return true. Built the package and ran it from Catalina and was able to install Clover on a USB drive without issue. They need to update the installer to check the permissions on the selected install volume not the root volume of the system running the installer. |
What steps did you follow to built the package? @bchernicoff |
@bmukheja With the latest xcode and command line tools installed, I just ran the buildme script which will present a menu asking what to build. I believe I chose Build Package but maybe I chose Build All. Sorry, I don't remember exactly. |
Circumvented it by -
|
Can Apple have blocked Clover in Catalina? To protect their system? |
No .. this is a feature of Catalina. It's not only Clover that's impacted .. Finder has the same restriction. |
I fixed this problem with this manual
profit |
Gomsoup's solution worked for me! Thanks! |
Yeah but now you've disabled an important security feature of your Mac. I would re-enable now that you've made the USB drive. |
"Of course I've SIP completely enabled (0x0) ;)." SIP is disabled by Clover as default if you enabled SIP you cannot install some packages |
Sure. What's that got to do with the Apple Mac he was disabling SIP on to run the Clover installer? |
It is not related with Clover and it's development |
and the second thing, no need to use installer to update Clover |
Not a proper solution, but you can partially disable parts of SIP in the Options in the boot screen without disabling SIP altogether. You only need to enable "Allow Unrestricted FS" |
This still doesn't work. So basically Clover simply can't be installed on Catalina? |
On Catalina (OS X 10.15), Clover installer can't get read/write access
Of course I've SIP completely enabled (0x0) ;). I didn't try without SIP, but I don't want to have to disable it each time I need to update Clover
The text was updated successfully, but these errors were encountered: