27 ms·
External boot disks still don’t work properly with M1 Macs
- sdfhbdf 6y agoI don't see it in mentioned in the article but could be a driver issue for the enclosures of theses disks. Had that happen when I was using shitty cables for an SSD to my Raspberry. Otherwise it's entirely possible it's for security reasons and somehow related to the secure enclave stuff. But I might way out of my depth here. What is the use case for using an external boot disk with a mac?
- jlokier 6y ago- Booting to recover your data when the system has trashed itself, typically due to a failed software update, to the point that it won't boot off the internal drive but the drive is still working. This sort of thing has been seen with older MBs. - Continuing to be able to use your laptop when the internal drive has failed. Very helpful if you can't afford a replacement, or if you need to carry on without waiting for a replacement and you have a recent backup. - Booting older versions of MacOS (that don't know about APFS, or if you have reason not to trust APFS partitioning) for testing, compiling for an older target, running software that doesn't run on the current version of MacOS, or other reasons. (But old MacOS won't work with the M1 so that doesn't matter at the moment.)
- yoz-y 6y agoOne thing that comes to mind is that as a developer you don't have to pollute your main partition with a beta if you can install it on an external drive.
- londons_explore 6y agoSSD's support namespacing allowing exactly this...
- gtufano 6y agoAFS has containers to install betas on the same partition, the main partition is not polluted (and the additional volume(s) can be removed at will). cfr. https://support.apple.com/en-us/HT208891 https://support.apple.com/en-us/HT208891 I'm not saying that it's "normal" not to be able to boot from external devices, I'm just answering your point
- minimaul 6y agoThis is quite risky - previous beta updates (such as Big Sur) did break installing updates on older OS releases in the same APFS container, and some beta updates have in the past done incompatible APFS updates that broke the ability to boot old OSes. Safer to use a separate disk or partition.
- simonh 6y ago* Recovery of the machine from an external clone disk in case of disk failure. * Booing up a disk from another machine where it's suffered a non-disk failure. * Because I want to.
- parsimo2010 6y agoI once worked with a team that worked three 8 hour shifts and flexible seating, so there were about 3 times as many workers as there were desks and each team member might be sitting at several possible computers. Rather than worry about syncing personal files and profiles across a network, each team member had their own external drive that they used to boot the Mac mini wherever they were sitting. There may have been better solutions for that particular team, but this certainly worked and I’d hate to throw away the option for doing something like that in the future. And I’ve booted Linux from an external drive a zillion times on a PC. It’s fairly handy to have the option.
- Spooky23 6y agoThat’s really cool. I used to support a similar need with an enterprise tool that cost exponentially more to implement and support.
- londons_explore 6y agoPerformance kinda sucks unless you pay a lot of attention to buying the right model of drive. Most drives are simply designed for storing a few TB's of photos and videos. As soon as you are doing low latency paging to the drive and millions of flush() operations, things bog down pretty badly, even on a modern SSD. Simple things like USB not having any decent way to do shared memory with the host are a big part of it...
- londons_explore 6y agoThe fact the errors occur before the "reboot" part of the installation tells me it isn't a driver issue. The "unable to set startup disk, SDErrorDomain 104" suggests the error is a check in firmware preventing this. It's probably simply unimplemented, and rather than try anyway there is a check somewhere in the firmware that the drive being marked bootable meets some criteria. Clearly the internal drive meets that, and some external drives do. Running a tracer on the commands sent to the drive would likely identify it.
- LocalH 6y agoI don't even think it should have to be justified. Booting from external media is one of the most basic computer maintenance tools we have. It's not like the computing industry has been giving two shits about user freedom anyway. The cynic in me wants to say that the insecurity of modern computing was intentional, so as to eventually require such user-hostile lockdowns. However, the rationalist in me understands that it most likely just ended up happening this way by chance. Either way, it's unfortunate that everything is being locked down more and more in the name of security. At the very least, such walled gardens should be opt out.
- deleted 6y ago[deleted]
- evgen 6y agoSome options/ides from the team that does the SuperDuper backup and disk dupe tool: https://www.shirtpocket.com/blog/index.php/shadedgrey/thats_big_sir_to_you/ https://www.shirtpocket.com/blog/index.php/shadedgrey/thats_...
- michelb 6y agoThis may be fine for the current M1 macs, since they are most likely not used by professionals or people that will do potentially installation damaging things, so a trip to the Apple Store will suffice. But this better work once the pro machines come out. It's already hard to recover data from the newer mac's when your system installation has issues, not being able to boot from another drive is going to suck.
- rowanG077 6y agoThe pro machines are allready out. You can buy a Macbook pro M1 right now.
- coldtea 6y agoParent doesn't mean machines with "Pro" in their branding name, they mean the models actually used by technical/cpu-demanding pros in video/graphic design/audio/3d/etc. (non technical/cpu-demanding professionals, e.g. some office working just needing web and excel, can use Macbook Air or whatever too). And those aren't out yet, those would be the 16 MBP, the Mac Pro, the iMac and iMac Pro, and so on.
- Toutouxc 6y agoYou can also use the "MacBook Air or whatever" to compile code just as fast [1] as the 16" MBP. If that isn't a cpu-demanding task then I don't know what is. (not trying to be rude, just that the Air is currently a very capable and pro-tier machine) [1] https://www.macrumors.com/2020/11/17/apple-silicon-m1-compiles-code-as-fast-as-mac-pro/ https://www.macrumors.com/2020/11/17/apple-silicon-m1-compil...
- sudosysgen 6y agoThose kinds of professionals won't be comparing it to other MacBooks, but to other computers of the same form factor. The M1 Macs still aren't the leader in multicore performance or multicore performance per watt. If you're a programmer that mostly relies on multicore performance, the current M1 Macs aren't the gold standard. Unless of course you are drawn to the OS or something else.
- s_dev 6y agoExternal SSD is my default setup. I encourage it in the office as well. Even my gaming machine is setup at home this way. When popping over a mates I often just plug it out and stick it in to their machine. It's very useful to be able to seperate data from the hardware. If something is wrong with a machine I can just plug straight in to another one. An SSD is much easier to carry than a laptop. The other problem with internal hard drives is when they get stuck inside e.g. with MacBooks being sealed these days. External SSDs can offer great flexibility and a trade off worth considering. I can imagine people having security concerns etc. Disappointing to hear this about the new M1s. I recommend people interested in dipping their toes into Linux Gaming trying this approach: https://www.easyuefi.com/wintousb/ https://www.easyuefi.com/wintousb/ https://rufus.ie/ https://rufus.ie/
- protoman3000 6y agoHow do you boot Windows from USB without using third party tools?
- adrian_b 6y agoI have no idea. That is why I boot Linux from Thunderbolt or USB and for the few Windows programs that I need I use either Wine or a Windows VM.
- s_dev 6y agoWinToUSB is $50 but they allow you to do Windows Home and MBR partitions for free. Rufus and Disk Utility for Linux/mac OS
- userbinator 6y agoLook up WinPE. It's a lightweight "live CD/USB" version of Windows that can be run entirely in RAM. A full "portable Windows" install can be made from it. AFAIK all the third-party tools do is automate the process of copying thousands of system files and also act as a boot manager.
- easton 6y agohttps://rufus.ie https://rufus.ie Load a Windows 10 ISO and click Windows to Go, wait a couple minutes. Full Windows on a USB and it’ll automatically rediscover hardware if you move it to a new PC.
- carlosrg 6y agoSlightly off-topic but I remember when system updates on Macs were handled much better than for example Windows. I think that's no longer the case: you can't download standalone updates (the .pkg) anymore, and installing them feels like you're installing the entire OS (even a minor release like 11.2.1 needs a several gigabyte download and takes a long time to install).
- CharlesW 6y agoI believe you're right that you can't download "delta" updates, but standalone OS installers/updaters can be downloaded. Go to https://apps.apple.com/app/macos-big-sur/id1526878132 https://apps.apple.com/app/macos-big-sur/id1526878132 (for Big Sur), click "Get", use Software Update to monitor the download progress, then "rescue" the installer ("Install macOS Big Sur.app") from Applications folder.
- marcodiego 6y agoI think we're just a few steps away from having our own devices in such a deeply locked state that boot disks will eventually stop working on any sufficiently modern system.
- my123 6y agoIt's just a set of bugs here, because of it using a redesigned boot chain. The bugs will be fixed, just takes some time. Has nothing to do with trying to impose additional restrictions.
- marcodiego 6y ago> Has nothing to do with trying to impose additional restrictions. For now, maybe. Consider the time when microsoft was partially successful to boot-lock arm devices: https://www.softwarefreedom.org/blog/2012/jan/12/microsoft-confirms-UEFI-fears-locks-down-ARM/ https://www.softwarefreedom.org/blog/2012/jan/12/microsoft-c... The old adage "do not assign to malice what can be properly explained by stupidity" should not be blindly applied when it involves powerful companies.
- my123 6y agoI can assure you here that it works on some drives but not others because the boot chain on Apple Silicon Macs is written from scratch, not using UEFI. Bugs are being worked out slowly, and there's no reason to assume bad intentions here. (I have an Apple M1 MacBook Air, and it boots from a Samsung T7 external SSD just fine)
- machello13 6y agoIMO this line of thinking implies a lack of contextual understanding about Apple's culture, strategy, and history. Of course we can never predict 100% what big companies will do, but we can be pretty sure Apple isn't interested in doing that.
- bitcharmer 6y agoNo, it's just Apple. The rest of the world doesn't do this nonsense.
- aloer 6y agoOT: one of the nice little things with MacBooks is that you have a disk cloning thing built in. It takes literally one step and half an hour to clone my internal 512gb ssd to external Samsung t5 and have it booted up. No problems whatsoever and I’ve been successfully copying the same system back and forth about 10 times last year One thing I do recommend though: remove airpods from the Apple account before cloning and pair again once the same system is running on new hardware. Sometimes this causes problems
- Toutouxc 6y agoDoes anyone have any info on why the actual macOS installation isn't bootable by both architectures? I seem to have lots of different universal and x86_64 binaries and kexts on my M1 machine. Also the kernel (that I thought was the actual kernel in use) in /System/Library/Kernels reports "Mach-O 64-bit executable x86_64" so I'm kinda confused about all this. I'd appreciate any pointers.
- pram 6y agoI presume it’s because the M1 variant doesn’t use EFI to boot.
- Toutouxc 6y agoThat's what I'm expecting to learn, but I wonder what's going on inside regarding the kernel and dylibs (and other stuff I don't understand yet).
- my123 6y agoOn your M1 machine, the used kernel is /System/Library/Kernels/kernel.release.t8101. (for T810x processors, A14 is T8101 and M1 is T8103, both share the same kernel) The installation should be bootable by both, but not sure that the flow to bless an install done on another machine to be bootable on an other M1 one is done/fully functional yet. (on M1 machines, you need to bless external volumes before booting from them) Booting an install done on an M1 on an x86 Mac should work already though.
- marcan_42 6y agoThat's not the kernel. I mean, it's the kernel, but not the kernel that the machine boots from. The built-in bootloader actually boots iBoot2 from /System/Volumes/Preboot/(UUID)/boot/(long hash)/usr/standalone/firmware/iBoot.img4, and that then loads the Darwin kernel from /System/Volumes/Preboot/(UUID)/boot/(long hash)/System/Library/Caches/com.apple.kernelcaches/kernelcache. However, the system firmware can only boot this from the internal SSD, not from any external storage. When you choose an external disk to boot from (the "bless" thing), those files get copied to the internal SSD, and it boots from that instead.
- louwrentius 6y agoEven on an Intel Mini, USB-C boot takes much longer than internal boot, seemingly due to Apple shenanigans. I have worked with External SSDs on Macs for years. Partially because to circumvent the Apple Price Tax. But also to just treat storage as something easy to swap.
- marcan_42 6y agoThe M1 boot process is very different from Intel macs. In fact, they do not support external boot disks at all, by design. This is because the built-in firmware is extremely minimal, and does not contain drivers for anything but the internal SSD. It doesn't even have a keyboard driver, or any kind of GUI other than showing the Apple logo and "Entering startup options" text, and some error screens. All of this is by design, for security - UEFI is an enormous hairball of code, especially on Intel macs, and almost impossible to secure properly for that reason. When you boot into the "Startup Options" menu, you are booting into a special macOS partition in the internal SSD. M1 Macs use macOS as the moral equivalent of the UEFI setup menu. That boot picker that looks like the UEFI boot picker on Intel Macs? Yeah, that's a full-screen app on macOS made to look similar. So how does external boot work? The "blessing" process done by the Startup Options screen involves copying the entire macOS Preboot partition - iBoot2 OS loader, Darwin kernel, auxiliary CPU/device firmwares, device tree, and some additional stuff - to the internal SSD. It then creates a local, signed boot policy that allows system firmware to boot this macOS install. You aren't booting from an external disk. You are booting from the internal SSD, with the root filesystem on the external disk. Additionally, the integration of the macOS user credentials with the SEP means that you can't "just" take an install made on another machine and use it on a separate one. It involves importing user credentials into the local machine. This process isn't implemented properly yet. As you might expect, this entire mechanism introduces a ton of corner cases around updates, boot selection, etc., and it is still very buggy and broken. The M1 launch was, when you look at details such as this, very obviously rushed. Further reading for those interested: https://github.com/AsahiLinux/docs/wiki/M1-vs.-PC-Boot https://github.com/AsahiLinux/docs/wiki/M1-vs.-PC-Boot https://github.com/AsahiLinux/docs/wiki/SW:Boot https://github.com/AsahiLinux/docs/wiki/SW:Boot https://github.com/AsahiLinux/docs/wiki/SW%3AStorage https://github.com/AsahiLinux/docs/wiki/SW%3AStorage I'm actually eagerly waiting for Apple to fix this in future system firmware releases, because my plan for installing Asahi Linux for end users with a minimal amount of fuss is to abuse the mechanism to adopt foreign macOS installations. This elides the current need to have a completely wasted, 60+GB macOS install as a dummy to actually launch Linux (we could clean it up and resize it to get the space back, but it still makes for a very annoying install process that I'm hoping to avoid). On the plus side, this dual-booting mechanism is very cleverly designed to separately secure different OSes, so you do not need to downgrade security on your machine to install an unsigned OS like Linux. It is a separate OS with a separate security policy. You can keep your macOS install fully secure, and capable of running iOS apps and other actions that require secureboot, and install Linux (or another macOS with a custom kernel, kexts, etc) in parallel, completely unintrusively. So kudos to Apple for designing this whole thing, and for opening it up for us to use :)
- cletus 6y agoI don't use an external boot disk but I certainly understand why people do. And yeah this needs to be fixed. But is anyone else shocked at how well the transition to ARM has gone for Apple? Because I am. I figured this would be something I would avoid as long as possible but honestly I'd probably be happy with this year's MBP M1 refresh.
- whatthesmack 6y ago> But is anyone else shocked at how well the transition to ARM has gone for Apple? I totally get why some folks would want to wait for the next-gen of these initial machines, but I'm not surprised at how well it's gone. I chose to buy the initial M1 MacBook Air model right-off-the-bat. The reason for this is that I went through the last two Mac CPU arch transitions (68k -> PPC, PPC -> x86), and the way Apple was able to handle those was truly impressive to me. Plus I really needed more built-in storage ASAP :)