Is anyone else having problems with the latest update?

 

My MBP has re-started, but has now had a grey screen for five hours. Looking on the web and I’ve seen comments ranging from ‘several hours’ to ‘up to 16 hours’ for the update to complete. Just wondered if anyone else is experiencing the same?

 

Gaz

 

 

Is this 10.15.5 you've just installed?   I've only noticed that it's available after I read your post.  I'll probably hold off installing it on my iMac for a while until there's a stable release. 

My MacBook Air had the latest 10.15.5 beta installed yesterday and all is OK.

TBH I don’t know if it’s 10.15.5, but it probably is.  Dave, did yours take a long time to complete? Mine’s not taken this long before, so I’m tempted to shut it down manually.

 

Gaz

 

 

Tried a restart with cmd & r, but it made no difference and has gone back to the same grey screen. Cooling fan is going full whack all the time too. Very frustrating!

 

Gaz

 

Response from an American friend of mine (who runs several Mac workstations and servers and tests betas). He's not aware of issues such as yours but suggests:

 

"He could try an SMC reset and zapping the PRAM. Those are the first two troubleshooting steps. After that is booting into recovery mode and running Disk Utility. If that passes, then use the 'reinstall' option (no data is lost, just the OS is reinstalled)"

 

Also:

 

"I'd power it off, then do the SMC reset and zap the PRAM.

https://support.apple.com/en-us/HT201295

Apple Support

How to reset the SMC of your Mac

Resetting the system management controller (SMC) can resolve certain issues related to power, battery, fans, and other features.

https://support.apple.com/en-us/HT204063

Apple Support

Reset NVRAM or PRAM on your Mac

If your Mac has issues related to settings stored in NVRAM or PRAM, resetting it might help."

 

HTH!

 

Wow, thanks for the reply Micky 👍

 

I left it running overnight just in case it was a time issue, but it clearly isn’t, so I’ll follow your suggestions and see how that goes.

 

Your reply and advice from your mate is very much appreciated 😎

 

Gaz

 

Sad to report that none of these worked. Although with different outcomes.  The SMC reset ended up with a totally black screen (I did check to see that it wasn’t just really dark). The NVRAM got it to chime twice, but I’m now back at square one and the grey screen.

 

Think I may need outside help 😢

 

Gaz

Hold the front page, something’s happening......

 

 

5 hours ago, IamGaz said:

Hold the front page, something’s happening......

 

 

That looks like it should do now.

 

I'm always amazed how long the reboot takes after an update, and as I'm on the public beta programme there are plenty of updates!

Back in business 😁

 

I did the NVRAM reset a second time and it sprung into life.

 

It was High Sierra 10.13.6 so not 10.15.5 at all.

 

Thanks again.

 

Gaz

Edited 5 June, 20205 yr by IamGaz

2 hours ago, IamGaz said:

It was High Sierra 10.13.6 so not 10.15.5 at all.

 

 

 

That might have been something to do with it if you've upgraded from 10.13.6 to 10.15.5 in one go.  I suspect it's better, from a security point of view if nothing else, to install each new update as they're made available. 

Edited 5 June, 20205 yr by Schtum

11 hours ago, Schtum said:

That might have been something to do with it if you've upgraded from 10.13.6 to 10.15.5 in one go.  I suspect it's better, from a security point of view if nothing else, to install each new update as they're made available. 

That's 2 major versions 10.13.x to 10.15.x IIRC there was some pretty significant disk format changes involved which would explain the very long time to update.

 

I agree that it's well worth keeping up-to-date - there have been quite a few security patches to macOS over recent months.

On 05/06/2020 at 23:13, Schtum said:

 

That might have been something to do with it if you've upgraded from 10.13.6 to 10.15.5 in one go.  I suspect it's better, from a security point of view if nothing else, to install each new update as they're made available. 

 

It was updating to 10.13.6, not to 10.15.5.  I'm not sure why it's not asking me to update to 10.15.5, and wonder it's probably something I've not done, or ignored.

 

It's a 2011 MBP, that I've had from new.  This was the first significant problem I've had with it.  The letter 'S' popped off a couple of months ago and it needed a new butterfly catch underneath the cap, which took all of about 20 seconds to fix, so it's doing really rather well.

 

Having said that it had another 'wobble' last night, out of the blue, while I was reading stuff on here.  It went back to the blank grey screen, then restarted (with no input from me), got about two thirds of the way across the progress bar, stopped, and then re-started.  And was stuck in that cycle.  So I switched it off (it's never usually switched off).  Started it up this morning and everything appears to be tickety boo.

 

So now I'm in a quandary as to whether to leave it, or update to 10.15.5 if I'm able to (i.e. if it's not too old).  Any thoughts?

 

Gaz

 

1 hour ago, IamGaz said:

 

It was updating to 10.13.6, not to 10.15.5.  I'm not sure why it's not asking me to update to 10.15.5, and wonder it's probably something I've not done, or ignored.

 

It's a 2011 MBP, that I've had from new.  This was the first significant problem I've had with it.  The letter 'S' popped off a couple of months ago and it needed a new butterfly catch underneath the cap, which took all of about 20 seconds to fix, so it's doing really rather well.

 

Having said that it had another 'wobble' last night, out of the blue, while I was reading stuff on here.  It went back to the blank grey screen, then restarted (with no input from me), got about two thirds of the way across the progress bar, stopped, and then re-started.  And was stuck in that cycle.  So I switched it off (it's never usually switched off).  Started it up this morning and everything appears to be tickety boo.

 

So now I'm in a quandary as to whether to leave it, or update to 10.15.5 if I'm able to (i.e. if it's not too old).  Any thoughts?

 

Gaz

 

 

 

Ahh I see.  Age might be the issue. As well as my iMac, I've got a 2011 Macbook Air which I haven't used in ages.  I'll fire it up and see if there's an update available for it. 

See Apple Support for compatibility with macOS 10.15 (Catalina), the 2011 MBP isn't included in that list.

 

Other articles suggest that the 2011 MBP isn't supported by macOS 10.14 (Mojave) either, so it seems macOS 10.13 (High Sierra) is the latest version for a 2011 MBP.

 

Having said that there does appear to be a patch that will allow older macs to install macOS 10.15 (Catalina), see Catalina Patch

Edited 7 June, 20205 yr by PetrolDave

I think the Patch sounds great, until you start reading the caveats like 'expect problems..'.

 

Think I'll just keep it going for as long as it can, then when the time comes 😱 ...... do the decent thing, and take it along to the People's Dispensary for old MBP's 😢

 

Ta for the replies.

 

Gaz

 

MBP currently in IT ITU 😨

 

Prognosis uncertain, but have been warned to expect the worst.

 

Starting to consider options.  Favourite so far is a new 16" MBP as Wifey has a Blue Light Card, so discounted direct from Apple and 24 months at 0%.

 

Currently using a spare Dell Latitude, which is a clunky old lump which has AVG telling me the world's going to end if I don't upgrade and start paying.

 

Gaz 

ITU advise hard drive faulty.  Temporary  HD used for testing and working fine.  Data on HD mostly recoverable.  HD being replaced with SSD.  Can't wait (well okay, having to) as ITU say it's condition is too good to just bin it 😎 

 

Gaz

 

Mac in business (pun intended).  All data recovered, new hard drive in, and working quite a bit faster than prior to the HD fault.

 

I suppose I shouldn't be surprised that the original HD is a Toshiba.

 

Very happy bunny 😁

 

Gaz

Being back in business didn't last long.  It went back to it's old tricks and ended up not firing up at all. The folks who put the new SSD in it said it was time to call it a day.

 

Thankfully I'd managed to do a complete back up a few days before onto a Samsung T5 SSD.

 

So off it goes to the place for dead MBP's. RIP my old friend.

 

It's 16" replacement arrived at 1:15pm this afternoon.  And is well, frankly astonishing.  Upload from the backup said it was going to take an hour and five minutes, but then it started transferring the data at 350mbps and it was all over and done with in just a few minutes.  The longest anything took was me going to the kitchen as I couldn't remember my payment card security number 🙄

 

Gaz