Mfcttrf

Why did they use ultrafast diodes in a 50 or 60 Hz bridge?

Notation clarity question for a conglomerate of accidentals

Does Bank Manager's discretion still exist in Mortgage Lending

Why is music is taught by reading sheet music?

Why not add cuspidal curves in the moduli space of stable curves?

Can I bring this power bank on board the aircraft?

Do jackscrews suffer from blowdown?

Why does the Pilatus PC-24 have such a large "Wing Support"?

Does publication of the phone call ruin the basis for impeachment?

What powers or limits devil promotion?

Question about modelling birdcage

Using 4K Skyrim Textures when running 1920 x 1080 display resolution?

How to identify whether a publisher is genuine or not?

How dangerous are my worn rims?

Did the Soviet army intentionally send troops (e.g. penal battalions) running over minefields?

What is the difference between increasing volume and increasing gain?

Is elastic wiring feasable?

Can Fabled Passage generate two mana with Amulet of Vigor?

How to refresh wired service getRecord manually?

French license plates

Single tx included in two different blocks

Manager told a colleague of mine I was getting fired soon

Why has Speaker Pelosi been so hesitant to impeach President Trump?

How to "Start as close to the end as possible", and why to do so?

Mac no longer boots

Macbook (2,1) boots into blue screen and hangsMacBook Pro won't boot anymore after a fallMacBook Pro only boots to grey Apple screen with spinning loaderMacBook Pro Yosemite hangs during bootMacBook Pro Boots only with a pressed keyiMac Won't Boot Any Disk — Keeps RestartingPanic Medic Boot Appearing on MacBrightness settings stuck after computer shut down in bootcamp

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

10

1

I’ve been using my Mac all year without fear. On Tuesday I shut it down as I was going out of town. Today, I tried booting up my Mac and it won't boot.

I tried resetting PRAM and SMC, but no go. I did the command D thing, but no issues reported.

mac boot

share|improve this question

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  Which Mac do you have and which macOS is it running?
  
  – lhf
  11 hours ago
  

  
  
  
  

add a comment
 | 

10

1

I’ve been using my Mac all year without fear. On Tuesday I shut it down as I was going out of town. Today, I tried booting up my Mac and it won't boot.

I tried resetting PRAM and SMC, but no go. I did the command D thing, but no issues reported.

mac boot

share|improve this question

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  3
  

  
  
  
  
  
  

  
  
  Which Mac do you have and which macOS is it running?
  
  – lhf
  11 hours ago
  

  
  
  
  

add a comment
 | 

I’ve been using my Mac all year without fear. On Tuesday I shut it down as I was going out of town. Today, I tried booting up my Mac and it won't boot.

I tried resetting PRAM and SMC, but no go. I did the command D thing, but no issues reported.

mac boot

share|improve this question

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited 41 mins ago

GGMG

10333 bronze badges

edited 41 mins ago

GGMG

10333 bronze badges

asked 14 hours ago

user347757user347757

5944 bronze badges

New contributor

user347757 is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 14 hours ago

user347757user347757

5944 bronze badges

1 Answer
1

active

oldest

votes

33

I’m going to jump out on a limb here and make the assumption that you’re probably a Chrome user and before you went away you updated Chrome.

If so, you're probably the victim of a Chrome updater bug and your issues are not related to your Apple hardware nor a bug with macOS.

NOTE: If you're running Mac OS X El Capitan or later and have not disabled SIP, then this will not be the cause of your problem, in which case you'll need to skip this answer and investigate other causes!

To rectify this, you need to follow these steps:

1. Boot into recovery mode by using the commandR keyboard shortcut upon powering up your Mac.




2. When you see the macOS Utilities window, go to the Utilities menu bar option and select Terminal



3. 
   

   In terminal, enter the following commands one by one, followed by pressing the enter key (NOTE: If your Mac hard drive is not called Macintosh HD then you will need to change the first command below to reference the name of your hard drive)

   
   
   

   chroot /Volumes/Macintosh HD
   rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
   mv var var_back
   ln -sh private/var var
   chflags -h restricted /var
   chflags -h hidden /var
   xattr -sw com.apple.rootless "" /var
   

   
   



4. Now reboot your Mac.

Further reading:

You may be interested in reading:

• Issue 1007358: Keystone modifies /var


• Chrome Update Impacts Some macOS Systems

share|improve this answer

edited 11 hours ago

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  How did you think of this, given the OP description of the problem?? The Chrome bug only affects systems with SIP disabled.
  
  – lhf
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  OMG! This freaking worked! You totally saved me!!
  
  – user347757
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  11
  

  
  
  
  
  
  

  
  
  @lhf Yeah, like I said, I was going out on a limb with my answer. My thought process was as follows: Many Uni students use Chrome because of its integration with Google’s services and because many online Uni dashboards have some compatibility issues with Safari. That, along with the timing of two days ago meant that it lined up with the timing of the Chrome update. As an aside, SIP only needs to be disabled if the user is running El Capitan or later (obviously) so this issue can affect other systems. In this case we don’t have that info re the OP either way.
  
  – Monomeeth♦
  11 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf By the way, thanks for your comment. I've updated my answer to provide additional info to help other users decide if this applies to them.
  
  – Monomeeth♦
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf the Chrome bug also affects systems that don't support SIP. I suspect the number of those is far higher than the number of systems with SIP disabled.
  
  – abligh
  3 hours ago
  

  
  
  
  

add a comment
 | 

33

I’m going to jump out on a limb here and make the assumption that you’re probably a Chrome user and before you went away you updated Chrome.

If so, you're probably the victim of a Chrome updater bug and your issues are not related to your Apple hardware nor a bug with macOS.

NOTE: If you're running Mac OS X El Capitan or later and have not disabled SIP, then this will not be the cause of your problem, in which case you'll need to skip this answer and investigate other causes!

To rectify this, you need to follow these steps:

1. Boot into recovery mode by using the commandR keyboard shortcut upon powering up your Mac.




2. When you see the macOS Utilities window, go to the Utilities menu bar option and select Terminal



3. 
   

   In terminal, enter the following commands one by one, followed by pressing the enter key (NOTE: If your Mac hard drive is not called Macintosh HD then you will need to change the first command below to reference the name of your hard drive)

   
   
   

   chroot /Volumes/Macintosh HD
   rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
   mv var var_back
   ln -sh private/var var
   chflags -h restricted /var
   chflags -h hidden /var
   xattr -sw com.apple.rootless "" /var
   

   
   



4. Now reboot your Mac.

Further reading:

You may be interested in reading:

• Issue 1007358: Keystone modifies /var


• Chrome Update Impacts Some macOS Systems

share|improve this answer

edited 11 hours ago

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  How did you think of this, given the OP description of the problem?? The Chrome bug only affects systems with SIP disabled.
  
  – lhf
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  OMG! This freaking worked! You totally saved me!!
  
  – user347757
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  11
  

  
  
  
  
  
  

  
  
  @lhf Yeah, like I said, I was going out on a limb with my answer. My thought process was as follows: Many Uni students use Chrome because of its integration with Google’s services and because many online Uni dashboards have some compatibility issues with Safari. That, along with the timing of two days ago meant that it lined up with the timing of the Chrome update. As an aside, SIP only needs to be disabled if the user is running El Capitan or later (obviously) so this issue can affect other systems. In this case we don’t have that info re the OP either way.
  
  – Monomeeth♦
  11 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf By the way, thanks for your comment. I've updated my answer to provide additional info to help other users decide if this applies to them.
  
  – Monomeeth♦
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf the Chrome bug also affects systems that don't support SIP. I suspect the number of those is far higher than the number of systems with SIP disabled.
  
  – abligh
  3 hours ago
  

  
  
  
  

add a comment
 | 

33

I’m going to jump out on a limb here and make the assumption that you’re probably a Chrome user and before you went away you updated Chrome.

If so, you're probably the victim of a Chrome updater bug and your issues are not related to your Apple hardware nor a bug with macOS.

NOTE: If you're running Mac OS X El Capitan or later and have not disabled SIP, then this will not be the cause of your problem, in which case you'll need to skip this answer and investigate other causes!

To rectify this, you need to follow these steps:

1. Boot into recovery mode by using the commandR keyboard shortcut upon powering up your Mac.




2. When you see the macOS Utilities window, go to the Utilities menu bar option and select Terminal



3. 
   

   In terminal, enter the following commands one by one, followed by pressing the enter key (NOTE: If your Mac hard drive is not called Macintosh HD then you will need to change the first command below to reference the name of your hard drive)

   
   
   

   chroot /Volumes/Macintosh HD
   rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
   mv var var_back
   ln -sh private/var var
   chflags -h restricted /var
   chflags -h hidden /var
   xattr -sw com.apple.rootless "" /var
   

   
   



4. Now reboot your Mac.

Further reading:

You may be interested in reading:

• Issue 1007358: Keystone modifies /var


• Chrome Update Impacts Some macOS Systems

share|improve this answer

edited 11 hours ago

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  How did you think of this, given the OP description of the problem?? The Chrome bug only affects systems with SIP disabled.
  
  – lhf
  12 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  4
  

  
  
  
  
  
  

  
  
  OMG! This freaking worked! You totally saved me!!
  
  – user347757
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  11
  

  
  
  
  
  
  

  
  
  @lhf Yeah, like I said, I was going out on a limb with my answer. My thought process was as follows: Many Uni students use Chrome because of its integration with Google’s services and because many online Uni dashboards have some compatibility issues with Safari. That, along with the timing of two days ago meant that it lined up with the timing of the Chrome update. As an aside, SIP only needs to be disabled if the user is running El Capitan or later (obviously) so this issue can affect other systems. In this case we don’t have that info re the OP either way.
  
  – Monomeeth♦
  11 hours ago
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf By the way, thanks for your comment. I've updated my answer to provide additional info to help other users decide if this applies to them.
  
  – Monomeeth♦
  11 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @lhf the Chrome bug also affects systems that don't support SIP. I suspect the number of those is far higher than the number of systems with SIP disabled.
  
  – abligh
  3 hours ago
  

  
  
  
  

add a comment
 | 

I’m going to jump out on a limb here and make the assumption that you’re probably a Chrome user and before you went away you updated Chrome.

If so, you're probably the victim of a Chrome updater bug and your issues are not related to your Apple hardware nor a bug with macOS.

NOTE: If you're running Mac OS X El Capitan or later and have not disabled SIP, then this will not be the cause of your problem, in which case you'll need to skip this answer and investigate other causes!

To rectify this, you need to follow these steps:

1. Boot into recovery mode by using the commandR keyboard shortcut upon powering up your Mac.




2. When you see the macOS Utilities window, go to the Utilities menu bar option and select Terminal



3. 
   

   In terminal, enter the following commands one by one, followed by pressing the enter key (NOTE: If your Mac hard drive is not called Macintosh HD then you will need to change the first command below to reference the name of your hard drive)

   
   
   

   chroot /Volumes/Macintosh HD
   rm -rf /Library/Google/GoogleSoftwareUpdate/GoogleSoftwareUpdate.bundle
   mv var var_back
   ln -sh private/var var
   chflags -h restricted /var
   chflags -h hidden /var
   xattr -sw com.apple.rootless "" /var
   

   
   



4. Now reboot your Mac.

Further reading:

You may be interested in reading:

• Issue 1007358: Keystone modifies /var


• Chrome Update Impacts Some macOS Systems

share|improve this answer

edited 11 hours ago

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

share|improve this answer

edited 11 hours ago

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges

answered 14 hours ago

Monomeeth♦Monomeeth

52.9k1010 gold badges112112 silver badges158158 bronze badges