

- #WHAT IS DISK UTILITY FIRST AID MAC HOW TO#
- #WHAT IS DISK UTILITY FIRST AID MAC SOFTWARE#
- #WHAT IS DISK UTILITY FIRST AID MAC PLUS#
- #WHAT IS DISK UTILITY FIRST AID MAC MAC#
#WHAT IS DISK UTILITY FIRST AID MAC PLUS#
This tool verifies and repairs a limited number of directory structure problems on any HFS or HFS Plus hard disk or volume.
#WHAT IS DISK UTILITY FIRST AID MAC MAC#
that was bundled with all computers running the classic Mac OS.
#WHAT IS DISK UTILITY FIRST AID MAC SOFTWARE#
READ CAREFULLY before you post next time.Disk First Aid is a free software utility made by Apple Inc. So all you wrote here, including the cause of problem, the accuse of culprit, and the possible solution, are noting but misdirections based on wrong interpretation of the text.
#WHAT IS DISK UTILITY FIRST AID MAC HOW TO#
He just don't know how to do it because he heard some misleading informations from people like you. His system does not work properly but the system core and the rest of hard drive stays intact, and it's totally eligible to recovery from Recover Mode or external bootable disc. In other words: OP deleted his user home, applications, and other runtime generated data from OS and app. This is a special security scheme since Catalina that the system volume is mounted as READ-ONLY, and Finder and other apps will only see these two as one single merged volume " Macintosh HD" because Apple invented a new type of file system link node, a.k.a the firmlink, to maintain backward compatibility. In case you're living under some rock since System 7: " Macintosh HD - Data" is a APFS volume of user data inside the same APFS container, that holds the system volume, " Macintosh HD". The OP only deleted the " Macintosh HD - DATA", not the "Macintosh HD". Nothing you posted here will help solve his problem. The original post talked about deleting the HD volume. You need a total hardware structure overhaul. And this will not be " solved" in macOS 12 or 13 or whatever future release, not even with Steve Jobs being resurrected from grave. Unlike Intel Macs, M1 Macs does not store its recoveryOS inside firmware on logicboard, but hidden partitions on the internal hard drive. It's a firmware/hardware issue rather than OS. READ CAREFULLY before you post next time.īasically your fundamental assumption " it's all Big Sur's fault" is completely wrong, too. You can not recover from external booting disc only if your internal hard drive is totally garbaged, including the recovery partition and the other fullback recovery partition, and this is NOT the case that the OP had.Īnd in fact, OP had mentioned that he managed to find a rescue SSD and successfully solved his issue later in this thread. Read the links in my post again, CAREFULLY.

I wrote you cannot RECOVER from a bootable drive. It never took that long even on a 2012 Intel Mac, the first generation Mac that started to support Recovery Mode. Wait patiently - 15-20 minutes - until the Recovery main menu appears If you feel lazy to read the text, here is the YouTube version:
/FirstAidInfo-57227ceb5f9b58857de3c052-dbd3c5e12a694f17b0564c8fe4ec4537.jpg)
It's not how Recover Mode works on M1 Macs. Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen.

On Intel Macs this "hardware security enclave" is implemented in separated T2 chip, and on M1 Macs it's built-in inside M1.Īnd yes, FileVault on T2/M1 Macs is only a secondary security checkpoint, that your system will not decrypt data on disk automatically, until you enter the password. Unfortunately, all data written on internal disk of any 2018 or newer Macs are encrypted by default, and the decryption key is buried in hardware security enclave. If you had data on the thing, then only expensive data recovery software or companies will help get some back.Unless it was encrypted. Jef Raskin, the Macintosh project initiator, was then forced to leave Apple, after Steve Jobs took over his project. The last time he involved into Mac development was back in 1980, when he tried to grab team leader role from Jef Raskin after Steve Jobs' own project "Lisa" failed. Steve Jobs had never participate in macOS development. Unlike in Steve Jobs' Mojave and previous. In that case, you should use Apple's new administrative tool to rescue it. Here is a long & technical blob post that explains details: You won't be able to boot a M1 Mac from either internal or external only if it's built-in SSD is totally corrupted, including the recoveryOS and an additional fallback recoveryOS partition, because system won't be able to verify the booting device and an unverified device could cause severe security breach. Unfortunately, Tim Cook's Apple has made Big Sur so that you CAN'T boot and recover from an external driveĪctually, you can boot from an external drive on M1 Macs.Īnd here is Apple's official document about how to make a bootable installer disc and how to use them on M1 Macs: All your informations are either inaccurate or outdated.
