Very possible. Yet Steve Gibson, who thought the usefulness of his Spinright software was less with SSDs says he gets many stories where his Spinrite fixes problems with SSDs. It works at the block level. SSDs are pushing density very high, just as this has become the case with spinning disks, which has increased the chances of some sort of failure. But SSDs might still be overall more reliable.
DiskWarrior does retain a useful function for me. Of course I can no longer use it to repair the internal drives of the Macs I service ā these drives are all SSDs with APFS. They have to be, because MacOS has required APFS to enable OS updates since Mojave, and APFS has been kill-me-now slow on a spinner since it appeared.
However spinning drives are still cheaper than SSDs, and backups donāt need to be fast. All these main-drive internal SSDs are backed up to conventional external hard drives, and I scan and repair the externals with DiskWarrior.
If Apple never finished APFS enough to release the full specs and make DW run everywhere again, I would be sorely disappointed in Apple. But not as much as I was when they killed HyperCard with neglect. That was when ( to borrow a phrase of Lalla the poet ) I started waiting for my love of the Mac to leave me.
I consider it completely unacceptable that Apple hasnāt made Time Machine compatible with APFS. Whoever heard of making a partial adoption of a new file system?
Reportedly, Big Sur supports APFS for Time Machine volumes, but using very different internal mechanisms.
Here are some links about APFS support for the Time Machine in Big Sur:
Not sure what you mean. Yes, APFS is a PIA, and Time Machine has long been buggy (though itās come in handy a few times), TM has backed up as before with Mojave and now Catalina.
As for APFS, itās unconscionable of Apple that even if APFS is a work in progress they havenāt released documentation about what they know so far, and canāt understand why they donāt.
This is a tad off topic. But the SIS plays havoc with trying to save photoshop files on the startup volume or the volume that houses the ps app. Unless you disable SIS and make the owner able to read/write on that volume-PS will not save any file as the owner or creator of file who does not have permission. So I disabled SIS -made myself (administrator also) the owner of the volume and then restarted and began saving all my ps files again (only sometimes for speed working) to my start up drive. I have not reenabled SIS yet so I donāt know if the permissions stuck with me and the administrator users. After talking to Adobe for about 45 min- I figured this out as they could not.
Apple has released detailed APFS specs. Itās almost 200 pages, Iāve only read some of it.
But Iām not sure if it goes into enough detail for Alsoft to write a reliable repair tool. The part Iāve read so far has lots of very low level detail, without a broad overview of how it all fits together. But perhaps I just havenāt got to that part yet.
HFS and HFS+ were in use for decades, had detailed specs, and Apple engineers would answer questions at WWDC or online. APFS seems much more secretive, and Apple is a more secretive company now.
Thanks for the link. That document is dated June 22 - less than two months ago.
Hopefully it will be enough information for Alsoft to fill in all the gaps in their knowledge. Now the question is how long it will take to complete APFS capability in Disk Warrior.
Itās my understanding that Alsoft has been working on APFS support based on what information theyāve been able to get, so they probably have a partly-finished implementation in-house that they can finish up now that they have this information.
If weāre lucky, then Alsoft guessed correctly about most of the missing information - this would let them quickly finish up the code and move on to testing. If weāre not lucky, then their guesses were wrong in ways that will require significant changes to whatās been developed so far, meaning a release will take longer.
Yippee! The Cavalry is on the horizon ā¦ weāll all be saved!
āThe Lord willinā and the creeks donāt rise!ā
Wow, talk about a blast from the past. I used to use Disc Warrior religiously years ago (in the PowerBook era), but I know I havenāt used it at all with my Intel-based Macs. And with Classic MacOS, it was essential to have it and also Norton Disc Doctor. Iām not at all sure why disc corruption/file fixing was more of an issue back then (and why you had to run such utilities on a regular basis), but maybe with the various versions of the OS in the last twenty years, it does a better job taking care of those housekeeping chores. Now Iām much more obsessed with having complete data backups, whether they are bootable or not, I donāt want to lose anything at all. So thatās my main weekly and bi-weekly chore.
Remember the old white ambulance icon with the red cross on it that Disk First Aid used to have?!!
Iāve found that Disk Warrior can save Time Machine backups on HFS+ external (spinning disk) drives that Disk Utility refuses to touch. It take several hours, but worth it to save the version archive. Otherwise, itās wipe, start over, then eventually the TM drive will corrupt at some future point anyway.
Hi all, I was very pleased to come across this discussion, sadly, though, no relief for that slight feeling of despair - Diskwarriorās APFS incompatibility seems like a very sad loss - that almost magical app that seemed to do just one thing when rebuilding the startup disk directory really really well.
So, how to āclean upā the startup disk directory now?
I did see a hypothesis that - using, say CCC to clone off then back to the internal HD would defragment the drive and at the same time rearrange the directory. Wonder if thatās right?
Even if so, plainly thatās cumbersome - and its not a quick get out of jail emergency ānot booting situationā 30 minute fix that DW was.
So, is our fallback for this awful failure to boot situations now perhaps:-
1: A time machine backup - then clean install OSX and migrate?
[with the side advantage that a clean install used to be considered good Mac health practice, maybe annually or bi annually in days of yore.]
2: maybe a better solution - daily CCC incremental bootable backup and in an emergency you can A: boot and get some work done
then
B: clone back
- possibly faster than option 1 too.
I wonder how well CCC deals with weekly external disc swops when making incrementally updated bootable backups - so that a pretty recent working OS installation is always available off-site?
I do that with folders etc. using Chronosync, but donāt use CS to make bootable backups. CCC seems more the respected candidate for that.
Ideas welcome
many thanks
Neil B
I OTOH canāt say how many times a CCC backup has saved my bacon - I had a 2014 then a 2017 iMac 5K with 3 TB fusion drives, and somewhere through the years 3 TB fusion drives with boot camp installed could not migrate through the OSes without breaking - and broke repeatedly even after being clean reformatted and restored through Migration Assistant.
Itās only when I moved on to a 2020 iMac with a 4 TB SSD that I found a really stable boot camp environment again.
APFS is more of a work-in-progress than it is a stable file system, and Apple doesnāt have the perseverance of say IBM when it comes to strictly defining the file system, data structures, and program logic.
I agree. I was a Mac consultant for many years, and DW was one of my go-to utilities. It wasnāt the optimization that was most important, it was rebuilding broken directories. DU only repairs them, DW would rebuild them, and did a better job sometimes.
Me too. FMPro became a (poor) substitute.
After 37+ years of working with Macs, my career definitely reached a plateau, and then took off, once I automatically ran DW on every newly backed up drive or/or major system update I ran into! After one of those sessions, DW would reliably āstraighten upā and repair, not only the main directory, but, like a local neighborhood street repair ā realign all the āhousesā (applications, files, folders, caches, Trash, etc.) on the street/drive! The time and debugging frustrations ā especially prior to knowledge of a soon to be announced major op sys update from Apple ā was painfully wasted time for all concerned. Regretfully, it seems that we are ārevisitingā that time of old ā¦ without even the benefit of Applejack or even good old AppleWorks.
Me too. FMPro became a (poor) substitute.
The the last few versions of FileMaker Pro have been amazing. Iāve used it to design database solutions for large logistics corporation.