Even so, I’d suggest formatting on a Mac even if you plan to use the ExFAT format. And this format is fine if you plan to share your SanDisk Extreme SSD Portable between your Mac and a Windows PC. For others, the macOS installer just can’t do the trick, and a high-quality SSD is left unbootable.And it’s a format that both your Mac and a Windows PC can read. Some users seem to have all the luck, and the first external SSD they connect to their M1 Mac works fine with the Big Sur installer, and they don’t look back. When running Big Sur 11.1 on an M1 Mac, making a bootable external disk is entirely unpredictable.(You can access any Time Machine drive using the Browse Other Backup Disks option, available from the Time Machine menu bar item.) If your temporary computer is a Windows PC, the process is a bit. Just plug your Time Machine drive into the available Mac, option-click the Time Machine menu bar item, and select Browse Other Backup Disks. You will see the contents of the HFS+. However, far from 11.2 solving this problem, it actually makes it worse.Connect your Mac-formatted drive on your Windows PC and select ‘ Load file system from the device’ from File in the menu bar.
![]() Originnaly Formatted External Ssd Can'T Be Found On Windows Hine Full Installer AppGet the drive formatted in the NTFS file format. Find your SSD drive in the list, right-click on it, and select Format. Disk Management should be open on your screen. Using the 11.2 full installer app, the one SSD (Samsung X5) that worked for me before works still, and the SSD which wouldn’t take a bootable installation of 11.1 still won’t oblige.Press the Windows + R keys at the same time, type diskmgmt.msc, and hit Enter. The M1 Mac started to boot from the external disk, before the display went black for a while. This didn’t work at all, as each attempt to start up from 11.1 on the external disk resulted in a boot loop kernel panic. Trying to restart from the external disk then results in an error.Updating a bootable external disk to 11.2As Apple hasn’t provided an update installer for 11.2, the logical way to update an existing bootable 11.1 external disk is to restart from it, and run Software Update. When that finally completes, instead of the Mac restarting from the external disk to complete installation, the installer just quits. At that stage, Activity Monitor reports that com.apple.MobileSoftwareUpdate.UpdateBrainService is taking lots of CPU, and there’s sustained and intense disk activity for many minutes. Please update this Mac and retry.”I therefore had to create a new user on the external disk, but was puzzled when that user had to have a different user long and short username. Additionally, I was informed that “Due to an issue with unlocking this system, you can’t migrate. During installation, I elected to copy account settings from my internal SSD, but this failed because “This Mac can’t be used to migrate data”. This eventually worked, but only after encountering further problems. This failed late during the installation, with the common installation error that ownership of the disk couldn’t be set.The only option left now was to start from scratch and format the external disk using Disk Utility, then install a fresh copy of 11.2 on it. This fails repeatedly after performing a full download of the update, merely reporting that “some updates couldn’t be installed”. Users who want to boot from an external disk would be wise not to buy an M1 model, until Apple has fixed these problems completely.With the release of 11.2.1, I have tried to update my bootable external SSD from 11.2 to 11.2.1. Some SSDs work, others don’t, and it seems a gamble as to which will work with any given M1.It doesn’t appear possible to update a bootable external disk, only to format it and install a fresh system, as if the disk had never had macOS installed before.The 11.2 full installer is incapable of copying existing account settings from the internal SSD to a fresh installation of 11.2.M1 Macs currently don’t work reliably with bootable external disks. It also appears reliable switching to and fro using the Startup Disk pane.Big Sur 11.2 does nothing to make it easier to make external disks bootable. The bootable external disk therefore now has two admin users: one copied from the internal SSD, the other created afresh.That said, my Samsung X5 is at last a bootable external SSD running Big Sur 11.2. SSD incompatibility with macOS is very rare, and I’ve never heard of anyone working around it with a user setting.Finally, the comment refers to booting from an external SSD. Support for external SSDs in macOS is very different from that, and isn’t in my experience dependent on whether an SSD manufacturer tests with macOS or not. Not only is there no “grub boot menu”, but users can’t set preferences for low-level control over external SSDs in this way. It there attributes these problems to SSD manufacturers for not testing compatibility with operating systems other than Windows, a claim which isn’t supported at all by the observations given for Linux, where a variable had to be set in “the grub boot menu”, which isn’t common to “*nix like OSs” as far as I’m aware, but Linux-specific.As I wrote, macOS doesn’t work like this. As the 11.2.1 full installer isn’t yet available through softwareupdate, that too will fail to deliver an update from 11.2.Looking again at that comment, it is almost entirely about Linux, and only attempts to make a generalisation to “*nix like OSs” in the final sentence. Windows 10 bootable usb for macI’ve been told that there was a bug in APFS that looks for this hard-coded string, and that when APFS was introduced, installs would fail without itApple engineers told me, after a month of looking at my install logs, that the problem was the system could not authenticate itself with Apple’s servers and thus hung.I tried both at once, and it worked, and I dare not try to test which works and risk breaking my system, as I don’t wanna be stuck internal booting and wearing out the internal SSD, with all the precious firmware on it.If you wanna experiment, I’d say open disk utility, view all devices, select the root device for your external boot disk, erase it as APFS, name it Macintosh HD, reboot to recovery (or a recovery USB preferably, follow , it’ll make a bootable disk that seems to work fine on M1’s), install MacOS to the disk, and see what happens.If this doesn’t work, maybe it’s the authentication issue the engineers were banging on about.(BTW, heads up: I’m on 11.1 and can’t install 11.2 on my external disk because the updater doesn’t work on external boot disks, so it seems. Eventually, one of two things got it working:1: I renamed the disk “Macintosh HD” before installation. So even if macOS did have something akin to a “the grub boot menu”, what difference could that make?I’ve got my M1 mini booting off an external disk, Samsung T5 (not X5, it’s regular USB over USB-C).It was no small task, took two months of messing around. This implies that a lack of this authorization previously is what caused all the problems. It then presented me with a list of users from my external boot system and asked me which of them I wanted to authorize to be able to administer the Mac Mini. I saw a dialog box I’ve never seen before which hints at what the problem was all along when I updated the internal drive to 11.3, I got a warning saying the attached external drive needed to be authenticated with an administrator account to work with this machine, else features like Software Update would not work. ![]()
0 Comments
Leave a Reply. |
Details
AuthorJohn ArchivesCategories |