Contribute
Register

< Solved > The installer does not recognize the installation disk

Joined
Jan 7, 2019
Messages
116
Motherboard
Gigabyte Z390 Designare
CPU
I7-9700K
Graphics
RX 580
Mobile Phone
  1. Android
Motherboard Gigabyte Z390 Designare
CPU I7-9700K
Graphics RX 580

Hi, I need help to install Ventura. I have BigSur running with no problems. I tried the updater but it failed. Now I'm trying to install it from scratch.

1) I've created an USB installer with terminal command
2) I've created an opencore EFI with HackinDROM app
3) I've copied EFI to USB EFI
4) Restart with USB

When GUI was shown, I tryied to install macOS ventura but my main disk was not shown in the list of options! Just the installer USB (blocked) and two SATA HDs.

IMG_20230319_181058.jpg


Then, I tried Disk utility, to format the main disk, but the main disk does not appear in the disks list either:

IMG_20230319_180913.jpg


My guess is that the installation drive is not suitable for macos Ventura. Could it be?

The drive is a SABRENT SSD 1TB, M.2 SSD 1TB, NVMe 1TB PCIe M.2 2280

Any help welcome. Thanks!
 
Motherboard Gigabyte Z390 Designare
CPU I7-9700K
Graphics RX 580

Hi, I need help to install Ventura. I have BigSur running with no problems. I tried the updater but it failed. Now I'm trying to install it from scratch.

1) I've created an USB installer with terminal command
2) I've created an opencore EFI with HackinDROM app
3) I've copied EFI to USB EFI
4) Restart with USB

When GUI was shown, I tryied to install macOS ventura but my main disk was not shown in the list of options! Just the installer USB (blocked) and two SATA HDs.

View attachment 565803

Then, I tried Disk utility, to format the main disk, but the main disk does not appear in the disks list either:

View attachment 565804

My guess is that the installation drive is not suitable for macos Ventura. Could it be?

The drive is a SABRENT SSD 1TB, M.2 SSD 1TB, NVMe 1TB PCIe M.2 2280

Any help welcome. Thanks!
you have to click on view and then show all devices
 
Probably target drive isn't in correct format, you'll need to reformat it
 
zip and upload your EFI

Drive should still show up regardless
Thank you! here it is.

The strange thing in that this drive is working fine right now with BigSur, with the same EFI, but is invisible for the Ventura installer.

That's why I think it could be an incompatible drive. I've read something here about it, but it doesn't explain in detail if my drive is incompatible (only some compatible drives are recommended in the article).
 

Attachments

  • EFI.zip
    9.9 MB · Views: 41
Last edited:
Thank you! here it is.

The strange thing in that this drive is working fine right now with BigSur, with the same EFI, but is invisible for the Ventura installer.

That's why I think it could be an incompatible drive. I've read something here about it, but it doesn't explain in detail if my drive is incompatible (only some compatible drives are recommended in the article).
seems ok, apart from:
Code:
<key>Drivers</key>
        <array>
            <string>OpenCanopy.efi</string>
            <string>AudioDxe.efi</string>
            <string>CrScreenshotDxe.efi</string>
            <string>OpenRuntime.efi</string>
            <string>HfsPlus.efi</string>
        </array>
which is in the wrong format

but that won't have an affect on a drive not showing up

maybe look into a WD nvme as they are a lot more compatible
 
seems ok, apart from:
Code:
<key>Drivers</key>
        <array>
            <string>OpenCanopy.efi</string>
            <string>AudioDxe.efi</string>
            <string>CrScreenshotDxe.efi</string>
            <string>OpenRuntime.efi</string>
            <string>HfsPlus.efi</string>
        </array>
which is in the wrong format

but that won't have an affect on a drive not showing up

maybe look into a WD nvme as they are a lot more compatible
Thank you. I'll try with WD nvme.

Could you tell me the right format for the drivers part?
 
Thank you. I'll try with WD nvme.

Could you tell me the right format for the drivers part?
from the sample.plist:

it should be in this format:

Code:
<dict>
                <key>Arguments</key>
                <string></string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <false/>
                <key>LoadEarly</key>
                <true/>
                <key>Path</key>
                <string>OpenCanopy.efi</string>
            </dict>
            <dict>
                <key>Arguments</key>
                <string></string>
                <key>Comment</key>
                <string></string>
                <key>Enabled</key>
                <true/>
                <key>LoadEarly</key>
                <false/>
                <key>Path</key>
                <string>AudioDxe.efi</string>
            </dict>
etc...
 
Hi I've updated your EFI Folder with latest the OC and kext files versions, clear NvRAM at boot and try the attached EFI Folder on a test USB drive and see if you get an agreeable result. Good luck.

PS - Why two versions of USBInjectall.kext? Surely just the right one will suffice but if your system boots fine, I guess so be it.
 

Attachments

  • EFI.zip
    4.9 MB · Views: 28
Back
Top