Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

SSD Unrepairable in Mojave

That corruption with APFS is scary. I just made my second backup on an 8TB external with all my files. Could it possibly be due to how much you allowed and actually used in the volumes? My volumes are all in one APFS container, and I set the parameters so that the maximums do not go beyond the limit of the actual space. My only guess is that there was a problem with volumes trying to consume more drive that you had. That might account for all the drives showing corruption. Just a guess as none of us know very much about APFS, as Apple looks like it isn't sharing the limits of its new file system. but I also have old HDDs which are full of SuperDuper clones that I access through a dual disk dock that accept either 2.5 or 3.5" SATA drives. I've had this system for years so it is HFS+. I know I have run into several problems with Super Duper, but all the problems have been solved without loss. Perhaps there are problems with CCC? I doubt it, but make sure you have the latest version as my SD version has changed several times in the last 6 months or so.
 

Attachments

  • Screen Shot 2019-05-07 at 7.16.30 AM.png
    Screen Shot 2019-05-07 at 7.16.30 AM.png
    51.4 KB · Views: 192
Unlike SuperDuper, CCC 4-5 doesn't use Block level copying. Thus, filesystem operations are performed by macOS. CCC 4-5 uses file level cloning only. You have use macOS to initialize your storage to the format of your choice. You won't see "filesystem corruptions" caused by CCC. There may be other issues, but not that particular one.
 
Is it not safe to clone an APFS SSD volume to a HFS+ Hard disk with CCC5 for backup reasons only? (Mojave)
 
"Is it not safe to clone an APFS SSD volume to a HFS+ Hard disk with CCC5 for backup reasons only?"

You can do that if you wish.

In fact, for my 2018 Mini (which came with APFS), I created an HFS+ clone of the internal drive on a backup drive -- and then "re-cloned" it back to my internal drive, so that the internal drive is now HFS+ as well.

No APFS in this house!
 
  • Like
Reactions: pippox0
With Super Super, you can clone to what ever file system you'd like regardless what the file system is on the original. The only thing you can't do is make a clone for one OS when you're working in another. So, if I'm in HS, I can't attach a Mojave boot disk and make a clone of the Mojave disk to another external or a removable internal. I tried and called the ShirtPocket guys when it didn't work. They explained that the different OS can not do the tasks that it's meant to as that instruction set is not in the older OS. I have my NVMe drives as APFS, both boot 960 and cache 970. But with the RAID0 on the Sonnet card SoftRaid doesn't work with APFS disks, and I don't believe you can create a raid with APFS anyway, It doesn't seen to matter which file system you use.
But, all that may end this fall with 1015. This is supposed to be the macOS that will be compatible with iOS which already uses APFS, so you can use the same apps with both. I also find it likely that even my souped up 12-core cMP won't get past Mojave, nor my 1012 MBP. My 4-core is already held at 14.3 as the bootROM flash before 14.4 has been bricking all the single processor cMPs. I've escaped twice with the MP. I may be looking at that Mojave sand dune for a long time... Things are going to be different as I heard that all the 2019 units and beyond will have a built-in OS and will not have backward OS compatibility. We may even see some changes in the last point update for Mojave. Just look what happened to Nvidia video cards. "CUDA FOREVAH"
 
naerct said:
My 4-core is already held at 14.3 as the bootROM flash before 14.4 has been bricking all the single processor cMPs.
Click to expand...

Please don’t spread misinformation. If You are referring to BootROM v142.0.0.0.0 which was never released to public. It was only in a Developer Preview (2x) and I am the person who discovered this, and worked with ADR to have it pulled. It’s also easy to recover from this. If you are not a Developer you don’t have access to this unless it’s unauthorized, in which case you shouldn’t be taking these chances. That’s why they are in Developer Previews. So we can find problems.

Others who were warned not to install this BootROM ignored the warnings and got bricked. BootROM 141.0.0.0.0 is not affected by that issue.

My single core cMP is currently on v144.0.0.0.0, it’s not available to the public (yet) but there are no reported issues, and MANY fixes. You are not confined to 14.3, only your choice confines you, not macOS and not the BootROM.
 
Last edited:
Today, I checked the startup disk with Disk Utility (Mojave). Disk utility locked up for more than 15 minutes. I choosed to force quit, then the message appeared: Volume OK.
I booted in the recovery mode. But I was unable to repair the Samsung SSD because it couldn't be unmounted.
My recovery part of the Samsung SSD is useless. (it could never repair the APFS volume)
Then I booted from a different SSD under High Sierra and tried to repair the disk with Mojave.
Again the warnings appeared:more than 10
Warning: inode_val: object (oid 0x....): invalid internal_flags (0x28000)
At the end was displayed the volume disk5 appears to be OK.
Should I reformat my SSD?
 
Last edited:
MacHammer wrote:
"Should I reformat my SSD?"

I'd take it to the High Sierra Mac, and try to reformat as HFS+.
Does that work?
 
It is very strange, but when I booted under Mojave on APFS five minutes ago and ran DU again, the warnings were gone.
DU reports now: The disk5 appeares to be OK.
Of course, I have never had these problems under HFS+. They are APFS related.
I have two SSDs in this MacPro, one Mojave APFS and one High Sierra HFS+
I will re-read your advice to run Mojave on HFS+ if the problems come up again.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back