17 ms·
Don’t format a drive of M1 Macs from recovery mode
- tumblewit 6y agoI recently encountered something similar on my M1 air when i tried to erase it (if you got a new m1 air don't do it it's not really necessary). So turns out, with I believe Catalina, APFS has a system partition and a data partition on an m1 mac. one is read only with SIP on. I don't know how exactly APFS stores snapshots but the read only is for snapshots + macos updates sort of like iOS. If you erase the mac (btw there is an erase mac option like in iOS in recovery if you don't know decryption key so manually doing it is unnecessary) then your mac will basically clean your drive and reinstall macOS to the latest version. Now once you do that the read only partition is basically a dynamic container and remaining software is in the partition called untitled. This is similar but here the partition scheme messes up a little. You can delete local snapshots if you use time machine to free up space but the system snapshots (not the back up ones this is something different to protect system integrity) stay. If you really want to erase an M1 mac do it using the configurator which btw people have claimed has bugs so maybe wait. But otherwise this is going to be like iOS so you can just keep using your mac with delta updates because your system partition is going to be read only with snapshots for any failed updates called macos - System while all your data will be in macos - data. This 'erasing / formatting' a computer is reminiscent of Windows experience. It's just easier to clean everything and start again. But ideally it shouldn't be needed for Apple silicon macs (once macos bugs are sorted ofcourse).
- simonh 6y agoThe one area with these M1 Macs that seems barely even half cooked is how they treat their disks. Does anyone know if this due to hardware limitations in the M1 architecture, or are the restrictions in the firmware level? I'm wondering if this is even fixable by Apple in later updates.
- giuliomagnifico 6y agoI suspect is due to a security choice from Apple, a firmware upgrade should fix it, or at least put a warning or doesn’t allow you to erase the whole SSD if you can’t install macOS after.
- GeekyBear 6y agoThe free Apple Configurator 2 utility will factory reset an M1 Mac, even if the firmware is completely hosed. It's also much quicker than Windows 10's "Reset this PC" functionality, which doesn't work at all if the OS or firmware is hosed.
- jonwest 6y agoSame, or similar behaviors with the 2020 Intel MBP. I ended up having to format the drive as an exFAT drive and then reformat again as APFS to get it to reinstall it was a real pain in the ass.
- giuliomagnifico 6y agoBut at least with an intel Mac you can boot in target mode using cmd - t and then clone/mount/erase/whatever the disk from another Mac! Instead with ARM you can’t mount the disk as an external drive. That’s why this mess started!
- galad87 6y agoA M1 Mac can be restored from Apple Configurator, the same as any other iPhone or iPad.
- giuliomagnifico 6y agoYes but to me looks a bit overkill use another Mac to restore a Mac with a restore partition. It was my last way, fortunately I solved without use it.
- devit 6y agoWhy not just do the usual dd if=/dev/zero of=<disk> bs=1M count=1024 instead of using those weird proprietary tools?
- sillysaurusx 6y agoYou'd likely brick your mac if you don't do it the anointed way.
- my123 6y agoAs long as you don't shoot yourself in the foot by touching other NVMe namespaces (and even that should be recoverable) and the SPI flash onboard, things can be restorable through DFU.
- wtallis 6y agoWhile it would make a lot of sense for Apple to use NVMe namespaces in this manner, it appears from information posted elsewhere in this thread by marcan_42 that Apple is not doing so, and is just using regular GPT partitions within a single NVMe namespace to store the stuff that isn't on the motherboard's NOR flash.
- my123 6y agoI can tell you that devices with Apple CPUs _do_ have multiple NVMe namespaces. The recovery OS and 1TR are not data needed to be saved permanently (as in serial number and such, without which you cannot restore the device), you can recover them through DFU. Data critical for being able to restore is in the SPI flash. (and it's assumed that some of it might be in other NVMe namespaces too)
- jabberwcky 6y agoThis option is horrendously inefficient on most modern drives. For many SSDs, issuing a secure erase request is an almost instantaneous process as it only requires the drive to generate a replacement encryption key, and need not even entail bulk writing or erasing physical flash pages
- fouc 6y ago>Uff…what a paintful process! If an issue takes less than 5 different attempts to resolve and under 1-2 hours to fix, that can't really be called painful, merely annoying. Especially when it's only a one-time problem.
- volta83 6y agoIf your bar is "I want to do X, let's start by reading the Arch Wiki", then sure. If your bar is "It just works", then for me at least, if it takes me more than 1 minute I'd describe it as painful. My mother would describe anything that's not immediately obvious as painful.
- kuschku 6y agoThe year of linux on the desktop won't happen because linux becomes more user friendly, but because macOS and windows 10 become less user friendly.
- jhanschoo 6y ago> No way I reinstall and do all the thing Apple suggests with another Mac with Apple Configurator. When the resolution means that you need another Mac at hand it is not merely annoying if you don't.
- kentiko 6y agoYour threshold is probably way higher than the average Macbook user that probably does not even know about the recovery mode.
- rvz 6y agoInteresting. These are all the issues I will avoid from early adopters when I eventually get a newer Apple Silicon based Mac computer. I have no time to go through the thorns and landmines over incompatible systems or buggy system software tools from Apple as described by the blog post. Again, I will wait until the software on Apple Silicon is mature and the developer ecosystem catches up to it which by then I'll be getting an M2 or M3 based Mac.
- distances 6y agoThis seems to be a good strategy with Apple's OS updates too. Most of my colleagues who updated to Big Sur have encountered problems so I'm keeping the strategy of "current minus one", and plan to update to Sur when the next one is out.
- deleted 6y ago[deleted]
- liminalsunset 6y agoBig Sur appears to have introduced several new security features that complicate this process. I attempted a wipe on my 2019 16" Intel MBP to upgrade to Big Sur.... and after this, it required you to do something like sign in with a user to disable startup security, because it would not trust its own official Big Sur installer due to signatures maybe.
- Jonnax 6y agoI think the reasoning is that it's to prevent a stolen laptop from being stolen, wiped and resold without the owner allowing it through their credentials. I remember a poster on HN saying that after some exploit for the T2 security chip came out, they were making money from being paid by thieves to use the exploit to wipe the devices. Of course they said they don't ask any questions which as we all know is an iron clad defence lol
- matwood 6y agoYeah, the high resale value of iPhones and Macs make them prime theft targets. Locking them to a user makes them less desirable to steal. IIRC iPods were similar. Early on, people wearing white headphones were targeted by thieves.
- liminalsunset 6y agoWanted to clarify that this wasn't the Apple ID activation lock screen. This was asking for my regular user password for an account that had been deleted from the system. Activation Lock only runs when the system is doing the first use setup.
- mehrdada 6y agoThe easiest way to reinstall <strike>iOS Big Sur</strike>macOS on M1 Macs is to treat them as what they really are, glorified iOS devices, and DFU restore the operating system from another Mac with Apple Configurator or similar tools (macOS is downloaded as an .ipsw file and deployed on the M1 Mac). Works like a charm and is quite fast and guaranteed (barring bootrom/physical hacks) to ensure the device is not running non-Apple software. P.S. T2 Macs are actually the most difficult to restore to the latest OS sometimes. The installer is anal about asking local password, booting from external USB, etc. and you might end up having to go through internet restore once and then upgrade the OS. M1 is actually an improvement and simplification from clean OS install perspective.
- ajconway 6y agoThis comment is downvoted, but surprisingly it was the correct way to resolve the issue after attempting to "factory reset" an M1 Mac.
- albertopv 6y agoNow imagine this happened on MS Windows...Shit MS, Windows sucks, etc. Reality is all OS have issues, pros and cons.
- wtallis 6y agoWindows and macOS are both very reluctant to tell the user what's actually happening on their disk. They both insist on abstractions that hide the reality of how partitions and filesystems are arranged behind the scenes. Sometimes that's a useful simplification, but sooner or later hiding that information from the user always leads to the OS lying about whether a device or filesystem is truly empty.
- SXX 6y agoI still can't access recovery mode because I had the same issue in attempt to setup proper Full-Disk-Encryption (no, you can't do that on M1 and need to use special encrypt user instead). Recovery know I have OS installed, but because it's not installed the same way it no longer able to find credentials for authentification. And yeah I don't have second Macbook to properly factory reset it. Along the way I stuck into 3 huge bugs and experience was terrible. Fortunatelly Apple support page actually show how to bypass it's bugs with command line magic which is easy for me as Linux nerd.
- SXX 6y agoApple support page that I reffering to: https://support.apple.com/en-us/HT211983 https://support.apple.com/en-us/HT211983 You even have to go through "Erase Mac" twice in process. It's only work if you reboot it properly after each time which is not mentioned on support page. Such a mess.
- whaaaaaaaaa 6y agoWhy would one clone x64 macOS to an ARM Mac? How on earth could it work?
- digi59404 6y agoThis is because the author didn't delete the entire volume group. You have to delete the whole volume group, i.e. erase the entire drive and it's partitions to reinstall OSX. This isn't new with the M1 Macs. This has been a thing since they introduced APFS. When they went into disk utility after the cli - Then they could delete everything and kick off the OSX Install. If the APFS Volume Group still exists the installer will try to unencrypt and work with it. So.. In short, just make sure you delete the volume group. There's a specific button for it. I just did this yesterday on a T2 Mac.
- garmaine 6y agoI bricked my first TouchBar MacBook the day I received it, trying to do a factory reset as my company's security policies demanded. Not sure exactly how I triggered that state. Thankfully Apple took it back as a return. It should not be possible to brick a device by pushing the wrong button. I was shocked that this wasn't caught by anyone at Apple before release.
- hnarn 6y ago> It should not be possible to brick a device by pushing the wrong button So you think all Apple devices should be shipped without root? Or that anything disk-related should only be allowed through CLI as root?
- garmaine 6y agoNo that’s not what I mean. I bricked the device. I’m not saying I wiped the hard disk and just can’t boot. I’m saying I put the machine in a state where it would NEVER AGAIN boot. Completely unrecoverable.
- garmaine 6y agoAdding another comment since the edit window on my sibling reply has elapsed. To be clear, I'm an IT professional who knows how to restore a device from boot media. I once managed a university computer lab, and wrote the linux-based image management software for 2000+ campus computers. I've written my own hobby operating, including the boot an initialization process. I thought any problem encountered reinstalling an OS is something I could handle. But that was not the case. Near as I could tell when I followed up with Apple after the incident, the boot process involved the security chip reading some data off the drive and validating it before handing off control. If that data (which is on the Apple reserved partition) was wiped, the firmware would not boot. And since the security chip was configured to not boot from media (the default state, IIRC), it was effectively bricked. So the very first generation of TouchBar MacBooks would not boot into recovery mode if you wipe the drive, nor would they boot any kind of recovery media. It's a state that required shipping to Apple for refurbishment to fix. It's my understanding that this was fixed in later models, perhaps even as a result of my incident.
- ulzeraj 6y agoApparently the author erased the APFS volume instead of erasing the physical volume.
- SXX 6y agoYou can't wipe actual physical volume on M1 without some command line magic and even then I not sure it's gonna work. Recovery disk utility say it's will wipe it, but it do nothing and Erase Mac option is the same: all it do is erase user data. I got stuck with almost the same issue even though I'm system administrator and programmer with decade of experience. I can't imagine how all this mess should feel for average Mac or Windows user.
- marcan_42 6y agoYou absolutely can wipe the main APFS container on M1, from 1TR mode (the recovery menu that you get by holding down power). That will wipe the OS along with user data. Unless you have something broken in system firmware at that point, it's a clean start. This works from the GUI Disk Utility too, usually, though that tool is flaky sometimes. It definitely works from the command line.
- ulzeraj 6y agoThe thing it doesn't look like we are actually erasing the device but a volume group inside it. I say that because there seems to be a protected partition that contains the OS installer. I could be wrong tho but I've reinstalled at least 2 systems like that.
- marcan_42 6y agoYou are erasing the container (as in one APFS container of multiple volumes) that contains the OS and data and everything else that is what, on a PC, you would consider "the whole drive" for fresh-install purposes. On an M1, that is only one GPT partition, but that doesn't really matter. The point is that that (plus perhaps clearing xART data) will fix pretty much any "normal" issues you have in the machine, equivalent to a fresh reinstall with full data wipe. The filesystem data structures are independent at the volume group level, so this will also fix any filesystem issues you might have (it would be very rare to have FS problems in the other two system APFS volume groups, as they are very rarely written to, and even more rarely have metadata/complex changes). Compare: this is like wiping boot, system, data, and vendor on an Android phone. You wipe the whole OS and user data. You do not wipe the bootloader and other partitions (because if you did, you'd brick the phone). This is as much of a "factory reset" as almost anyone will ever need. If you really want to wipe the whole drive, you need Apple Configurator 2 and another Mac to re-install, as the machine is then unable to boot in anything except DFU mode if you wipe the system containers. Unlike Android phones though, this is supported by Apple, so you can't in fact brick these Macs like that - just be aware that this option does (currently) require another Mac to do the re-install.
- tshanmu 6y agoBecause privacy...
- marban 6y agoIDK but I always just wipe (as in delete all partitions) and do a fresh install on any new MB; and had no issues with the latest Air.
- eric-hu 6y agoWhy do this on a new MacBook? Is there a security concern?
- marban 6y agoYeah, peace of mind and Internet-install obv. also has the latest OS build.
- vetinari 6y agoThe OOBE install contains apps you might not want or need (Garageband, iMovie, Pages/Numbers/Keynote). If you have one of the smaller SSDs, saving gigabytes of space on the first two might be interesting for you.
- sneak 6y agoYou didn't delete all the partitions, then. If you actually delete all the partitions on an M1 Air, it will not only not boot, it won't boot any external media either, as the firmware is missing. The machine then has to be put into DFU mode and restored from .ipsw via USB, like an iPad or iPhone.
- marcan_42 6y agoM1 Macs are not like Intel macs, Apple have done a dismal job of documenting them, and their "for users" tooling is still buggy and broken because the launch was clearly rushed. Here is what you need to know to actually understand these things: The SSD has 3 partitions. Each partition is an APFS container. Each container contains multiple APFS volumes. Your OS, and everything you care about, is on the second partition/container. The first partition contains boot configurations. The third partition contains the One True Recovery OS (1TR), which includes the Boot Picker menu (that thing you get when you hold down the power button). These partitions form part of system firmware, think of them as part of UEFI/BIOS. Do not touch these. If you mess up those volumes, the only way to recover the machine is via Apple Configurator 2 from another Mac (DFU mode). Disk Utility, the GUI, is broken sometimes. If something doesn't work properly there, ditch it and use the command line. Both Disk Utility, the GUI, and diskutil, the CLI, will hide the first and last APFS containers from you to stop you from shooting yourself in the foot. They're still there, just hidden from the main listing. You can get info for them. Be careful with that. To do OS reinstalls, you want to be in 1TR. This is not the macOS recovery. Hold down the power button and pick Startup Options from there. Then you can use diskutil (preferably the command line version). You should delete the whole APFS container (disk0s2 usually) corresponding to your install, which will contain multiple volumes. Re-create it as APFS. That will create a container with one volume. You can then install to it and the macOS installer will create all the other volumes. Additionally, the SEP data is stored separately from the OS (in one of the volumes of the first container). To wipe that, after wiping the partition and before reinstalling, run `xartutil --erase-all`. I've never tried that myself, and I suspect it's not really required because a reinstall should start with a fresh store, but it's probably a good idea to try if you have authentication/user-related issues after reinstalling. There is also OS recovery, which is the recovery instance that comes with an OS install. It looks exactly the same as 1TR, but it's not the same, and this is highly confusing. For any serious digging around, you want to be in 1TR. Booting holding down the power button will get you there, usually; after a failed macOS boot I've seen it go into regular recovery anyway. To be absolutely sure, boot into 1TR (holding down power, then startup options), then do a clean shutdown, and boot again the same way. More info on what's on the SSD of these things: https://github.com/AsahiLinux/docs/wiki/SW:Storage https://github.com/AsahiLinux/docs/wiki/SW:Storage
- jonplackett 6y agoI felt quite anxious reading this. Reminds me of the endless reinstalls I had to do of windows back in the 2000s and the anxiety of it all working again once it was back running. So glad that isn't necessary anymore.
- stinos 6y agoWhat is needed to mess up an OS so badly that a reinstall fixes it?
- bombcar 6y agoBack then it was mainly driver issues - you could also boot safe mode and see it trying to load many various versions of a driver - usually the graphics driver. You could fix it by hand or you could do a fresh install - which would also wipe out any errant startup programs, etc.
- jonplackett 6y agoWith windows 98? So many reasons. Driver issues, viruses, just not starting and you aren’t sure why. Crashing and you aren’t sure why. Blue screen of death and you aren’t sure why. I genuinely still have my 25 digit windows 98 license key memorised from having to reinstall it so many times.
- Theodores 6y agoGenuine question, but do Apple users upgrade to the latest version of the OS or is that optional? Just asking for a friend.
- matsemann 6y agoMacOS upgrades are often heavily breaking stuff. So developers will have to release new versions of their software fixing various bugs or be compliant with some new demand from MacOS for running. This often also leads to the new versions not being compatible with older OS versions or at least not being maintained. So as a user you're often forced to upgrade the OS if you want to use the newest versions of various software. Every MacOS update is a minefield. We have a dedicated Slack channel at work where people discuss if they dare to upgrade yet, and share which software now is breaking on their computers, warning others to wait.
- Theodores 6y agoThanks. It is webP support in Safari that interests me (well, my friend...). So this arrived in September 2020. What I want to know is if normal Apple users, i.e. not programmers, whether they can benefit from webP images yet, when using the default Safari browser. I have no idea in this pandemic about basic things.
- trinix912 6y agoIt's optional as long as your version of macOS is supported by the apps you're using, which is usually somewhere around five years. You can then still continue to use the old version, you just won't be able to update the apps / install new ones which require the new OS version from the App Store.
- braincode 6y agoI'm still wondering how to unseal a formerly protected SSV M1 volume after disabling all csrutil protections, namely: https://twitter.com/braincode/status/1360117171842478081 https://twitter.com/braincode/status/1360117171842478081 Device enrollment prompts are indeed annoying :/
- wil421 6y agoNot sure what happened with this guy but I was able to erase my brand new M1 Mac 5 times. My Mac had issues with the recovery process and wasn’t transferring all the files. I was able to fully erase and install OS X from recovery 5 times. My biggest issue was time machine. I opened a support ticket and they took a bunch of logs.
- m1mac 6y agoI agree that disk management of M1 Macs is poorly documented, but the author's issue appears to stem from: > Nope, this don’t work as I suspected… so, let’s check online, Apple suggests a long procedure and a short by typing “resetpassword” in terminal, that was a chance but since it founds no users, there’s no passwords to reset. "resetpassword" opens Recovery Assistant. Recovery Assistant is primarily intended to provide a "forgot password" flow, which is why it wants to identify a user. However, in the app menu bar, there is an option called "Erase Mac." That is how you do a full secure erase of an M1 Mac. It will work without any user, and even without any OS install at all. (I have tested this myself by erasing a machine multiple times without reinstalling the OS.)
- minikites 6y agoYet another example of Apple escalating the war with their own users who just want to use the computer they paid for.
- h0nd 6y agoI read this article in Italian voice and it felt totally right.
- sneak 6y agoThe best way to zeroize (as much as can be done closed-case without dedicated research) an M1 mac is the following, as far as I can tell: * boot external USB installer media * run `diskutil zeroDisk force /dev/disk0` * run `nvram -c` * power system off * system will now fail to boot anything, including external media, because it has no firmware available * put system in DFU mode [1] * plug in USB-C cable to the correct port (only one usb-c port can be used for this purpose) and connect to another mac running Apple Configurator 2 (which, sadly, is only available via the App Store, so requires an Apple ID, and also requires internet access to activate the attached M1 device) * Restore IPSW such as [2] (note that this is for 11.2.0 and is no longer current as of a week or two ago) This is the best way to get an M1 back into as close to a "factory" state as possible. Unfortunately, it requires an Apple ID (to use the App Store), so you have to dox yourself to Apple (email and working phone number, at the minimum) to get the Apple Configurator 2 app. (If anyone knows how to copy an App Store app from one mac to another, freshly installed mac, and have it work without logging in, please email me.) PS: If you're looking to go even deeper, following the zeroDisk you might wish to create a 100% blank/empty hfs volume on the disk0, and then "repair" it, which will TRIM the free space (99%+ of the disk) at the disk controller level as well. This may or may not have the same effect as writing all zeroes. You'll likely have to use `diskutil` to do this, as Disk Utility is mostly garbage. [1]: https://support.apple.com/guide/apple-configurator-2/revive-or-restore-a-mac-with-apple-silicon-apdd5f3c75ad/mac https://support.apple.com/guide/apple-configurator-2/revive-... [2]: http://updates-http.cdn-apple.com/2021WinterFCS/fullrestores/071-00846/DCCBFDF4-0B4E-4628-A843-F8755C863FB0/UniversalMac_11.2_20D64_Restore.ipsw http://updates-http.cdn-apple.com/2021WinterFCS/fullrestores... (shasum 7315f657df2a14b838b9d51eb49cdfff5be090e7)
- pornel 6y agoI also have lots of issues with reinstalling broken Big Sur. The installer apparently needs to phone home to Apple to get permission to reinstall the OS, and this fails. When this doesn't fail, it doesn't get permission to write to nvram, so the OS reverts itself to previous version after reboot. I like Macs having iPad-like performance, but I don't like the boot process is so locked down that it reminds me this computer belongs to Apple, not me.