Only if you havn't a SSD yet. Also if e.g. you have a Fusion drive.
On a SSD Mojave runs better with APFS.
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
What have you done with an obsolete OSX Mojave Today?
- Thread starter MBAir2010
- Start date
- Sort by reaction score
On a SSD Mojave runs better with APFS.
Updated - apps, cloud files etc - and backed it up with CCC to an RAID1 DAS. Better safe than sorry. 
Define "better". (It's certainly not faster with APFS, and, whatever its other ostensible dubious merits, APFS increases the complexity of easily creating bootable backups immensely, not to mention an utter dearth of recovery utilities should anything ever snarl up your data partition.)
Last edited:
Better= better handling of SSD Read/Writes, longer life of the SSD medium.
Normally on a SSD once, it dies, everything is lost. Don't expect to read sectors like on an rotating drive.
Recovery utilities will already fail by accessing the controller, that is my experience.
The separate data partition you speak of came only later, with Catalina
Propaganda at odds with reality.
<sigh> <ignite blade>
I made no reference to dead drives.
Which is why Mojave can be cloned back into HFS+, but Catalina cannot. (Catalina sucking the high, hard one being a common theme of these 32bit & HFS+ threads.)
Crucial contextual word bolded, underlined, and italicized so that the avatarless respondent might understand the reality of the "assertion". (There were at least three or four utilities one could use to create bootable external clones of one's operating system in HFS, whereas there's only one that half-ass works with APFS.)
R i d i c u l o u s !
CCC never has any problem making bootable clones neither with HFS+, nor with APFS on Mojave.
In fact: it is not even aware of the file system below.
The problem you are addressing comes with newer mocOS versions and their system partitions, not with APFS.
And there it had to struggle with Apple's restrictions.
And ‒ by the way – the system boots on an EFI that is not APFS, but plain FAT16.
Last edited:
Now name a second utility that can make a bootable backup of an APFS OS from Catalina onward.
(See the "single source dependency" problem for an overview of the issue that I am highlighting here.)
No blip. What do you think I'vebeen grousing about in these threads?
~ ~ ~ ~ ~
No *business* that cares about, say, the redundant security of being to deploy particular configuration to its machines via "sneakernet" (i.e., manual cloning from external "master" physical backups) in the event anything ever happens to its network, will ever use the newer Apple machines sans a good deal of trepidation, and not at all if it refrains from having a network for whatever reason.
In short, Apple is abandoning its prior end-users in deference to its new "customers": the shadowy intelligence patrons that control "evil big tech" now, which are pursuing their own agendas of escalating dependency: They want you on their "cloud" 24/7, and for you to have little to no control over "your" computer. <insert meme of Neo waking up in The Matrix, and all the rows of pods have Apple logos>
dd (that was easy
)Again, APFS is not the culprit. but Apple's decision to lock pretty much everything.
I don't appeal that.
Last edited:
Insofar as I am aware, DDrescue (a linux utility) it does not have the ability to create a viable bootable clone partition of a partition. Blitzing the entire target drive is the only option. DDr is also useless if the machines to be serviced are running an OS that forbears USB-booting -- because there's no way to launch the utility.dd (that was easy
APFS thrashes rotational drives, and Apple cheerfully insists that everyone with a thinside intel iMac or MacMini (85% of 2012-2020 machines) "upgrade" to Catalina or other APFS OS.
There are multiple legs on Apple's new stool-of-suck. (Spotlight telemetry is another stool-leg.)
You just have got no clue.
The macOS command dd if=/dev/rdisk0 of=/dev/rdisk1 bs=1m will backup anything from disk0 to disk1.
It makes a 1.1 copy of the full drive.
That's true ! Don't use APFS on spinners.
Apple can stomp with it's foot that Cupertino gets an earthquake, I won't, but I happily use APFS.
Last edited:
(When I moderate forums elsewhere, one of the highlights of my day is summarily dispatching generic avatarless alphanumeric-handled users at the first hint of overweening smug. Kid, if you're gonna gamma-crow, at least get yourself a fedora.)
Because "a 1.1 copy of the full drive" perfectly satisfies a requirement for "a viable bootable clone partition of a partition" exactly how?
I even italicized the pertinent word *twice*, and you <blanked-out> right over it.
If you prefer to clone only a partition, dd is your friend too:
dd if=/dev/disk0s1 of=/dev/disk1s2 bs=1m
Will raw copy partition 1 of disk 0 to partition 2 of disk1.
It's just somewhat slower, since it copies logically.
Here you are...
If it's so "easy", go slap a GUI shell around it, and steal Bombich's lunch-money.
...and the fellows Linuxians and Windowsians look at your obsolescence problems with big compassion.
They mostly don't even know how to spell "incompatible".
SuperDuper. Been using it for years and it can do bootable APFS backups from different-size SSDs (been cloning my 2TB NVMe SSD's startup volume to a 128gb external SSD). It's also possible to bypass superduper completely for restoring too. (via the migration assistant - just point it to the superduper disk)
Apple provides asr, which is the backbone of bootable APFS backups.
I am wondering what is the XProtect version people have on their Mojave installations?
My Late 2008 13 inch unibody seems to stuck on 2188, while the latest should be 2190.
My Late 2008 13 inch unibody seems to stuck on 2188, while the latest should be 2190.
The best way to remove 99.99% of malware risk from any Mac system is to perform these two steps:
* Right(or control)-click Safari, News, and Mail, and remove all of them from the dock. (Find third-party browsers and mail-clients as replacements. Stop rewarding Apple's deliberately withholding of so-called "security" by buying newer machines.)
* Install the uBlock and Adblocker Ultimate browser extensions.
And do not ever pay money for antimalware utilities (and especially not for Macs).
~ ~ ~ ~ ~
(Disabling dead-weight MRT is also an option to explore.)
True, true, true, true to all of the above however when something suddenly stops updating itself you can't help but start to wonder what could have possibly caused it.
Perhaps even more deliberate Mojave obsolescence?
Although I don't use Auto Update on any of my devices, I do feel for the users - not just being sheep in this regard - that find comfort in it. I just want to be in control as much as possible with all my gear. Whatever ecosystem it's part of.