I have followed all other routes of troubleshooting including trying a known good replacement PSU.īuy my issue currently is that it appears I cannot get the Mac Pro 3,1 to boot from that USB So, I want to more thoroughly diagnose (what I suspect to possibly be) a logic board / logic board component issue(s). (somehow it doesn't feel right to jump in the car for a two hour drive to a different area to hand it over to a service technician and put others at risk right now, and fortunately others seem to agree and have been very helpful - some things are more important than fixing a Mac!). I intend to use the ASD-3S123 (Apple Service Diagnostic tool specifically for the Mac Pro 3,1 - which I have created on a bootable USB with the suggested EFI and OS boot partitions) using the helpful advice here - and verified from other qualified sources keen to assist whilst we are in lockdown due to Covid restrictions. I have a mac pro 3,1 I am not yet ready to consign to the dump as it is clean and runs well except for the frequently reported black screen crash and fans on full problem - after anything between two minutes and 2hrs or so (record recently is 2:45hrs) Running Apple Service Diagnostic from USB boot thumb drive Hi Apple Community, Rm -rf Boot (i saw it on some YT video and they said it might help) Sudo mount -t msdos /dev/disk0s1 /Volumes/EFI These are the commands i've used so far to try and fix the problem: it does have the same storage and the same disk number as the EFI partition had before it changed somehow.Ģ: Apple_CoreStorage macOS 249.2 GB disk0s2ģ: Apple_Boot Recovery HD 650.0 MB disk0s3 another is that when doing diskutil list in terminal, instead of EFI type and a name EFI, it now shows "Apple_HFS" instead and doesn't have a name. a lot of developments though have occurred since i last did those, and one is that it doesn't show up anymore on the bootable drives list when pressing option upon startup. i have tried numerous methods but they have not worked at all. i think this first showed up after i wiped out windows without using bootcamp. i have a problem regarding this lingering efi partition in my mac which is hindering me from installing windows through bootcamp. I have a macbook pro mid 2012 13", running on macos x el capitan. I am using a 13" 2015 MacBook Pro with Retina display on macOS High Sierra 10.13.6 Running " mkdir /Volumes/efi" and then " sudo mount -t msdos /dev/disk0s1 /Volumes/efi" both as root now allows me to mount the EFI partition normally via "diskutil mount disk0s1", but does not fix BootChamp.įYI holding option at boot does allow me to go to windows. I have not tried First Aid in disk utility or re-installing the BootChamp app yet. Running "/sbin/fsck -fy" from single-user mode Running the command " sudo /usr/sbin/bless -mount /Volumes/BOOTCAMP/ -setBoot -nextonly -verbose" as a suggestion from this link: output from terminal I get is this: Disabling system integrity protection via recovery mode terminal after resetting SMC/NVRAM (SIP was also off before resetting those 2) Resetting SMC via shut down, and then holding control+option+shift+power button for 10 seconds, and then booting up Resetting PRAM and NVRAM via command+option+p+r after boot chime I need the ability to use BootChamp back. After further investigation, I also found I was unable to mount the EFI partition via "diskutil mount disk0s1". After the new macOS 10.13.6 update, my ability to use BootChamp to quickly switch to Windows 10 from macOS via one-time next only boot is gone.
0 Comments
Leave a Reply. |