Automatic reboot vs. hardware (button) boot: wrong partition

Dear all,


I've recently changed my SSD cause it was broken (MacBook Pro mid2010).

I've installed a new one and set up OS high sierra.


Immediatly during the OS installation and ever since, my mac is booting into the correct partion with the button (hardware) and into "prohibited sign" with automatic reboot.


It's like the two commands, for some reasons, were connected to different roots.

I tried to reset SMC/PRAM, check the "start up" partition on settings and other few stuff.

But it remains a mistery. During the updates installation, during the installation of the OS itself, automatic reboot fails. Hardware switch off and on does the deal (= continue and finishing the installation).


Why is this happening ? I have the feeling reboot command tells the mac to restart from a partition is not there. But I have no other partion, I have one disk, formatted with one partition and notheing else (and hardware boot works).

It looks like a windows error, like "mac OS thinks reboot is on A:" but there's no "A:" listed in the booting list.


I am puzzeled.


Please let me know whether something come to your mind, it's not vital, it's just annoying and stupid.


Riccardo













MacBook Pro 13", macOS 10.15

Posted on Oct 22, 2019 12:37 AM

Reply

Similar questions

17 replies

Nov 6, 2019 11:24 AM in response to riiiic

Thought of something else to try and see what's happening. When next you do a reboot try holding the command+s keys after you hear the gong sound -- system will try to boot into single-user mode and you will see a bunch of text messages fly by. You should after 10-20 seconds get a prompt that says something like:


localhost:/ root$


and that means you are now in single-user mode if it got that far. You can continue the booting process by just typing the command:


exit


followed by the return/enter key. You will see lots more text messages and hopefully some sort of error message that might give a clue as to what the problem is. It might also get far enough to clear the screen and go into graphics mode or it might hang or ???


You could also look at the file /var/log/system.log and look for messages that are near the time of the hang -- so have some kind of watch that is synchronized with your Mac so that you can not at exactly what time the prohibited sign appears on the screen and then look for messages in the system.log file right around that time.


Also when you say "automatic reboot" does that mean you click on the Apple icon at top right of screen then click on the "Restart" menu item?


Also, did you ever do a safe boot (hold down the shift key during power-up? Does that make any difference?


Good luck...


Nov 6, 2019 1:39 PM in response to riiiic

My system shows some of these same commands, so not sure, but doubt these are the problem.


What do these commands show:


bless --info
bless --getboot
ls -lai /System/Library/Coreservices | head
ls -lai /System/Library/Coreservices/boot.efi
df -kt


You might need to precede these with "sudo" and then give your admin password at the prompt for the first couple of commands. Do you only have one boot volume on this Mac? I think yes but want to be certain.


Were there any problems when you created the macOS boot disk that system is now booting from? Has this prohibitory boot during restart problem always happened? Did you go thru a normal macOS High Sierra install on the new SSD (using the "Install macOS High Sierra.app" program) or did you do something like clone/copy the old disk to the new or ??? If you did do the clone/copy how exactly did you do it? I just looked at your OP again and it says that you did do a normal "Install macOS..." for High Sierra, but just want to make certain.


Good luck...

Nov 8, 2019 12:10 AM in response to dot.com

dot.com wrote:

My system shows some of these same commands, so not sure, but doubt these are the problem.

What do these commands show:

bless --info
bless --getboot
ls -lai /System/Library/Coreservices | head
ls -lai /System/Library/Coreservices/boot.efi
df -kt

Last login: Fri Nov  8 08:58:52 on ttys000


ric@MBP-di-Riccardo ~ % sudo bless --info                       


Password:


         612 => Blessed System File is {Preboot}/0AC8A298-BA61-4573-9E97-5A1128A424BC/System/Library/CoreServices/boot.efi


         500 => Blessed System Folder is {Preboot}/0AC8A298-BA61-4573-9E97-5A1128A424BC/System/Library/CoreServices


The blessed volume in this APFS container is "/".


No blessed APFS snapshot for this volume.


ric@MBP-di-Riccardo ~ % sudo bless --getboot                         


/dev/disk1s5


ric@MBP-di-Riccardo ~ % ls -lai /System/Library/Coreservices | head  


total 4128


1152921500311930630 drwxr-xr-x  183 root  wheel    5856  6 Nov 09:06 .


1152921500311902553 drwxr-xr-x  116 root  wheel    3712  6 Nov 08:20 ..


1152921500312397058 -rw-r--r--@   1 root  wheel     485  6 Nov 09:06 .disk_label


1152921500312397060 -rw-r--r--@   1 root  wheel       7  6 Nov 09:06 .disk_label.contentDetails


1152921500312397059 -rw-r--r--@   1 root  wheel    1925  6 Nov 09:06 .disk_label_2x


1152921500311979091 drwxr-xr-x    3 root  wheel      96  9 Set 02:15 AOS.bundle


1152921500311982158 -rwxr-xr-x    1 root  wheel   63872 24 Ott 02:40 APFSUserAgent


1152921500311973372 drwxr-xr-x    3 root  wheel      96  9 Set 08:48 AVB Audio Configuration.app


1152921500311944176 drwxr-xr-x    3 root  wheel      96 24 Ago 05:22 AddPrinter.app


ric@MBP-di-Riccardo ~ % ls -lai /System/Library/Coreservices/boot.efi


1152921500312396527 -rw-r--r--  1 root  wheel  592440  6 Nov 08:31 /System/Library/Coreservices/boot.efi


ric@MBP-di-Riccardo ~ % df -kt                                       


Filesystem    1024-blocks     Used Available Capacity     iused      ifree %iused  Mounted on


/dev/disk1s5    976557744 10738760 882934056     2%      483984 9765093456    0%   /


devfs                 225      225         0   100%         785          0  100%   /dev


/dev/disk1s1    976557744 78816540 882934056     9%      289466 9765287974    0%   /System/Volumes/Data


/dev/disk1s4    976557744  3146772 882934056     1%           2 9765577438    0%   /private/var/vm


map auto_home           0        0         0   100%           0          0  100%   /System/Volumes/Data/home


drivefs          31457280 10167132  21290148    33% 18446744069414590616 4294967295 293038031285378688%   /Volumes/GoogleDrive


ric@MBP-di-Riccardo ~ % 

ou might need to precede these with "sudo" and then give your admin password at the prompt for the first couple of commands. Do you only have one boot volume on this Mac? I think yes but want to be certain.

yes I had to put sudo :) for the first two.

ere there any problems when you created the macOS boot disk that system is now booting from? Has this prohibitory boot during restart problem always happened? Did you go thru a normal macOS High Sierra install on the new SSD (using the "Install macOS High Sierra.app" program) or did you do something like clone/copy the old disk to the new or ??? If you did do the clone/copy how exactly did you do it? I just looked at your OP again and it says that you did do a normal "Install macOS..." for High Sierra, but just want to make certain.

First time I installed via network connection to apple server, I couldn't download a proper copy from the app store, cause my HDD was broken and I've just installed a brand new SSD.

When this problem showed up, I have download High Sierra, put it in a USB key and do a "clean install", which didn't remove the problem.

Is this because Network Installation configure the boot sequence wrongly ?

Is it because my SSD is for some reason not recognize during the the "restart", because is not an "apple" HDD ? xD

Jokes aside, it all started at that moment, removing the HDD cause broken, install from network (power key then "cmd+C", not sure, but it opened a 1980 dialogue box with a computer connecting with a cable, after a while it started downloading and installing HS) .




Good luck...

Thanks a lot again.

Oct 27, 2019 8:52 AM in response to riiiic

Does the System Preferences "Startup Disk" show the correct boot disk?


Do you mean the "power button" where you say it starts Ok when you press "the button"?


What do these Terminal commands show? (three commands with a return after each -- please copy paste command and it's response if you reply):


diskutil list
df -kt
ls -la /Volumes



Good luck...

Oct 28, 2019 12:30 AM in response to dot.com

dot.com wrote:

Does the System Preferences "Startup Disk" show the correct boot disk?

Yes, it does

Do you mean the "power button" where you say it starts Ok when you press "the button"?

Yes, i'm sorry, I mean the power button

What do these Terminal commands show? (three commands with a return after each -- please copy paste command and it's response if you reply):

diskutil list
df -kt
ls -la /Volumes


Good luck...

Thanks a lot for your help.

Nov 6, 2019 12:06 PM in response to dot.com

Hello Thanks for your reply.


You could also look at the file /var/log/system.log and look for messages that are near the time of the hang -- so have some kind of watch that is synchronized with your Mac so that you can not at exactly what time the prohibited sign appears on the screen and then look for messages in the system.log file right around that time.

Here is the log file.


lso when you say "automatic reboot" does that mean you click on the Apple icon at top right of screen then click on the "Restart" menu item?

Apple_Sign-->restart

Restart during update

Restart after an installation that requires it.


Anything that cause a "restart", it ends into a forbidden sign.


Forbidden sign -->hold power key (switch off) -->push power key ---> "hardware boot" ---> complete installation/update --->log in


I'll try the cmd+S later.

Nov 6, 2019 12:10 PM in response to riiiic

"failed to bootstrap path" ? could this be it?


Nov 6 20:45:24 MacBook-Pro-di-Riccardo Installer Progress[88]: Unregister process 122, phaseName loginwindow Boot, uuid 56ACB1ED-135C-4FBC-B78B-1CC636F7638B

Nov 6 20:45:25 MacBook-Pro-di-Riccardo Installer Progress[88]: Releasing the boot windows

Nov 6 20:45:28 MBP-di-Riccardo xpcproxy[262]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

Nov 6 20:45:30 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.findmydeviced.261): Failed to bootstrap path: path = /usr/libexec/findmydeviced, error = 108: Invalid path

Nov 6 20:45:31 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mdmclient.277): Failed to bootstrap path: path = /usr/libexec/mdmclient, error = 108: Invalid path

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.CoreAuthentication.agent.plist, error = 17: File exists

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.MemorySlotNotification.plist, error = 138: Service cannot be loaded on this hardware

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.trustd.agent.plist, error = 17: File exists

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.eospreflightagent.plist, error = 138: Service cannot be loaded on this hardware

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.ExpansionSlotNotification.plist, error = 138: Service cannot be loaded on this hardware

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.ctkd.plist, error = 17: File exists

Nov 6 20:45:36 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.user.domain.501.100005.Aqua): Failed to bootstrap path: path = /System/Library/LaunchAgents/com.apple.CommCenter-osx.plist, error = 138: Service cannot be loaded on this hardware

Nov 6 20:45:39 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.diskarbitrationd.87): Failed to bootstrap path: path = /usr/libexec/diskarbitrationd, error = 108: Invalid path

Nov 6 20:45:58 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.CoreLocationAgent[402]): Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.CoreLocation.agent

Nov 6 20:45:59 MBP-di-Riccardo xpcproxy[422]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

Nov 6 20:46:06 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.remindd.367): Failed to bootstrap path: path = /usr/libexec/remindd, error = 108: Invalid path

Nov 6 20:46:41 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.UserEventAgent.290): Failed to bootstrap path: path = /usr/libexec/UserEventAgent, error = 108: Invalid path

Nov 6 20:46:44 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.routined.347): Failed to bootstrap path: path = /usr/libexec/routined, error = 108: Invalid path

Nov 6 20:50:31 MBP-di-Riccardo com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.mdmclient.596): Failed to bootstrap path: path = /usr/libexec/mdmclient, error = 108: Invalid path

Nov 6 20:50:33 MBP-di-Riccardo xpcproxy[600]: libcoreservices: _dirhelper_userdir: 557: bootstrap_look_up returned (ipc/send) invalid destination port

Nov 6 20:54:28 localhost bootlog[0]: BOOT_TIME 1573070068 0

Nov 6 20:54:29 localhost com.apple.xpc.launchd[1]: rc.server: optional boot task not present

Nov 6 20:54

Nov 8, 2019 8:24 AM in response to riiiic

Wait a minute -- back the truck up!!!!


This 2010 MacBook won't run Catalina so how did you ever install the OS on it? Did you use the DosDude1 installer trick? The normal Catalina installer will not let you install catalina on unsupported hardware. The DosDude1 installer will however, but it has a special install procedure. Is this what happened?


If that is the case did you follow the complete DosDude1 install procedure, and do the "Post Install" step and follow all his procedure?


More details on how you got Catalina on this 2010 MacBook please.


If you want to install High Sierra from Apple, then say so.


Good luck...

Nov 10, 2019 4:44 AM in response to dot.com

Hello, thanks for your reply.

I'm trying to go back to anything.

I have this problem since the 14.4.2019, when I installed the new SSD disk and installed High Sierra on it via APPLE server.

I tried to ask the official apple support centre, via genius bar and calling them. The answer was always "PRAM, VRAM, SMC reset", together with "don't call again cause your machine is not officially supported anymore".

Nothing worked.

Installing high sierra with a clean installation via USB didn't work.

I gave a try to Catalina, installed as you guessed, but nothing changed either.

My Mac is 10 years old in few months, It's an annoying problem, but not vital as I said, switching off and on do the deal.

Since it started with High Sierra I posted it in High Sierra.

As this happens before even booting, I'm start to think it is an issue that comes from the new disk itself.

Either the disk itself is not well configurated or it is imply not recognise during the "restart" process.

I bet If I could put the old disk on, this would stop to happen. But I can't do it since the disk is broken.

Anyway, thanks a lot, I am planning to buy a new one soon.


Riccardo




This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Automatic reboot vs. hardware (button) boot: wrong partition

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.