(Sorry for the claudefeels in this — I was working through the actual process with Claude and Claude Code and tried to get the facts back out of that chat history into this story post and it blurred until I couldn't tell what was mine and what wasn't. Weird state of things, but this sat in drafts for three months instead of doing what I meant to do which was spare some folks the hassle of figuring out how to set up and external user drive on a Silicon Mac Mini)
TLDR: I finally upgraded my 2TB+256GB i7 Mac Mini file server to an M4 Mac Mini 256GB with an external 2TB SSD for the user directory and had some frustrating file permissions problems to figure out. Specific steps are at the end.
After a catastrophic RAID failure four years ago, I looked at my options and set a $500 budget for a file server that could serve two main purposes: local file sharing access to my replacement RAID and local and cloud backups of that RAID as well as all my cloud services files on iCloud, Dropbox, etc.
The current model of Mac Mini was both too expensive and un-repairable, but the two-core 2014 Mac mini was easy to open and expandable using a standard 2.5 inch SATA drive. I got a clean refurbished i7 Mini from Pacific Macs and a 2TB SATA SSD. It turned out I also needed a logic board removal tool and an 821-1501-A cable to run two internal drives in a Mini that shipped with only one, but those didn't count against the budget. It all worked out in the end and the i7 has been running 24/7 for approximately 1337 days.
Basically it worked like this: the Mac Mini was always on and always online. The RAID connects over Thunderbolt 2 and backs up with SuperDuper to an 8TB Seagate drive. Separately, another USB drive works as the Time Machine destination and the Mini syncs everything ("keep offline", don't "optimize storage", etc) — everything comes to the Mini in a normal MacOS way and gets backed up in a normal MacOS way. That's the convenience tax for not trying to run this through some other kind of home-rolled server.
So anyway, I got excited when Apple put out the M4 Mini with expandable storage but of course they did it in the worst Apple way, with firmware and form factor lock-in. Popular blog posts pointed to a few grey market vendors and a complex process that requires a second Mac — something I have, but it was enough friction to stop me from trying. For my purposes, the base price of $699 +$300 in storage was out of my budget. A year or two later, the jackpot prices of that storage have doubled, all the Minis have been bought by LLM farmers, and Tim Apple killed off the low cost base model... while I was driving to the store to pick up the very last M4 256/16. (More on that in a moment.)
In the meantime, if it ain't broke don't fix it. But the i7 was broken in a deep way and that was the OS. Without a more modern version of MacOS than the i7 could run, iCloud does not allow file encryption. That meant my terabyte of iCloud storage wasn't deeply encrypted on Apple's side and security patches were harder to come by. Not great for an always-on machine with my most important files.
In comes OpenCore Legacy Patcher. Hobbyist software to get modern MacOS running on older hardware and keep those perfectly functional computers out of the landfill. With OpenCore Legacy Patcher I was able to get the i7 Mini updated to Sequoia and install subsequent patches which have become more frequent of late.
And that was doing fine for a few months, but the last few security patches really did drag down the perceived speed. I started to worry it was an OCLP issue and/or the inevitable thermal paste decay on the i7.
But what I didn't realize was that I could situate my /user folder on an external drive. Now, external drives that were $89 last year are over $300 now, so "wait until it dies and buy an M4/2TB" was still my main option — but there was also a real risk of M4 Mac Minis going away in favor of a low-end Mac Neo in the $500–$1000 range, and higher prices across the board on an M5 Mini. And then I remembered I already bought an $89 Crucial X8 2TB last year to use as a more rugged laptop Time Machine.
So wiping that 2TB and connecting it with a TB3 cable to a low-end Mini seemed like it would work for me. A $500 machine + a thing that was already on my desk. I also already had the $49 Thunderbolt 2 to Thunderbolt 3 dongle to be able to connect the RAID to my laptop. So after far too many conversations with friends, I finally got in the car on May 1 to go to the store and get the last M4 16/256 they had in stock. When I got there they also had an $899 24/512, and I tell you I thought a long time about that upgrade — but again it was beyond the budget for the use I had, and after two years waiting to buy an M4 it wasn't perfect enough to justify nearly twice the price.
A week later I finally sat down to set it all up. It was awful.
My settings kept resetting. Everything moved slow as rocks. Total disaster, I thought. There are special permissions that were obvious in hindsight but really hard to search for or track down.
I'd made an admin user on the internal storage. That user had wiped the external drive and created my main user and set up the home directory on the external drive. One admin macOS user can't just sudo another user's files, so both the drive and the home directory were owned by the wrong user and the permissions were all out of whack.
The steps to set up a user on an external SSD on an Apple Silicon Mac:
External Home Folder Setup on macOS 26 Tahoe
Problem
macOS 26 does not correctly set ownership when a user home folder is placed on an external drive. Symptoms look like OS bugs: settings revert on logout, Finder crashes on login, widgets reset, preference files fail to write. The root cause is a permissions problem.
Requirements
- External drive formatted as APFS
- Admin account separate from the user being created
Steps
-
Format external drive as APFS via Disk Utility
-
Create the home folder directory on the external drive manually in Finder or Terminal:
mkdir /Volumes/DriveName/username -
Create the user in System Settings > Users & Groups
-
Change home directory — right-click the user, select Advanced Options, set Home Directory to:
/Volumes/DriveName/username -
Log out of admin, log in as the new user once to initialize the home folder structure, then log back into admin
-
Enable ownership on the volume — this is disabled by default on external APFS volumes and must be done before any permission changes will work:
sudo diskutil enableOwnership /Volumes/DriveName -
Set correct ownership on the home folder:
sudo chown -R username /Volumes/DriveName/usernameNote: some system-protected directories under
~/Librarywill return "Operation not permitted" — this is expected and harmless -
Verify ownership:
ls -la /Volumes/DriveName/The home folder must show owned by
username, notadmin -
Full restart required — logout/login alone is not sufficient to stabilize the session
-
Log in as the new user and verify settings persist