- Feb 7, 2019
after update to 10.14.3 supplemental update, reboot, unable to get resources
can not use mv bootcaches menthod
can not use mv bootcaches menthod
That's what I did. I my case, the RAID never reappeared as a bootable drive. But I may have goofed. Anyone else?So, if I understand correctly, updating via the normal software update mechanism in settings worked for 10.14.1 and 10.14.2, but renders the system unbootable after 10.14.3? A clean install of the operating system using the 10.14.3 installer is successful? Sounds like the kernel was updated, and the kernel cache needs to be rebuilt. Try allowing the system to boot with the bootcaches plist in place, and rename it after the first reboot
Well done! Do you remember what the kernel flags were? It certainly sounds like it was trying to do something odddone!!!
mount the Boot OS X drive, and edit /com.app.boot.P/com.app.Boot.plist, remove Kernel Flags
be cos it mount the baseboot.dmg?,so every time reboot in os will see the error message.
@tiyo may be the best person to reply, but I understand you need to remove any additional kernel flags from the com.apple.boot.plist file on your Boot OS X helper partitions. They need to match the example in the first post, with nothing listed under the Kernel Flags string and your Root UUID marching the UUID of your array partition.So what exactly needs to be done?
cd /Volumes/Macintosh\ RAID/usr/standalone/ mv bootcaches.plist bootcaches.plist.bak
That's a pity. It should work fine. I'm glad you eventually got it working, but it's disappointing you've had so much troubleI can confirm that everything works on my Mac Pro 5.1 with 10.14.4.
When I run the required commands within the installer and reboot – Mojave never boots and I cannot set it as a boot drive again. So I have to shutdown my Mac Pro right after the installer gives the bless error, which allows MP go into an infinite boot loop mode, and then boot into a single user mode and execute the required commands there. This is a bit annoying as I have to physically switch between my video cards all the time.
It's definitely caused by SIP. Boot into recovery mode (Cmd+R) or single-user mode (Cmd+S), run csrutil disable, reboot back into Recovery mode or single-user mode, move the bootcaches plist file out of the way, run csrutil enable, and then reboot back into normal mode. Moving the bootcaches.plist in the installer is easier because SIP is already disabled but once you've rebooted you'll have to disable it yourself to complete the process. This may also involving swapping out your video card to get into single user mode and back.I’m having an error “operation not permitted” while trying to rename bootcaches from single user boot mode. SIP perhaps?
What could I do?
I’ve seen SoftRAID mentioned a few times, but I’ve never used it and I don’t know it’s boot process. If it’s free and documented I might be able to look into it, but I have a lot of other projects on the go!Has anybody gotten Mojave to work on SoftRAID?
I tried it with a RAID 0 HFS+ install and failed
Yes, the same method works in macOS 10.15 Catalina Beta (19A471t). The main trick is to format the drive in HFS instead of APFS. I used a VMware method to install Catalina using a raw disk access and then booted my Mac from the assembled RAID. All RAID preparations were done in macOS and not within VMware, as keyboard does not work when installing Catalina in VMware.Has anyone have tested if RAID 0 in APFS still works on macOS Catalina?
Good work! You can also use the shorthand ‘-t hfs+’ from memory. I know macs and VMware treat early boot differently, so I’ll double check it tonightYes, the same method works in macOS 10.15 Catalina Beta (19A471t). The main trick is to format the drive in HFS instead of APFS. I used a VMware method to install Catalina using a raw disk access and then booted my Mac from the assembled RAID. All RAID preparations were done in macOS and not within VMware, as keyboard does not work when installing Catalina in VMware.
This step in the instructions:
gpt add -b 409640 -s 59440560 -i 2 -t apfs /dev/disk9
Should be this:
gpt add -b 409640 -s 59440560 -i 2 -t 48465300-0000-11AA-AA11-00306543ECAC /dev/disk9
After creating this partition, it has to be formatted as HFS:
newfs_hfs -J -v Macintosh\ RAID /dev/disk9s2