mac OS Installer lingers after failed Mojave 10.14.3 to 10.14.4 update

I’ve worked this problem w Apple Mac L2 across two phone calls lasting a total of 5 hours and escalation to L3 without a possible resolution, hence opening up my search to the world.

Ultra condensed sequence of events starting Wed, Apr 17:

  1. The 14.3 to 14.4 upgrade is supported through multiple reboot sequences, and between reboots 1 and 2, the update became irrevocably damaged (long unresolved story w L2 and L3 as to how they believe it happened based on my step by step explanation of how this occurred).
  2. The result is a lingering disk image called “mac OS Installer” that’s only visible when booting w Startup Manager. This means that (Mojave) Disk Utility, “About this Mac – Storage”, Recovery OS, and Internet Recovery OS cannot see my main “Macintosh HD” as they all permanently hang on “Locating Disks”.

Current status and how I worked around the problem:

  1. I can boot my partially updated and totally unreliable 14.3 image using Startup Manager, however it’s no longer a production environment.
  2. I bought another 1 TB SSD and replaced my existing optical drive in my Mid 2012 MBP w a Data Doubler (DD). The new SSD went into the main drive bay and the now damaged original SSD is in the DD in the optical bay (both the main and optical bay’s SATA are 6G, and both SSDs are identical 6G’s).
  3. Installed a fresh 14.4 on the new SSD and recovered my data from my cloud based backup service – thankfully, no issues

  4. Because of what I explained in #2, I cannot reformat my original SSD that contains the “mac OS Installer” image that now resides in my DD in the optical bay as I plan on using the second SSD for backup and other dev/test work.

My ask: What are the step by step instructions to delete a disk imaged called “mac OS Installer” that was left during a irrevocably failed 14.3 to 14.4 upgrade?

Thank you

Per Steve’s request, here’s the diskutil list enter image description here

here’s the permanent hang on Disk Utility from the fresh 10.14.4 in the main drive bay enter image description here

Text Clippings in macOS 10.14.3 Don’t Wrap

Now that I’ve upgraded to macOS 10.14.3 (from 10.10.5), text clippings in the Finder no longer wrap to the window width, and they also inherit the background that was behind the text when it was dragged to the Desktop.

Text clippings will properly wrap their text when they are opened through QuickView (via the spacebar), but when double-clicked, they do not.

Is there any way to restore the traditional, previous behavior of text clippings, such that the text wraps within the window, and has only a white (or black) background? I have hundreds that I use in my work . . . 

FYI, text clippings are now plists! Finally . . . Yea!!

😉

(I had “Greetings, folks!” as the opening sentence, but it kept getting truncated to just “, folks!” Weird . . . )

Can’t Boot My 10.14.3 Mac Pro Into Internal Recovery Mode

< 3.5 GHz, 6-Core Mac Pro (MacPro6,1) with 16GB RAM and D700 GPUs, running macOS 10.14.3 >

Greetings, folks!

I am baffled that I cannot boot my Mac into Recovery Mode after a clean install of 10.14.3. (I have poured through this site’s related pages!) I have plugged my keyboard directly into the Mac Pro, bypassing the hub, and tried multiple ways of holding down cmd-r during the boot process including prior to pressing the power button. I have no problem booting the Mac into Internet Recovery Mode (cmd-opt-r). Holding down the option key on boot does nothing; the Mac just boots normally. Holding down the shift key will bring up the login screen.

diskutil reports that the recovery volume exists and is valid. The calls returned below are:

  • diskutil list (with and without an external drive mounted)
  • diskutil verifyVolume disk1s3
  • diskutil cs list
  • sudo gpt -r show /dev/disk0

I had even downloaded and installed the recovery update, macOSUpd10.14.2.RecoveryHDUpdate.pkg, on multiple volumes, but still with no luck.

Any thoughts on why my Mac doesn’t respond to cmd-r?

Are there any shell scripts or AppleScripts that can be used to force the Mac to boot into the Recovery HD? (I can’t imagine . . . )

Blessings, and thank you!!

Richard Fairbanks


6-251-76-76:~ Me$   diskutil list /dev/disk0 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *500.3 GB   disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:                 Apple_APFS Container disk1         500.1 GB   disk0s2  /dev/disk1 (synthesized):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      APFS Container Scheme -                      +500.1 GB   disk1                                  Physical Store disk0s2    1:                APFS Volume Cupid                   370.2 GB   disk1s1    2:                APFS Volume Preboot                 45.9 MB    disk1s2    3:                APFS Volume Recovery                517.0 MB   disk1s3    4:                APFS Volume VM                      2.1 GB     disk1s4  /dev/disk2 (external, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *4.0 TB     disk2    1:                        EFI EFI                     209.7 MB   disk2s1    2:                  Apple_HFS Cupid Clone             500.0 GB   disk2s2    3:                  Apple_HFS OS X 1                  40.0 GB    disk2s3    4:                 Apple_APFS Container disk3         40.1 GB    disk2s4    5:                  Apple_HFS Applications            100.0 GB   disk2s5    6:                  Apple_HFS Me                      1000.0 GB  disk2s6    7:                  Apple_HFS Miscellaneous           2.3 TB     disk2s7  /dev/disk3 (synthesized):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      APFS Container Scheme -                      +40.1 GB    disk3                                  Physical Store disk2s4    1:                APFS Volume macOS Mojave            25.3 GB    disk3s1    2:                APFS Volume Preboot                 44.4 MB    disk3s2    3:                APFS Volume Recovery                517.0 MB   disk3s3    4:                APFS Volume VM                      8.6 GB     disk3s4  6-251-76-76:~ Me$   diskutil verifyVolume disk1s3 Started file system verification on disk1s3 Recovery Verifying file system Volume was successfully unmounted Live mode required because other APFS Volumes in its Container are mounted Using live mode Performing fsck_apfs -n -l -x /dev/rdisk1s3 Checking the container superblock Checking the EFI jumpstart record Checking the space manager Checking the space manager free queue trees Checking the object map Checking volume Checking the APFS volume superblock The volume Recovery was formatted by diskmanagementd (945.230.6) and last modified by apfs_kext (945.241.4) Checking the object map Checking the snapshot metadata tree Checking the snapshot metadata Checking the extent ref tree Checking the fsroot tree Verifying allocated space Performing deferred repairs The volume /dev/rdisk1s3 appears to be OK File system check exit code is 0 Restoring the original state found as mounted Finished file system verification on disk1s3 Recovery 

taken from: How to boot into recovery mode without cmd-r?

6-251-76-76:~ Me$   diskutil list /dev/disk0 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *500.3 GB   disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:                 Apple_APFS Container disk1         500.1 GB   disk0s2  /dev/disk1 (synthesized):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      APFS Container Scheme -                      +500.1 GB   disk1                                  Physical Store disk0s2    1:                APFS Volume Cupid                   362.6 GB   disk1s1    2:                APFS Volume Preboot                 45.9 MB    disk1s2    3:                APFS Volume Recovery                517.0 MB   disk1s3    4:                APFS Volume VM                      2.1 GB     disk1s4  6-251-76-76:~ Me$   diskutil cs list No CoreStorage logical volume groups found  6-251-76-76:~ Me$   sudo gpt -r show /dev/disk0       start       size  index  contents           0          1         PMBR           1          1         Pri GPT header           2         32         Pri GPT table          34          6                   40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B      409640  976695384      2  GPT part - 7C3457EF-0000-11AA-AA11-00306543ECAC   977105024          3            977105027         32         Sec GPT table   977105059          1         Sec GPT header 

My MacBook Air (13-inch, 2017) does not go to sleep after Mojave update [10.14.3]

Ever since upgrading to the latest version of Mojave[10.14.3], my MacBook Air (MBA) (13-inch, 2017) refuses to sleep with the lid down in the default settings on battery power. This leads to severe battery drainage along with the MBA getting really hot in the backpack while carrying. Numerous tries with clearing the SMC, resetting to the default battery setting, are not helping.

I have tried to look into the reason why this is occurring.

Entering pmset -g assertions yields

2019-03-18 22:12:04 +0530 Assertion status system-wide: BackgroundTask 0 ApplePushServiceTask 0 UserIsActive 1 PreventUserIdleDisplaySleep 0 PreventSystemSleep 0 ExternalMedia 1 PreventUserIdleSystemSleep 0 NetworkClientActive 0 Listed by owning process: pid 61(powerd): [0x0000000d00088000] 52:39:18 ExternalMedia named: "com.apple.powermanagement.externalmediamounted" pid 103(hidd): [0x0000dc9200099fd0] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4295019668.3" Timeout will fire in 120 secs Action=TimeoutActionRelease No kernel assertions. Idle sleep preventers: IODisplayWrangler

While the log shows the following

log show --style syslog | grep "Wake reason"

2019-03-11 01:17:46.678832+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:17:46.678835+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:17:59.740650+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:17:59.740653+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:13.368112+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:13.368115+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:27.621691+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:27.621694+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:40.662311+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:40.662313+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:53.706124+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:18:53.706127+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:19:07.346584+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:19:07.346587+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:19:21.040185+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance) 2019-03-11 01:19:21.040187+0530 localhost kernel[0]: (AppleACPIPlatform) AppleACPIPlatformPower Wake reason: EC.DarkPME (Maintenance)

What is this

EC.DarkPME (Maintenance)

How to fix this?

Extand main APFS partition on MacOS Mojave 10.14.3

As it can be seen from the screenshot below my APPLE SSD is of size 500GBs, but my Apple_APFS Container disk1 is of size 450GBs. There was a Container disk 2 of size 50GBs before but I successfully removed it using:

sudo diskutil eraseVolume "Free Space" %noformat% /dev/disk0s4 

I tried resizing the main APFS cotnainer with the following command:

diskutil apfs resizeContainer disk0s2 0 

but I am getting the following error:

Error: -69519: The target disk is too small for this operation, or a gap is required in your partition map which is missing or too small, which is often caused by an attempt to grow a partition beyond the beginning of another partition or beyond the end of partition map usable space

Following some screenshots displaying the current state of the sysetm:

 diskutil list /dev/disk0 (internal, physical):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      GUID_partition_scheme                        *500.3 GB   disk0    1:                        EFI EFI                     209.7 MB   disk0s1    2:                 Apple_APFS Container disk1         449.3 GB   disk0s2    3:       Apple_KernelCoreDump                         655.4 MB   disk0s3  /dev/disk1 (synthesized):    #:                       TYPE NAME                    SIZE       IDENTIFIER    0:      APFS Container Scheme -                      +449.3 GB   disk1                                  Physical Store disk0s2    1:                APFS Volume Macintosh HD            362.2 GB   disk1s1    2:                APFS Volume Preboot                 55.2 MB    disk1s2    3:                APFS Volume Recovery                517.2 MB   disk1s3    4:                APFS Volume VM                      1.1 GB     disk1s4 

enter image description here

enter image description here

enter image description here

Linking with LAPACK library under OS 10.14.3 and Xcode 9.0 [on hold]

I’m trying to compile a simple Fortran code (with gfortran 8.2.2) in which I access some LAPACK routines on OS 10.14.3. Unfortunately, I can no longer link with the Accelerate framework (which used to work fine for a long time). For example,

gfortran -framework Accelerate abc.o def.o -o mycode 

now leads to

ld: framework not found Accelerate 

I’m using Xcode 9.0 and I installed the developer tools.

It’s been a while since I’ve compiled that code and I’ve updated the OS, Xcode, and gfortran since then so I cannot trace the problems to a single change. Any ideas?

iMac Late 2013 with MacOS 10.14.3 not recognizing my printer, any help and or ideas?

First of all I am not sure this is the right place/space to ask for help about this, if not please let me know and I suggest me any other place to move this into.

As title says I am unable to add my printer (Canon MG7720) to my MacOs and I can’t find anything helpful over Internet. Currently the printer is connected through the USB cable (directly into the iMac, I’d it connected to a USB Hub and I was blaming it but it was not the case). Before have the printer connected to the USB I was having issues also with the AirPrint feature since I was able to add the printer and use it one time only from there it never worked again 🙁 does any have an idea in what could be wrong or what I am missing here?

Cisco AnyConnect errors on MacOS Mojave 10.14.3

My Cisco AnyConnect started giving this message few days ago and I am unable to connect to VPN

Posture Assessment Failed: Unable to download CSD library. Please try again

11:19:09 AM    Contacting xxxxxxx. 11:19:10 AM    Posture Assessment: Required for access 11:19:10 AM    Posture Assessment: Checking for updates... 11:19:10 AM    Posture Assessment: Updating... 11:19:10 AM    Posture Assessment: Failed 11:19:10 AM    Connection attempt has failed 

Problems with Samsung Galaxy Tab 2 and macOS Mojave 10.14.3

I have a Samsung Galaxy Tab 2 with android 4.1.2, when I plug the usb cable to usb port in minimac, macOS don’t detect my tablet. With Android File Transfer I can see the disk and the mini card in the tablet, but I want use Calibre to management my library with Aldiko, but I understand that it’s necessary “view” the tablet in finder to Aldiko can transfer the epub files of minimac to tablet.

Any tips on using / troubleshooting caliber on macOS with Android devices?