MP 1,1-5,1 Innie: A fix for PCI drives seen as external

[cdf]

Thank you so much for your reply dear Cdf but i follow your post #9 instruction 3 time and the result was after reboot my system macOS not working so i reinstall again i think i miss some thing so that's why i need your more guideline a small video of post 9 will be best for us
thanks

Well, the instructions were clarified since you originally tried, so you may want to try again. Also, please note that because Innie is now a standalone kext, installing it is really no different than installing any other kext, and there are resources online for this. However, as I've mentioned above, patched installations are problematic: the kext expects an unmodified system. In fact, your system not working after installing the kext unfortunately points in that direction. Thus, the kext is probably not compatible with your system.

 

[Masood zafar]

Well, the instructions were clarified since you originally tried, so you may want to try again. Also, please note that because Innie is now a standalone kext, installing it is really no different than installing any other kext, and there are resources online for this. However, as I've mentioned above, patched installations are problematic: the kext expects an unmodified system. In fact, your system not working after installing the kext unfortunately points in that direction. Thus, the kext is probably not compatible with your system.

okay thank you for your reply sir will you please tell me what operating system you install in your 2009 macPro

 

[Masood zafar]

okay thank you for your reply sir will you please tell me what operating system you install in your 2009 macPro

i mean are you using macOS Big sur on your 2009 MacPro

 

[startergo]

@cdf This guy is still set as external:

kextstat | grep -v com.apple
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   49    4 0                  0x87000    0x87000    as.vit9696.Lilu (1.5.1) B75B4CEB-4242-35A6-97FD-94BE0CA07BE8 <8 6 5 3 2 1>
   50    0 0                  0x9000     0x9000     com.cdf.Innie (1.3.0) A7385B07-17E1-3DC1-95E8-402BC70D39B4 <5 3>
   51    0 0                  0x82000    0x82000    as.vit9696.WhateverGreen (1.4.7) 8F64A486-EEC6-3233-A350-BD11E9A7F8FA <49 14 8 6 5 3 2 1>
   52    0 0                  0xd000     0xd000     as.lvs1974.DebugEnhancer (1.0.3) CB3CC52F-15C1-3A17-9F0E-F4FA9A1C2AA7 <49 8 6 5 3 2 1>
   53    0 0                  0x11000    0x11000    as.lvs1974.HibernationFixup (1.4.0) 9F07287D-D85D-3437-BA35-2567E8B53A79 <49 8 6 5 3 2 1>
   54    0 0                  0xd000     0xd000     as.vit9696.RestrictEvents (1.0.1) 1CEF0BFA-9CCF-3B0B-988B-C1132D8F027D <49 8 6 5 3 2 1>

 

[startergo]

Few reboots later I got more of them:

kextstat | grep -v com.apple     
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
   49    4 0                  0x87000    0x87000    as.vit9696.Lilu (1.5.1) B75B4CEB-4242-35A6-97FD-94BE0CA07BE8 <8 6 5 3 2 1>
   50    0 0                  0x9000     0x9000     com.cdf.Innie (1.3.0) A7385B07-17E1-3DC1-95E8-402BC70D39B4 <5 3>
   51    0 0                  0x82000    0x82000    as.vit9696.WhateverGreen (1.4.7) 8F64A486-EEC6-3233-A350-BD11E9A7F8FA <49 14 8 6 5 3 2 1>
   52    0 0                  0xd000     0xd000     as.lvs1974.DebugEnhancer (1.0.3) CB3CC52F-15C1-3A17-9F0E-F4FA9A1C2AA7 <49 8 6 5 3 2 1>
   53    0 0                  0x11000    0x11000    as.lvs1974.HibernationFixup (1.4.0) 9F07287D-D85D-3437-BA35-2567E8B53A79 <49 8 6 5 3 2 1>
   54    0 0                  0xd000     0xd000     as.vit9696.RestrictEvents (1.0.1) 1CEF0BFA-9CCF-3B0B-988B-C1132D8F027D <49 8 6 5 3 2 1>

And setting built-in properties in OC works consistently (with Innie disabled)

 

[cdf]

@startergo, do the disks still all get the built-in property?

 

[startergo]

@startergo, do the disks still all get the built-in property?

Yes:

And so on...
At the bridge level they are ok, but down the stream at the device level they are external.

 

[cdf]

And so on...
At the bridge level they are ok, but down the stream at the device level they are external.

Thanks. I think I know what's going on. I'll address this bug as soon as I get the chance.

 

[startergo]

Thanks. I think I know what's going on. I'll address this bug as soon as I get the chance.

I wonder if it is not better to convert it to a EFI rather than kext driver? EFI driver can even be injected in the firmware or in rEFInd.

 

[matyaszabo]

Hey Guys! I need some help. Disabled SIP but still can't copy Innie.kext into Extensions folder (Big Sur, Mac Pro 2019) What am I doing wrong?

update: NVM figured it out, it works! thank you @cdf

 

[JedNZ]

Innie 1.3.0 works perfectly with the instructions from post #9 on a cMP 5,1 2012 that I’m setting up as a Server for a client - no OC or RFP - just a plain, standard HS installation. Thank you again for the continued work in developing this tool/resource.

 

[DigitaLife]

The latest version of Innie is 1.3.0:

Releases · cdf/Innie

Make PCIe drives appear internal. Contribute to cdf/Innie development by creating an account on GitHub.

github.com

Making PCIe drives appear internal with Innie

You will need:

​

Innie​

Download the latest release version. The uncompressed folder contains the file Innie.kext.​

Installation

1. Disable SIP.
2. Copy Innie.kext to /Library/Extensions. You may need to authorize this.
3. Open terminal.
4. For macOS Catalina or later, enter sudo mount -uw /. You may need to authorize this.
5. Enter the following commands:
   

   sudo chmod -R 755 /Library/Extensions/Innie.kext
   sudo chown -R root:wheel /Library/Extensions/Innie.kext
   sudo touch /Library/Extensions
   sudo kextcache -update-volume /

6. Wait for the last command to complete.
7. For macOS Big Sur, approve the installation in System Preferences > Security & Privacy.
8. Reboot.

If all goes well, your drive will now be seen as internal.

Spoiler: Instructions for installing older versions of Innie (like those attached below)...

Legacy instructions

These instructions apply to Innie 1.2.1 and earlier. For these versions, Innie is a Lilu plugin.

You will need:

Lilu​

Download the latest release version. The uncompressed folder contains the file Lilu.kext.​

​

Innie (see also attached to this post)​

Download version 1.2.1 or earlier. The uncompressed folder contains the file Innie.kext.​

Installation

1. Disable SIP.
2. Control-click on Lilu.kext and select "Show Package Contents." You will see the folder "Contents." Open it.
3. In Contents, create a new folder called "Plugins" (exactly like this, but without quotation marks, of course). This is where Innie will go.
4. Copy Innie.kext into the Plugins folder.
5. Now copy Lilu.kext to /Library/Extensions. You may need to authorize this.
6. Open terminal.
7. For macOS Catalina or later, enter sudo mount -uw /. You may need to authorize this.
8. Enter the following commands:
   

   sudo chmod -R 755 /Library/Extensions/Lilu.kext
   sudo chown -R root:wheel /Library/Extensions/Lilu.kext
   sudo touch /Library/Extensions
   sudo kextcache -update-volume /

9. Wait for the last command to complete.
10. For macOS Big Sur, approve the installation in System Preferences > Security & Privacy.
11. Reboot.

I have tried several times to install Innie 1.3.0 following your guide but without success!
I have tried with both Catalina and Mojave but nothing!
Any suggestions on how I can fix this problem?
Thanks in advance!

 

[cdf]

Any suggestions on how I can fix this problem?

As a first step, verify that Innie is properly loaded: Check System Information > Extensions for unsigned kexts. Innie should be listed with "loaded yes."

Note that Innie can be hit or miss with patched installations. It should also be considered incompatible with devices that use third party drivers. Also, if you are using OpenCore, you should inject Innie through your configuration, or (even better) use device properties instead of Innie (see the OpenCore guide).

 

[matyaszabo]

@cdf yesterday installed and worked perfectly (re-enabled SIP after). today checked system information and it says that it's not loaded. disabled SIP again, entered (sudo mount -uw /) in terminal and got "volume could not be mounted: permission denied" "failed with 66" message
any suggestions ?

 

[DigitaLife]

As a first step, verify that Innie is properly loaded: Check System Information > Extensions for unsigned kexts. Innie should be listed with "loaded yes."

Note that Innie can be hit or miss with patched installations. It should also be considered incompatible with devices that use third party drivers. Also, if you are using OpenCore, you should inject Innie through your configuration, or (even better) use device properties instead of Innie (see the OpenCore guide).

I'm using Oc 0.6.5 and so far the icons of NVMe drive were always like Internal Disk but in fact, since I installed the HighPoint SSD7101A-1 controller with the related driver, icons have become like External Disk!
Is there any way to fix this conflict?

 

[cdf]

@cdf yesterday installed and worked perfectly (re-enabled SIP after). today checked system information and it says that it's not loaded. disabled SIP again, entered (sudo mount -uw /) in terminal and got "volume could not be mounted: permission denied" "failed with 66" message
any suggestions ?

The problem is keeping unsigned kexts loaded, and with the added security in Big Sur, this becomes a game of cat and mouse... At this point, I'm inclined to just discourage the use of Innie on Big Sur. Perhaps try to keep SIP off. Also, make sure to allow the kext in Security & Privacy.

Is there any way to fix this conflict?

Not that I am aware of, unfortunately.

 

[matyaszabo]

The problem is keeping unsigned kexts loaded, and with the added security in Big Sur, this becomes a game of cat and mouse... At this point, I'm inclined to just discourage the use of Innie on Big Sur. Perhaps try to keep SIP off. Also, make sure to allow the kext in Security & Privacy.

hmm it seems to work if SIP is turned off. what's the downside of that?

 

[PowerMove]

The latest version of Innie is 1.3.0

I installed Innie 1.3.0 on a 2010 Mac Pro running MacOS 10.14.6 with an OWC Accelsior 1M2 M.2 SSD to PCIe 4.0 Adapter Card, following your instructions as laid out here, and it is working flawlessly. Thanks for much putting in the effort to make this fix available.

Michael

 

[alphascorp]

I'm really not sure. Did you also allow the kext in System Preferences > Security & Privacy? How did you install Big Sur?

Hi @cdf

Here is the continuation of my little problem about the NVMe system disk (on macOS Big Sur 11.0.1, 11.1 and 11.2) seen internally by the disk utility but still appearing on the desktop.

Yesterday, with the release of BS 11.2 I did a clean installation on a second NVMe blade (Samsung 970 EVO) using a USB installer patched with Barry K Nathan's micropatcher 0.5.1 (I also specify that no changes were made to the system after the installation),
Then I installed innie 1.3.0 following scrupulously the instructions of post #9, the system disk is seen internally by the disk utility but once again it still appears on the desktop (and disappears from the desktop when unchecked the "external disk" option in the Finder Preferences)

Only the Finder seems to consider it as external.

Second observation, when I put back in place my first NVMe blade containing BS 11.1 to migrate my data, it does not appear on the desktop.

Conclusion, as confirmed by my screenshot, only the NVMe startup disk appears on the desktop, but seen internal by the disk utility (and System Information.app).

This happens only with macOS booted on NVMe PCI blades, because I tested with a clean installation of 11.2 on a classic SSD (Crucial BX500) positioned in bay #1, after booting on it, no internal disk appears on the desktop (my 2 NVMe blades were still present).

 

[cdf]

Conclusion, as confirmed by my screenshot, only the NVMe startup disk appears on the desktop, but seen internal by the disk utility (and System Information.app).

This happens only with macOS booted on NVMe PCI blades, because I tested with a clean installation of 11.2 on a classic SSD (Crucial BX500) positioned in bay #1, after booting on it, no internal disk appears on the desktop (my 2 NVMe blades were still present).

Interesting. Hopefully the next update will help. In the meantime, perhaps you could use IORegistryExplorer to check the properties highlighted in post #504.

 

[alphascorp]

Interesting. Hopefully the next update will help. In the meantime, perhaps you could use IORegistryExplorer to check the properties highlighted in post #504.

Thanks for quick response

After checking all highlighted properties in post #504 seems correct in my case.

EDIT:

Hi @cdf
I noticed an inconsistency between the information given by IORegistryExplorer showing that the NVMe disk is not ejectable and the disk information window (from the disk utility) showing that the NVMe disk is ejectable.
However, the disk utility displays the NVMe disk as internal and no eject symbol appears next to it.

 

[startergo]

For macOS Catalina or later, enter sudo mount -uw / in terminal.

For BS this does not work (nor is needed) as it is a sealed volume, so this only applies to Catalina. I install kexts with Hackintool in BS. I tested Innie in /L/E without OC. It mostly works, but again one of the NVME drives appear as external (Orange Icon), but internal in Disk Utility.

I have to mention this yellow icon appears on the booted NVME disk.

 

[dabiohazard]

Works on High Sierra by using Kext Utility.app and it copying the file to System/Library/Extensions ! Thanks so much for this fix! SO Much easier than trying to configure in Opencore! I never could figure out how to get it working that way. (Stuck on High Sierra for my Star Wars Nvidia Card)

 

[NicoFR75]

Hi @cdf

Here is the continuation of my little problem about the NVMe system disk (on macOS Big Sur 11.0.1, 11.1 and 11.2) seen internally by the disk utility but still appearing on the desktop.

Yesterday, with the release of BS 11.2 I did a clean installation on a second NVMe blade (Samsung 970 EVO) using a USB installer patched with Barry K Nathan's micropatcher 0.5.1 (I also specify that no changes were made to the system after the installation),
Then I installed innie 1.3.0 following scrupulously the instructions of post #9, the system disk is seen internally by the disk utility but once again it still appears on the desktop (and disappears from the desktop when unchecked the "external disk" option in the Finder Preferences)

Only the Finder seems to consider it as external.

Second observation, when I put back in place my first NVMe blade containing BS 11.1 to migrate my data, it does not appear on the desktop.

Conclusion, as confirmed by my screenshot, only the NVMe startup disk appears on the desktop, but seen internal by the disk utility (and System Information.app).

This happens only with macOS booted on NVMe PCI blades, because I tested with a clean installation of 11.2 on a classic SSD (Crucial BX500) positioned in bay #1, after booting on it, no internal disk appears on the desktop (my 2 NVMe blades were still present).

View attachment 1723459

Hello, I've the same problem.

I just upgraded from Catalina to BigSur today my NVME is still showing as "ejectable" after Innie 1.3.0 install (followed post #9 instructions).
I'm on a MacPro 3.1 with NVME on PCIE adapter, it's my boot disk.
On Catalina the previous version of Innie was working fine, the NVME was shown as internal and non-ejectable.

 

[maxming]

@cdf

Can this problem be solved? I look forward to it as soon as possible
I need him very much

Currently I have several software that recognize my SSD as an external hot-swappable device

At the same time, the finder shows that the SSD is also a removable disk icon

At the same time, the Disk Manager shows that the disk can also be launched.