Just a quick note, as this seems not to be mentioned anywhere so far:
Apple recently released Public Beta 4 of macOS High Sierra (Build 17A315i) – which broke my APFS formatted external SSD drive; kind of.
Solved (again)
Read more Solution approach: fixing APFS disk issue “fsroot tree invalid” in macOS High Sierra Public Beta 4 (17A315i)
Read more Solution approach: fixing APFS disk issue “fsroot tree invalid” in macOS High Sierra Public Beta 4 (17A315i)
The error appearing reads:
error: alloced_size of dstream does not match calculated size error: xf : INO_EXT_TYPE_DSTREAM : invalid dstream error: inode_val: object: invalid xfields fsroot tree invalid
Problem shows itself with the following symptoms:
- No startup chime since the OS update
- When I manually
"Shutdown..."
the Mac from within the OS/Finder, it immediately crashes - After pressing the startup button, the screen stays gray for about 2-3 minutes (no logo or progress bar visible)
- Sometimes Mac restarts automatically while in Finder
Disk Utility.app
– in macOS and in Recovery Mode – can’t repair (aka First Aid) the volume; fsroot tree is brokenPhotos.app
is broken; Permission repair fails (launching Photos withOption+CMD
keys pressed)
I reported this critical issue to Apple via bugreport.apple.com as Bug #33924532
…and I hope I’m the only one affected by this issue ✌️
I have the EXACT same problem. How to fix it???
I haven’t had the time to fix it yet on my Mac; but I think my approach will most likely be to reformat the drive from the Recovery volume (startup holding
CMD+R
) and reinstall macOS High Sierra Public Beta 4 to it from scratch.Maybe it would even be better to boot into the Web Recovery Mode (startup holding
CMD+Option+Shift+R
), as this should ensure having the most recent macOS High Sierra Beta version files.As mentioned in my last comment, I was able to resolve the
fsroot tree invalid
error by completely reformatting the APFS volume (with some little struggles) – as described here in my followup post.Cheers
Apple just acknowledged the above behavior in High Sierra Public Beta 4 as a Bug: