![]() ![]() i had failed to do this originally however, and my firmware was several layers behind. the firmware updates fairly automatically with each install of newer OS. but it needed doing before i could move forward. Thanks in advance to my fellow Mac Pro enthusiasts!!Ībsolutely, the only reason i changed the firmware (it was less messing, more upgrading) because i knew full well from researching that the firmware i upgraded to was tried and tested on my mac, and also legit. I'd appreciate any advice, or workaround, to get this running. Can someone let me know what I'm missing here? Is it the 128Gb RAM modification? I have a vague memory of reading that the modification may affect Boot Camp, but my memory could be completely wrong here. Boot Camp ran just fine on my 3,1 with El Capitan. When I try to run Boot Camp it says, "Boot Camp Assistant cannot be used. Secondary OS Drive SATA SSD 1TB (Where I want to install Windows and/or a Linux OS).Primary OS Drive PCIE SSD 1TB (Where Mojave is).Processor 2 x 3.46 GHz 6-Core Intel Xeon.It died finally after over a decade of use, and so I bought a 5,1. Now when choosing Boot Camp from the Control Panel, you should get something similar to what is shown below.I had Boot Camp running just fine on my classic Mac Pro 3,1. Using the echo command is just a quick shortcut. ![]() Note: The correct way, to edit the /etc/fstab file, is to use the command sudo vifs. sudo bashĮcho "LABEL=Macintosh\040HD\040via\040rEFInd none hfs rw,noauto" >/etc/fstab Note: The character sequence \040 is just the octal representation of the space character. This entry will instruct macOS not to mount the volume labeled "Macintosh HD via rEFInd" at startup. Loader \System\Library\CoreServices\boot.efiĮnter the following commands to modify the /etc/fstab file. Icon \System\Library\CoreServices\icons\os_mac.png When finished, save the changes, then quit TextEdit. You should be able to just cut and paste these lines. open -e nfĪdd the following lines to the end of the nf file. Open the file in the TextEdit application. sudo cp nf Īdd write permissions to the CoreServices folder and the nf file. cd "/Volumes/Macintosh HD via rEFInd/System/Library/CoreServices" Use the command below to navigate to the folder containing the nf file. Uncheck all the "Options", as shown below. Open TextEdit, then navigate to the "Preferences." window. Note: The error message Could not set boot device property: 0xe00002bc was expected and can be ignored.Ĭonfigure the TextEdit application. Enter the following commands to install the software to the "Macintosh HD via rEFInd" volume. sudo diskutil ap resizeContainer disk1 223600M JHFS+ "Macintosh HD via rEFInd" 200MĪfter the command completes, restart the Mac.ĭownload the rEFInd Boot Manager software from this SourceForge web site. The diskutil command, shown below, shrinks the APFS container by 300 MB and creates the new 200 MB "Mac OS Extended (Journaled)" volume labeled "Macintosh HD via rEFInd". Note: You will have to replace "Macintosh HD" with the the name of your macOS volume.Ĭreate the new volume. The commands need to be entered into a Terminal application window. Finally, macOS will be instructed to not automatically mount this new volume at startup.īelow are the steps. ![]() ![]() This boot manager will then be configured to silently boot the macOS stored in the APFS container. Instead of placing macOS in the volume, a third party boot manager, called rEFInd, will be substituted. Since the Windows Boot Camp software can detect bootable "Mac OS Extended (Journaled)" volumes, the follow instructions create such a volume. However, if you do so, then the following will fix the problem you are having. Number Start (sector) End (sector) Size Code Nameġ 6 76805 300.0 MiB EF00 EFI System PartitionĪccording to Apple, you are not suppose to use the APFS with the Boot Camp Assistant application. Total free space is 2112456 sectors (8.1 GiB) Partitions will be aligned on 2-sector boundaries Main partition table begins at sector 2 and ends at sector 5įirst usable sector is 6, last usable sector is 122138127 Type device filename, or press to exit: 0:įound valid GPT with protective MBR using GPT.ĭisk identifier (GUID): 67089514-C692-4DF1-8679-633BDE4D77E6 When I ran the gdisk tool (based on this thread answer) to list the partition details, I see my mac partition (#2) has FFFF code (seems to be unknown) c:\Temp>gdisk64.exe In Windows session, in the bootcamp "Restart in macOS." option is returning "Could not locate the macOS boot volume." error. In my Macbook pro (2016 touch bar), previously I installed Windows 10 and upgraded to creators version. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |