OpenCore Legacy Patcher

[alecmac1501]

after formating usb with ( mac os extended journaled ) and scheme with ( Guid patition map ) and big sur installer downloaded , I want to select the usb to create macos usb installer but I get ( NO DISKS FOUND )

PS: I tried many usb's
I read time ago that I have to chang usb name to something but I forgot it

any help?

 

[Bigwaff]

Just follow the instructions and you should be fine

Download and build macOS Installers | OpenCore Legacy Patcher

 

[alecmac1501]

thank you for replay, but I know this tutorial 100% but when I want to choose the usb he does not see usb and get NO DISKS FOUND , while usb is shown up in desktop and in the disk utility !!!

 

[alecmac1501]

I am sure that I have to change the usb name to something like ( MacOS X Base System or ........ ) something like that.
it is very simple and I used it in the past before many times with succes but I forgot it 😔😔😔

 

[Bigwaff]

Did OCLP app format your USB or did you? If you did format, you did it wrong.

 

[DeltaMac]

There would be no requirement to rename your USB drive. (the MacOS Base System name is used by the recovery system, so, in any case, would not be one that you would choose.)
Of course, you can name a drive that you have erased -- anything you like. The task of making the bootable USB installer will name it again, so whatever name you choose will ultimately be replaced. And, you can always name it something else, after you create the bootable installer. (I use a name on bootable installers made of special characters and accents, so I have no confusion about the drive when it appears in the middle of some other drives that might have multiple mounted partitions - just something that I do

But, when you have erased the drive, try ejecting that new disk after the format is complete, unplug it from your Mac, then reinsert for a fresh mount. That should help you.

 

[alecmac1501]

( Bigwaff ) I work more than 20 years in pc and macs repaire and installation and I know how to formate disks in windows and in mac.
( DeltaMac ) I have to change usb name ONLY to be shown up in OCLP to choos it , but when the progress begin the name will ultimately be replaced again with success..

 

[steve123]

Yeah, there is some weirdness going in. I have a Mac Mini 7,1 that does something like this. I cannot get the USB drive with the installer to appear in the boot picker. In fact, I have a hard time getting the boot picker to work. I am wondering if it is a USB power issue or maybe some kind of conflict with another usb device or maybe the EFI and/or firmware is messed up.

 

[alecmac1501]

I AM IN THE FIRST STEP :in my case I cannot put the big sur installer app or any other system on the usb because OCLP cannot see the correct formated usb and give ( NO DISKS FOUND ) , while usb is shown up in desktop and in the disk utility !!!

 

[steve123]

Is your USB disk partitioned? OCLP will not install on a partition. You must use the installer in the bundle to install to a partition.

 

[alecmac1501]

no , usb is not partitioned

 

[steve123]

Try using the installer in the bundle?

Create a bootable installer for macOS - Apple Support (CA)

Use an external drive or secondary volume as a startup disk from which to install macOS.

support.apple.com

 

[lucianosipriano88]

I'm having the same problem..
No disk Found

Did you manage to solve the problem?

 

[lucianosipriano88]

Try using the installer in the bundle?

Create a bootable installer for macOS - Apple Support (CA)

Use an external drive or secondary volume as a startup disk from which to install macOS.

support.apple.com

I already tried, but without success

 

[DeltaMac]

I already tried, but without success

What part was not successful?
First, were you able to create the bootable installer?
Then, you also need to follow the steps to modify the EFI partition (which is what you do if the OCLP, then Build and Install OpenCore.
Finally, you have to choose the EFI partition first when you boot to your bootable installer, THEN (and only then) you will see the installer partition correctly to continue with the boot. (Remember, you are booting to a version of macOS that is NOT compatible with your Mac. When you see the bootpicker screen, you have to choose the EFI partition first, as that forces your Mac to boot from the installer that you have decided to use to upgrade your older Mac...)
Is that different from what you see on your own Mac?

 

[Gershwin]

I'm experiencing the exact same issue as alecmac1501.

OCP (I've tried all versions from 1.5.0 back to 1.3.0) is showing "No disks found" when attempting to create an install disk from the "Create macOS installer" menu.

However, if for the sake of testing I try to "Build and Install Opencore" and select "install to disk," the USB drive is shown in the list of disk options.

So, the USB drive is not at fault, the "Create macOS installer" function is.

 

[eltiotito]

Hi friends.
I had the same problem. I try diferents ways to fixed (re-format usb drive, change usb drives, create partitions, delete partitions, change from GUI to MBR), nothing worked. But, a simple thing works, I just change the usb port where I had connect the usb drive. Is working for me.

 

[calphool99]

I *think* I know what's going on. I looked at the github code for OCLP. The code that is running when you click on Create MacOS Installer / Use Existing Mac Installer / {some installer you downloaded } / Select Local Disk can be found in the function list_disk_to_format() in support / macos_installer_handler.py. The code is invoking diskutil as a child process and capturing its output and gathering up what the utility reports as if it had been run on the command line. It first makes sure that at least one of the disks is big enough to hold the installer, and eliminates any disks that aren't big enough (that wasn't my problem, it was getting past that). However, THEN it seems like it tries to use the fact that the diskutil is supposed to report "external" for the USB device. Mine however is reporting "internal" for both my SSD and the USB I have plugged in. So this code seems to be using an unreliable method to determine if the device is a USB device (namely the fact that diskutil usually [though apparently not always] reports it as "external"), as referenced here:

External USB's are appearing as "Internal… - Apple Community

discussions.apple.com

I bet everyone who is running into this problem is the same as me -- their USB device is reported in Disk Utilities as "Internal Physical" so the code refuses to include it in the list of available USB devices.

So now what to do? Not sure. I don't exactly know why diskutil is reporting a USB device as "internal." Interestingly enough, when I plug the USB stick into my other USB port, or into a hub, it suddenly appears as "external" and then seems to work just fine in OCLP. I think there needs to be an override button on that screen or something for people who are running into this weirdness (like "I know how to select a USB device, quit trying to protect me from myself"), *OR* rather than dinking around with diskutil, why aren't they just reporting the devices listed in /Volumes? Maybe there's some reason, but the bottom line is that there's a bug in OCLP that isn't taking into account the fact that sometimes USB devices are being reported by diskutil was internal devices.

 

[Marvyb]

I *think* I know what's going on. I looked at the github code for OCLP. The code that is running when you click on Create MacOS Installer / Use Existing Mac Installer / {some installer you downloaded } / Select Local Disk can be found in the function list_disk_to_format() in support / macos_installer_handler.py. The code is invoking diskutil as a child process and capturing its output and gathering up what the utility reports as if it had been run on the command line. It first makes sure that at least one of the disks is big enough to hold the installer, and eliminates any disks that aren't big enough (that wasn't my problem, it was getting past that). However, THEN it seems like it tries to use the fact that the diskutil is supposed to report "external" for the USB device. Mine however is reporting "internal" for both my SSD and the USB I have plugged in. So this code seems to be using an unreliable method to determine if the device is a USB device (namely the fact that diskutil usually [though apparently not always] reports it as "external"), as referenced here:

External USB's are appearing as "Internal… - Apple Community

discussions.apple.com

I bet everyone who is running into this problem is the same as me -- their USB device is reported in Disk Utilities as "Internal Physical" so the code refuses to include it in the list of available USB devices.

So now what to do? Not sure. I don't exactly know why diskutil is reporting a USB device as "internal." Interestingly enough, when I plug the USB stick into my other USB port, or into a hub, it suddenly appears as "external" and then seems to work just fine in OCLP. I think there needs to be an override button on that screen or something for people who are running into this weirdness (like "I know how to select a USB device, quit trying to protect me from myself"), *OR* rather than dinking around with diskutil, why aren't they just reporting the devices listed in /Volumes? Maybe there's some reason, but the bottom line is that there's a bug in OCLP that isn't taking into account the fact that sometimes USB devices are being reported by diskutil was internal devices.

I created an account just to say thank you. Been trying for a couple of days with no success, with different usbs and ports. Using a dongle solved it.