Jump to content
Taruga

Mojave Raid 0 APFS Solution

33 posts in this topic

Recommended Posts

Thx Taruga

My experiences:

- i have disabled SIP from Recovery Boot. Then I started the system from a different disk

- then I removed from RAID

   /System/Library/Caches/

 /System/Library/PrelinkedKernels/

 

on Boot OS X 1 manual  create

com.apple.boot.S 

 |– put var and System from com.apple.boot.R

I have modified

com.apple.boot.R/Library/Preferences/SystemConfiguration/com.apple.Boot.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel Flags</key>
	<string></string>
	<key>Root UUID</key>
	<string>automatic generate UUID-XXXX-XXXX</string>
        <key>BLLastBSDName</key>
        <string>disk3s2</string>
        <key>Path</key>
         <string>\XXXX-XXXX-PrebootUUID-XXXX-XXXX\System\Library\CoreServices\boot.efi</string>

</dict>
</plist>

on Boot OS X

manual  create com.apple.boot.R 

and  put var folder

Reel-MBP:~ r$ tree /Volumes/Boot\ OS\ X 
/Volumes/Boot\ OS\ X
├── System
│   └── Library
│       ├── Caches
│       │   └── com.apple.corestorage
│       │       ├── EFILoginLocalizations
│       │       │   ├── Lucida13.efires
│       │       │   ├── Lucida13White.efires
│       │       │   ├── appleLogo.efires
│       │       │   ├── battery.efires
│       │       │   ├── disk_passwordUI.efires
│       │       │   ├── flag_picker.efires
│       │       │   ├── guest_userUI.efires
│       │       │   ├── loginui.efires
│       │       │   ├── preferences.efires
│       │       │   ├── sound.efires
│       │       │   └── unknown_userUI.efires
│       │       └── EncryptedRoot.plist.wipekey
│       └── CoreServices
│           ├── BridgeVersion.bin
│           ├── BridgeVersion.plist
│           ├── PlatformSupport.plist
│           ├── SystemVersion.plist
│           ├── boot.efi
│           ├── boot.efi.j132ap.im4m
│           ├── boot.efi.j137ap.im4m
│           ├── boot.efi.j680ap.im4m
│           ├── bootbase.efi.j132ap.im4m
│           ├── bootbase.efi.j137ap.im4m
│           └── bootbase.efi.j680ap.im4m
├── com.apple.boot.P
│   ├── Library
│   │   └── Preferences
│   │       └── SystemConfiguration
│   │           └── com.apple.Boot.plist
│   ├── System
│   │   └── Library
│   │       └── PrelinkedKernels
│   │           └── prelinkedkernel
│   └── usr
│       └── standalone
│           └── i386
│               └── EfiLoginUI
│                   ├── Lucida13.efires
│                   ├── Lucida13White.efires
│                   ├── appleLogo.efires
│                   ├── battery.efires
│                   ├── disk_passwordUI.efires
│                   ├── flag_picker.efires
│                   ├── guest_userUI.efires
│                   ├── loginui.efires
│                   ├── recoveryUI.efires
│                   ├── recovery_user.efires
│                   ├── sound.efires
│                   └── unknown_userUI.efires
├── com.apple.boot.R
│   └── var
│       └── db
└── var
    └── db
        ├── AdminUserRecoveryInfo.plist
        ├── CryptoUserInfo.plist
        └── secureaccesstoken.plist

22 directories, 40 files
Reel-MBP:~ r$ tree /Volumes/Boot\ OS\ X\ 1 
/Volumes/Boot\ OS\ X\ 1
├── System
│   └── Library
│       ├── Caches
│       │   └── com.apple.corestorage
│       │       ├── EFILoginLocalizations
│       │       │   ├── Lucida13.efires
│       │       │   ├── Lucida13White.efires
│       │       │   ├── appleLogo.efires
│       │       │   ├── battery.efires
│       │       │   ├── disk_passwordUI.efires
│       │       │   ├── flag_picker.efires
│       │       │   ├── guest_userUI.efires
│       │       │   ├── loginui.efires
│       │       │   ├── preferences.efires
│       │       │   ├── sound.efires
│       │       │   └── unknown_userUI.efires
│       │       └── EncryptedRoot.plist.wipekey
│       └── CoreServices
│           ├── BridgeVersion.bin
│           ├── BridgeVersion.plist
│           ├── PlatformSupport.plist
│           ├── SystemVersion.plist
│           ├── boot.efi
│           ├── boot.efi.j132ap.im4m
│           ├── boot.efi.j137ap.im4m
│           ├── boot.efi.j680ap.im4m
│           ├── bootbase.efi.j132ap.im4m
│           ├── bootbase.efi.j137ap.im4m
│           └── bootbase.efi.j680ap.im4m
├── com.apple.boot.R
│   ├── Library
│   │   └── Preferences
│   │       └── SystemConfiguration
│   │           └── com.apple.Boot.plist
│   ├── System
│   │   └── Library
│   │       └── PrelinkedKernels
│   │           └── prelinkedkernel
│   ├── usr
│   │   └── standalone
│   │       └── i386
│   │           └── EfiLoginUI
│   │               ├── Lucida13.efires
│   │               ├── Lucida13White.efires
│   │               ├── appleLogo.efires
│   │               ├── battery.efires
│   │               ├── disk_passwordUI.efires
│   │               ├── flag_picker.efires
│   │               ├── guest_userUI.efires
│   │               ├── loginui.efires
│   │               ├── recoveryUI.efires
│   │               ├── recovery_user.efires
│   │               ├── sound.efires
│   │               └── unknown_userUI.efires
│   └── var
│       └── db
│           ├── AdminUserRecoveryInfo.plist
│           ├── CryptoUserInfo.plist
│           └── secureaccesstoken.plist
├── com.apple.boot.S
│   ├── System
│   └── var
│       └── db
└── var
    └── db
        ├── AdminUserRecoveryInfo.plist
        ├── CryptoUserInfo.plist
        └── secureaccesstoken.plist

25 directories, 43 files

Now I can also run without Single user mode and with SIP disabled.

After restarting, some files will be deleted.

(AdminUserRecoveryInfo.plist, CryptoUserInfo.plist, secureaccesstoken.plist from /Volumes/Boot OS X/com.apple.boot.R/var/db/

But the catalog structure itself is important, I think

 

On 9/29/2018 at 7:56 AM, Taruga said:

√ Copy PrelinkedKernels folder into com.apple.boot.S/System/Library/ on Boot OS X partitions

 

What you have in com.apple.boot.S I have in com.apple.boot.R on Boot OS X  1

and com.apple.boot.P on Boot OS X

 

 

Edited by wodawoda

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)

Hi wodawoda, I never needed to change com.apple.Boot.plist. with all of that
That looks like you're booting (or trying to boot) from Preboot volume instead, right ?
I never tried that.

Yesterday, I tried to update Mojave to the current beta and it didn't work.

I was able to update before all the betas until the final version,  but the current beta starts to install and after reboot I'm still on the same version.
Looks like update gets interrupted somewhere.... Well, I was expecting something like this sooner or later.
Let's see if I can find a way to fix it, or check later if it will work with the final versions of that beta

Anyway,  my current Boot OS X folder content is this (after trying to install the beta update) and the OS always boots normally:
 

├── Library
│   └── Preferences
│       └── SystemConfiguration
│           └── com.apple.Boot.plist
├── System
│   └── Library
│       ├── Caches
│       │   └── com.apple.corestorage
│       │       ├── EFILoginLocalizations
│       │       │   ├── Lucida13.efires
│       │       │   ├── Lucida13White.efires
│       │       │   ├── appleLogo.efires
│       │       │   ├── battery.efires
│       │       │   ├── disk_passwordUI.efires
│       │       │   ├── flag_picker.efires
│       │       │   ├── guest_userUI.efires
│       │       │   ├── loginui.efires
│       │       │   ├── preferences.efires
│       │       │   ├── sound.efires
│       │       │   └── unknown_userUI.efires
│       │       └── EncryptedRoot.plist.wipekey
│       └── CoreServices
│           ├── PlatformSupport.plist
│           ├── SystemVersion.plist
│           ├── boot.efi
│           ├── boot.efi.j132ap.im4m
│           ├── boot.efi.j137ap.im4m
│           ├── boot.efi.j680ap.im4m
│           ├── bootbase.efi.j132ap.im4m
│           ├── bootbase.efi.j137ap.im4m
│           └── bootbase.efi.j680ap.im4m
├── com.apple.boot.S
│   ├── Library
│   │   └── Preferences
│   │       └── SystemConfiguration
│   │           └── com.apple.Boot.plist
│   ├── System
│   │   └── Library
│   │       └── PrelinkedKernels
│   │           └── prelinkedkernel
│   └── usr
│       └── standalone
│           └── i386
│               └── EfiLoginUI
│                   ├── Lucida13.efires
│                   ├── Lucida13White.efires
│                   ├── appleLogo.efires
│                   ├── battery.efires
│                   ├── disk_passwordUI.efires
│                   ├── flag_picker.efires
│                   ├── guest_userUI.efires
│                   ├── loginui.efires
│                   ├── recoveryUI.efires
│                   ├── recovery_user.efires
│                   ├── sound.efires
│                   └── unknown_userUI.efires
├── com.apple.boot.once
│   ├── com.apple.Boot.plist
│   ├── prelinkedkernel
│   └── usr
│       └── standalone
│           └── i386
│               └── EfiLoginUI
│                   ├── Lucida13.efires
│                   ├── Lucida13White.efires
│                   ├── appleLogo.efires
│                   ├── battery.efires
│                   ├── disk_passwordUI.efires
│                   ├── flag_picker.efires
│                   ├── guest_userUI.efires
│                   ├── loginui.efires
│                   ├── recoveryUI.efires
│                   ├── recovery_user.efires
│                   ├── sound.efires
│                   └── unknown_userUI.efires
├── com.apple.installer
│   ├── PlatformSupport.plist
│   ├── SystemVersion.plist
│   ├── boot.efi
│   └── com.apple.Boot.plist
├── usr
│   └── standalone
│       └── i386
│           └── EfiLoginUI
│               ├── Lucida13.efires
│               ├── Lucida13White.efires
│               ├── appleLogo.efires
│               ├── battery.efires
│               ├── disk_passwordUI.efires
│               ├── flag_picker.efires
│               ├── guest_userUI.efires
│               ├── loginui.efires
│               ├── recoveryUI.efires
│               ├── recovery_user.efires
│               ├── sound.efires
│               └── unknown_userUI.efires
└── var
    └── db
        ├── AdminUserRecoveryInfo.plist
        ├── CryptoUserInfo.plist
        └── secureaccesstoken.plist


cat com.apple.boot.S/Library/Preferences/SystemConfiguration/com.apple.Boot.plist 


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel Flags</key>
	<string></string>
	<key>Root UUID</key>
	<string>624F43E6-B6C1-3C1E-9BA7-90E41366B873</string>
</dict>
</plist>


I'm not sure if that Root UUID entry is needed or not because all the times I tested before,  I was able to boot without any changes to com.apple.Boot.plist. But yesterday I was trying a lot of different things and it was left that way.

624F43E6-B6C1-3C1E-9BA7-90E41366B873 it's the Volume UUID that you can get with:

taruga$ diskutil info /Volumes/APFS_Raid0/

 Device Identifier:        disk10s1
   Device Node:              /dev/disk10s1
   Whole:                    No
   Part of Whole:            disk10

   Volume Name:              APFS_Raid0
   Mounted:                  Yes
   Mount Point:              /Volumes/APFS_Raid0

   Partition Type:           41504653-0000-11AA-AA11-00306543ECAC
   File System Personality:  APFS
   Type (Bundle):            apfs
   Name (User Visible):      APFS
   Owners:                   Enabled

   OS Can Be Installed:      Yes
   Booter Disk:              disk10s2
   Recovery Disk:            disk10s3
   Media Type:               Generic
   Protocol:                 SATA
   SMART Status:             Verified
   Volume UUID:              624F43E6-B6C1-3C1E-9BA7-90E41366B873
   Disk / Partition UUID:    624F43E6-B6C1-3C1E-9BA7-90E41366B873

   Disk Size:                479.2 GB (479217082368 Bytes) (exactly 935970864 512-Byte-Units)
   Device Block Size:        4096 Bytes

   Volume Total Space:       479.2 GB (479217082368 Bytes) (exactly 935970864 512-Byte-Units)
   Volume Used Space:        24.6 GB (24568803328 Bytes) (exactly 47985944 512-Byte-Units) (5.1%)
   Volume Free Space:        454.6 GB (454648279040 Bytes) (exactly 887984920 512-Byte-Units) (94.9%)
   Allocation Block Size:    4096 Bytes

   Read-Only Media:          No
   Read-Only Volume:         No

   Device Location:          Internal
   Removable Media:          Fixed

   Solid State:              Yes
   Hardware AES Support:     No

 

I'm using Clover revision: 4644 and my drivers64UEFI folder has this:

drivers64UEFI/
├── ApfsDriverLoader-64.efi
├── AppleImageCodec-64.efi
├── AppleKeyAggregator-64.efi
├── AppleUITheme-64.efi
├── AptioInputFix-64.efi
├── AptioMemoryFix-64.efi
├── DataHubDxe-64.efi
├── FSInject-64.efi
├── FireWireDevice.efi
├── FireWireOhci.efi
├── FirmwareVolume-64.efi
├── HFSPlus-64.efi
├── PartitionDxe-64.efi
└── SMCHelper-64.efi

 

Edited by Taruga

Share this post


Link to post
Share on other sites
On 9/29/2018 at 7:56 AM, Taruga said:

That looks like you're booting (or trying to boot) from Preboot volume instead, right ?

Yes, Mojave on apfs always boot from preboot

 

A use 

diskutil apfs list 
or 
diskutil info disk3s1 | grep "Volume UUID"

 

On 10/1/2018 at 8:51 PM, Taruga said:

I'm not sure if that Root UUID entry is needed or not because all the times I tested before

Root UUID was created automatically in my com.apple.Boot.plist 

 

This is nvram from 1 drive Apfs installation

efi-backup-boot-device 
<array>
<dict>
   <key>IOMatch</key><dict>
<key>IOProviderClass</key>
<string>IOMedia</string>
<key>IOPropertyMatch</key>
<dict>
<key>UUID</key>
<string>5CD6F5B8-7244-4647-A005-24CCF9779291</string>
</dict></dict>
<key>BLLastBSDName</key>
<string>disk2s2</string>
</dict><dict>
<key>IOEFIDevicePathType</key>
<string>MediaFilePath</string>
<key>Path</key>
<string>\EBA6D803-676C-433C-B368-0A7EF0E7AA52\System\Library\CoreServices\boot.efi</string>
</dict></array>

5CD6F5B8-7244-4647-A005-24CCF9779291 - UUID from Mac HD (/)

EBA6D803-676C-433C-B368-0A7EF0E7AA52 -  UUID from Preboot

I'm not sure if that Preboot entry is needed but way not add (testing :) )

 

On 10/1/2018 at 8:51 PM, Taruga said:

Yesterday, I tried to update Mojave to the current beta and it didn't work.

I also. I installed .pkg from/Library/Updates/  using Pacifist.app, maybe it's not very elegant but it works. The full installation works normally, the update does not.

I do not use Refind & Clover anymore.

Recovery HD also not work for me

Share this post


Link to post
Share on other sites
Posted (edited)

Maybe it will be useful for someone

Reel-MBP:~ r$ diskutil mount  disk0s3
Volume Boot OS X on disk0s3 mounted
Reel-MBP:~ r$ sudo bless -mount /Volumes/Boot\ OS\ X  -setBoot
Reel-MBP:~ r$ sudo bless --getBoot --verbose
Password:
EFI found at IODeviceTree:/efi
Current EFI boot device string is: '<array><dict><key>IOMatch</key><dict><key>IOProviderClass</key><string>IOMedia</string><key>IOPropertyMatch</key><dict><key>UUID</key><string>71C5CE43-F054-4737-B0E9-F2E588AC4C73</string></dict></dict><key>BLLastBSDName</key><string>disk0s3</string></dict></array>'
Boot option is 8BE4DF61-93CA-11D2-AA0D-00E098032B8C:Boot0080
Processing boot option 'Mac OS X'
Boot option matches XML representation
Found device: disk0s3
Disk boot device detected
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT1@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/EFI System Partition@1
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/Untitled 2@2
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/Booter@3
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT1@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/EFI System Partition@1
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT1@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/Untitled 2@2
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT1@1/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/Booter@3
Checking IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntelPchSeriesAHCI/PRT0@0/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDriver/Samsung SSD 850 EVO 250GB Media/IOGUIDPartitionScheme/Untitled 2@2/AppleRAIDMember/AppleRAIDStripeSet/raid0@0
Comparing member to IODeviceTree:/PCI0@0/SATA@1F,2/PRT0@0/PMP@0/@0:2	EQUAL
Found Boot!=Root aggregate media disk2
/dev/disk2

 

and mabe this

 

MacOS isn’t booting a file off of the System volume (/dev/disk3s1), it’s booting the boot.efi file from the new APFS Preboot volume (/dev/disk3s2) that you’ll find inside APFS containers:

<key>BLLastBSDName</key>
<string>disk3s2</string>

<key>Path</key>
<string>\00B24073-D432-4C9A-AC90-468B0E3B7733\System\Library\CoreServices\boot.efi</string>

It doesn’t matter if you’ve encrypted the device or not. Every macOS device booting an APFS filesystem boots like this.

You can see the container layout with this command: diskutil apfs list

diskutil apfs list
APFS Container (1 found)
|
+-- Container disk3 14233F96-9751-4DE9-9D8D-203EE8D07310
    ====================================================
    APFS Container Reference:     disk3
    Size (Capacity Ceiling):      499218800640 B (499.2 GB)
    Capacity In Use By Volumes:   239534854144 B (239.5 GB) (48.0% used)
    Capacity Not Allocated:       259683946496 B (259.7 GB) (52.0% free)
    |
    +-< Physical Store disk2s2 76DA7DF5-5D4F-4E33-B85E-1342AA29E864
    |   -----------------------------------------------------------
    |   APFS Physical Store Disk:   disk2s2
    |   Size:                       499218804224 B (499.2 GB)
    |
    +-> Volume disk3s1 00B24073-D432-4C9A-AC90-468B0E3B7733
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk3s1 (No specific role)
    |   Name:                      HD (Case-insensitive)
    |   Mount Point:               /
    |   Capacity Consumed:         237743906816 B (237.7 GB)
    |   FileVault:                 No
    |
    +-> Volume disk3s2 A0FC6D07-D36C-4946-9008-B60814B8D88C
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk3s2 (Preboot)
    |   Name:                      Preboot (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         43737088 B (43.7 MB)
    |   FileVault:                 No
    |
    +-> Volume disk3s3 4BFD3303-F3F7-451C-B1B1-C1B46B633F44
    |   ---------------------------------------------------
    |   APFS Volume Disk (Role):   disk3s3 (Recovery)
    |   Name:                      Recovery (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         511995904 B (512.0 MB)
    |   FileVault:                 No
    |
    +-> Volume disk3s4 5DABC0D4-1B0F-4058-A5A9-5D5EABD7CB14
        ---------------------------------------------------
        APFS Volume Disk (Role):   disk3s4 (VM)
        Name:                      VM (Case-insensitive)
        Mount Point:               /private/var/vm
        Capacity Consumed:         1073762304 B (1.1 GB)
        FileVault:                 No

It comes in a triplet: OS/System volume, Preboot, and Recovery. If you’re booted from a System volume within an APFS Container, you’ll also see a (temporary) VM volume, which has taken the place of and is mounted at /private/var/vm.

So we’re booting from Preboot.

Let’s mount them and see. For the OS that’s booted off the internal disk, that’s usually:

Reel-MBP:~ r$ diskutil mount /dev/disk3s2
Volume Preboot on /dev/disk3s2 mounted
Reel-MBP:~ r$ ls -l /Volumes/Preboot/
total 0
drwxr-xr-x  6 root  wheel  192  9 wrz 22:50 00B24073-D432-4C9A-AC90-468B0E3B7733
Reel-MBP:~ r$ 

In the HFS+ boot model, the kernel is hardcoded to look for the Recovery partition at the partition id minus 1 of the associated System partition. With APFS, a single APFS container can now contain multiple System volumes - but only a single Recovery/Preboot volume is required within the container, each of which can contain multiple GUID-named folders (one for each System volume).

Looking back at the information we got from the bless command, we can see that the boot.efi is in a subfolder within the GUID folder:

System/Library/CoreServices/boot.efi
<key>Path</key>
<string>\FD77CA06-84E9-42D0-B5FE-6295D28CBB2F\System\Library\CoreServices\boot.efi</string>

 

Edited by wodawoda

Share this post


Link to post
Share on other sites

Everything was just fine until I tried to update to Mojave 10.14.1, the update couldn't finish because of bless message, I had to disconnect my raid and fresh install in a single ssd, now mi raid is connected, but offline.. could somebody help me to make it work again?

Screen Shot 2018-11-06 at 6.08.08 PM.png

Share this post


Link to post
Share on other sites
On 10/4/2018 at 12:47 PM, Reel said:

MacOS isn’t booting a file off of the System volume (/dev/disk3s1), it’s booting the boot.efi file from the new APFS Preboot volume (/dev/disk3s2) that you’ll find inside APFS containers:


That may be right for a real mac with a normal apfs volume (single disk)  but I don't think it's right at all for a hackintosh with an APFS Raid volume (stripe with multiple disks)

I don't think you can boot directly from the Raid 0, either from Mojave volume or Preboot volume because it's not mounted yet.


On hackintosh, it boots from EFI (CLOVER, etc), then it gets the boot.efi (as well as other needed files) from either of the BOOT OS X partitions and not from the new APFS Preboot volume like you say (because raid is not mounted yet).

You're mixing two very different things ; Mojave in a single APFS disk with a Mojave in raid 0 with dual disks

You still had to modify BOOT OS X although you say "it’s booting the boot.efi file from the new APFS Preboot volume (/dev/disk3s2) that you’ll find inside APFS containers" ;)


You're just quoting things from this article: http://michaellynn.github.io/2018/07/27/booting-secure/

That article it's about single APFS volumes, not APFS Raid. The boot process it's very different.

 

Edited by Taruga

Share this post


Link to post
Share on other sites

Hi, just to tell you that the clean installation and update on an iMac 11.2Mid 2010 of 21.5 "with x2 SSD Kingston on RAID 0 16GB Ram has worked perfectly with the MacOS High Sierra Patcher Tool for Unsupported Macs, without APFS, only Mac OS Plus registered.
We have tried it as a resource since High Sierra does not allow to install natively in RAID volumes.


Just Use: http://dosdude1.com/highsierra/
 

For Mojave, maybe works too the http://dosdude1.com/movaje/ from dosdude1 to install on RAID 0 

 

Excellent day! .

Captura de pantalla 12.png

Captura de pantalla 11.png

Edited by eykaus

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By rdall96
      Hello everyone!
       
      I am fairly new to the world of Hackintosh. I recently moved my previous build into a smaller form factor. However, I am running into a series of problems with the USB ports on the new case and the new motherboard.
       
      Part List:
      - i7-7700k
      - Gigabyte Z270N Gaming 5
      - 16GB Trident Z RGB 3200 MHz
      - Sapphire RX 470
      - NZXT Kraken x62
      - NZXT H200 for the case
       
      Everything in the Hackintosh works just like it did before, nothing changed in the hardware department other than the motherboard (previously a gigabyte Z20X Ultra) and the case.
      This motherboard does not have any USB 2.0 ports in the back, there is only one header on the board, currently taken by the Kraken x62. The rest of the ports are all either USB 3.1 Gen1 or USB 3.1 Gen2, and the front of the case has 3.1 Gen1 ports as well.
       
      This is my current problem:
      When I plug something into either the type A or type C Gen2 ports, it works fine as a normal USB 3.x device with normal speeds, but when I plug something into any other USB port, it only works at lower 2.0 speeds. This is a big problem for me, since I have a few external devices that need the 3.0+ speeds and I don't know what to do.
      I tried to follow many different guides on how to patch USB ports, remove the limits, etc... But nothing seems to work.
       
      Please someone help me!
    • By angelo_ios
      EDIT: MacOS Mojave 10.14 ONLY I didn’t test 10.14.1! The EFI folder is compatible with High Sierra.
       
      Guide to installing 10.14 Mojave on a ASUS X555L
       
      What Works:
      -WiFi
      -Sound
      -Graphics (Intel)
       
      What doesn't Work:
      -Bluetooth
      -NVidia Web Drivers
      -Battery Indicator
       
      Used Kexts:
      Picture
       
      Clover setup:
      Clover plist is downloadable in this topic.
       
      Let's start
       
      Step one:
      First get a USB with 8+ GB of storage and a MacOS Mojave 10.14 installer from the AppStore.
       
      Partition the USB in a GUID style and 2 partitions, one partition HFS+ and one partition FAT32.
       
      In the FAT32 partition put the EFI Folder there.
       
      On the HFS+ partition get the MacOS Mojave .app using this command:
      sudo /Applications/Install\ macOS\ Mojave.app/Contents/Resources/createinstallmedia --volume /Volumes/USBNAME --applicationpath /Applications/Install\ macOS\ Mojave.app --nointeraction Lets install!
       
      Put the USB in a 3.0 port on the LEFT side of the Notebook.
       
      In the BIOS follow the default Hackintosh settings, do NOT forget to put Memory allocation to 64MB (Otherwise you won't boot)
       
      Boot into the Installer and install MacOS Mojave.
       
      Boot into MacOS. Now your Graphics are working but your WiFi and Sound are not! for the WiFi follow this video:
      https://www.youtube.com/watch?v=OxFsjhc-AuM Once rebooted WiFi is working! 
       
      For sound get the VooDooHDA.kext and place it into /Library/Extensions
       
      Reboot once again and your sound is now working flawlessly!
       
      My EFI Folder is downloadable

      config.plist
      EFI.zip
    • By dukzcry
      Here's my driver for LSI MegaRAID SAS family of controllers called SASMegaRAID.kext. This one was requested few times at InsanelyMac and other Mac-related communities.
      Download link https://github.com/dukzcry/osx-goodies/releases or https://www.insanelymac.com/forum/files/file/306-sasmegaraidkext/
      F.A.Q.:
      Q: I can't manage controller via supplied utility
      A: Only monitoring functional is supported, management is done via controller BIOS
      Q: Any chance to make cards based on SAS2208 chip work?
      A: Not currently, the chip belongs to the same family, but it requires a lot of handling different from common handling for supported cards.
      Q: The driver loads but my device doesn't show up anywhere in profiler. What should I do?
      A: Try inverting "PreferMSI" key value. It's under "Settings" dictionary in kext's plist. 
      Q: macOS doesn't see my volumes
      A: Set them as virtual (logical) disks in controller's BIOS. If no luck try "Uncontiguous enumeration.zip" version. See full issue report https://www.insanelymac.com/forum/forums/topic/285197-driver-for-lsi-megaraid-sas-family/?do=findComment&comment=1987665
      Q: Is it possible to push more from my setup?
      A: It may be.
      The plist from "Unsafe settings unlocked.zip" allows tweaking of dangerous options. Before playing with them you need to detach all HDDs with critical data and attach some spare HDD for doing the tweaks. The "MaxSGL" option is number of scatter gather list entries you controller can handle. The "MaxTransferSize" determines the maximum size of data transfer (in bytes) per request your controller can catch. If you set them to some enormously big value then they will be truncated to the max values your hardware can achieve (may still be not safe enough for successful data transfers). "MaxTransferSizePerSegment" does the same but for a single SGL entry (will never be larger than MaxTransferSize). For the tests you need to stick to the system.log and start a transfer of a >= 100gb data. If the settings you set are inappropriate, you'll see the I/O errors.
      Q: My Mac stopped to go sleep after i've loaded your kext.
      A: This is awaited. See https://www.insanelymac.com/forum/forums/topic/285197-driver-for-lsi-megaraid-sas-family/?do=findComment&comment=1986269 Use kext from "Unsafe settings unlocked.zip" and set "AllowSleep" key to true.
      Q: Your driver doesn't work for me. Are there any alternatives?
      A: Yes there is one https://www.insanelymac.com/forum/forums/topic/314799-guide-z820-el-capitan-the-great-guide-sucess/?do=findComment&comment=2556863
      Q: I get "mfiutil: mfi_open: not such file or directory" error
      A: It maybe that unit number of you device is not 0 (which is default). Try the following:
      $ ls /dev/mfi?
      /dev/mfi2
      $ sudo mfiutil -u 2
    • By TomZanna
      Buongiorno, ho installato Mac OS Mojave su un Acer A515-51-602C.

      CPU  Intel i5 8250U con UHD620
      GPU  Nvidia GeForce MX150
      RAM  8GB
      HDD  1TB
      WiFi Intel AC 3168
       
      Non funziona
      - Touchpad I2C
      - Audio
      - Batteria
      - Tasti FN
      - Lettore SD
      - Wifi (e mai funzionarà)
      - GPU dedicata (e mai funzionerà)
       
      Attualmente il touchpad è collegato tramite PS2 ma, se possibile, preferirei usarlo tramite I2C (posso cambiarlo dal BIOS).
      CLOVER.zip
      Report.zip
    • By GoggoneXCV
      Ciao a tutti,

      Sono in procinto di installare Mojave nel mio pc (vedi firma) in dual con Win10, ho già installato una volta Sierra nel mio vecchio pc, quindi armato di quella poca esperienza, provo ad installarlo anche in questo nella seconda SSD m2, solo che mi si blocca all'avvio, potreste darmi una mano nella configurazione di Clover?

      Grazie anticipatamente. 
×