Mojave question

[spadz93]

Ever since Mojave came out, both my Macbook pro and Mac pro simply cannot make it through an OS update (10.14.2, 10.14.3, etc). They will go through the hoops and then get stuck on the Apple boot screen for hours, and will ultimately never boot up again. I have to fully wipe my mac and recover my files each time an OS update comes out. Has anyone else had this issue? It's beyond time consuming.

[caincha]

Could it be an issue with file system (HFS/APFS)?

Try to do a clean install and then recover from Time Machine on setup screen instead of recovering the whole system from backup. 

[spadz93]

On 6/22/2019 at 2:42 AM, caincha said:

Could it be an issue with file system (HFS/APFS)?

Try to do a clean install and then recover from Time Machine on setup screen instead of recovering the whole system from backup. 

I always do fresh installs, but use the migration wizard that MacOS has to migrate my files back, I just use the backup I make of my boot drive as the source

[caincha]

I usually restore my backup on the setup screen after a fresh install - it's much faster than finishing the install and then using the migration tool inside the system…

Regardless: I had issues with file system incompatibility HFS/APFS before. If you're not running a M.2 (or 'blade') SSD and instead are using a regular 2,5" SSD I would recommend to reformat in HFS and go from there to see what happens.

 

But if you are running a M.2 setup on a separate card inside your Mac Pro I can't help you… A friend is having the same issues on several setups (he services Mac Pros around here) and we just can't figure it out…

[DrMacintosh]

If you have access to another Mac, I would make a bootable USB installer, boot from it and use DiskUtility to run First Aid on your drive and also completely wipe the drive. Including the recovery partition which could be damaged and be what is leading to all of these problems. 

 

Once the drive is clean, install macOS and migrate your data back. 

[spadz93]

On 6/26/2019 at 7:46 PM, caincha said:

I usually restore my backup on the setup screen after a fresh install - it's much faster than finishing the install and then using the migration tool inside the system…

Regardless: I had issues with file system incompatibility HFS/APFS before. If you're not running a M.2 (or 'blade') SSD and instead are using a regular 2,5" SSD I would recommend to reformat in HFS and go from there to see what happens.

 

But if you are running a M.2 setup on a separate card inside your Mac Pro I can't help you… A friend is having the same issues on several setups (he services Mac Pros around here) and we just can't figure it out…

I should have clarified better, this is what I do, i use the wizard during the initial setup. I typically use HFS as well, but it may be converting it over to APFS. I can double check this.

9 hours ago, DrMacintosh said:

If you have access to another Mac, I would make a bootable USB installer, boot from it and use DiskUtility to run First Aid on your drive and also completely wipe the drive. Including the recovery partition which could be damaged and be what is leading to all of these problems. 

 

Once the drive is clean, install macOS and migrate your data back. 

I can try cleaning the drive outright, I usually just format the Mac OS install volume and go from there

[SilverSoul]

On 7/2/2019 at 4:24 PM, spadz93 said:

I should have clarified better, this is what I do, i use the wizard during the initial setup. I typically use HFS as well, but it may be converting it over to APFS. I can double check this.

I can try cleaning the drive outright, I usually just format the Mac OS install volume and go from there

It's likely converting your filesystem to APFS every time you install it.

 

The real question is why would you use HFS+ when it's one of the worst filesystems on the planet? Unless you're running something with a heavy write workload (like mongoDB, which you should run on a server) then you should be on APFS. I'd argue it's even worth running it on a hard drive because of how bad HFS+ is.