Supplemental update 10.13.3 installation issue

[Abaddon]

Morning all,

 

Irritating issue here - have a Mac Mini running High Sierra (which wouldn't install on the mirror, but that's another story!), which is saying that Supplemental Update 10.13.3 needs installing. The problem is, I have - several times now. It gets installed, then a short time after rebooting it says there was an installation error, and asks for it again. Or it doesn't say there was an error at all but just indicated that the update still needs doing.

 

I have a Carbon Copy clone of the boot disk (which is a mirror on the Mini), and I have tried to do it on this one as well in case it was a RAID install error (the High Sierra update wouldn't install on the RAID mirror, so I had to CC it on to an external HDD and do it there, then clone it back), but it doesn't matter which disk it boots from, it just won't seem to install the update properly.

 

Any ideas? Can't find anything similar on t'interweb at the moment..

[Koldov]

Just giving this a bump and registering my interest...

 

Having a similar problem (not such a complicated set-up though).

 

Going round in a circle... You have a 10.13.3 update... OK... Download... Install.... Restart.... About this Mac = 10.13.1...

 

No error given though, just wait a couple of days... You have a 10.13.3 update...

 

I even did this manually!

 

 

Still got no error and 10.13.1

[Abaddon]

Glad it's not just me! The only difference is that when I look in "About this Mac", it does actually say "10.13.3" - it just keeps coming back up again as an update anyway.

[mandril]

same here.. I also have MacMini with Mirrored RAID (2 internal HDs). I tried the 10.13.3 update and it failed. Now it keeps asking to update to 10.13.3. But About your Mac already shows 10.13.3 I am also going to try to carbon clone my hard drive to an external and do the update there but OP said that didn't work for him. Maybe the OS installation is messed up already from the failed update. Might need to do a clean install to fix? What do you guys think? I really would prefer not to.

[Koldov]

So, a little update if anyone needs it...

 

I got tired of messing around reinstalling this update, I thought it may have been due to using VNC to access the Mac and so I actually went to the server room and ran the update 'in person' so to speak (thought it may have something to do with not being able to write some files when I get disconnected from the session as it shuts down or something).

 

Anyway, it installed (as usual) and this time asked me to do some of the usual questions on start-up (looking good I thought)....

 

No, still 10.13.1...

 

Well, back to Google (I'm surprised there isn't more about it on here as Google is returning quite a few hits now) and there are all sorts of weird and wonderful workarounds.

 

From cloning the disk and then starting the Mac with the cloned disk, but choosing the deployment to go to the original disk (due to some believing the update fails to write to an OS disk in use).

 

Or deleting whole partitions, creating new ones and running the update from there (I also think there is a lot of confusion about what update is actually needed as it appears there are different ones depending on your Mac). There are combos, supplementals and all sorts....

 

And also something to do with not having a recovery partition on your disk or something along those lines (as it tries to create one).

 

Honestly, they all looked far too difficult for me, so I skimmed them when it got comlpicated...

 

In the end I plumped for the 'reinstall(?)' of the OS (not really, but I'm a bit hazy with MacOS and its terminology). Essentially I downloaded High Sierra (10.13.3) from the app store and ran it!

 

Took a while but eventually booted up again, and indeed 10.13.3 was installed. I don't seem to have lost anything, but it isn't a mission critical bit of kit (was bought in anger to manage iPads about 3 years ago and hasn't been used since).

 

After that it found a 'supplemental update (10.13.3)....? So I ran that too and it seems all is good.

 

The only thing I didn't like was the fact that it installed a new version of the 'Server' app and I now can't seem to find the 'bytes served' option in statistics (as this is what I used to verify the 'Caching Server' was working)... But hey ho...

 

YMMV

Edited March 15, 2018 by Koldov