Small Yellow warning triangle on my Mac. And the black text uses "might damage". That is not saying or implying "unsupported".
Small Yellow warning triangle on my Mac. And the black text uses "might damage". That is not saying or implying "unsupported".
Except there isn't, I already provided a solution in this thread previously but it seems you guys rather complain about a broken yet unsupported feature because "we have always done it this way":
Nobody stops you from storing your user data on a different drive than the internal one. Apple should be ashamed of selling 250GB Macs in 2023 still, as well.
ok.. I think there is a bit of cultural misunderstanding here.
For those of us who grew up with Unix/Linux/AIX/IRIX/HPUX/Ultrix we have always moved user home directories away from the system volumes. It is good practice, as it prevents a user from chewing up all the disk space on the system volume. Such mishaps often led to system hangs with mystery logs, broken files, weeping maintainers.
So it was and is natural for us to move user home directories onto another volume. It also allows us some insulation from system-upgrades gone wrong.
Many of us came from grown-up industrial operating systems (AIX/IRIX/HPUX/Ultrix) where this "just worked." I, for one, had never heard anyone from apple caution that it was unsupported. In fact, it "just worked" when I did it several major versions ago. It broke with Ventura 13.3. And it broke in a way that has little to do with logging in.
Disk file ownership is broken for external mounts. As root, do an ls -l for an externally mounted directory. The owner is _unknown and the UID is 99. Now as user Barney do the same thing. The owner is Barney and the UID is Barney's.
Interesting? Now log in as Fred -- the owner is Fred and the UID is Fred's.
Nevermind login support -- Ventura 13.3 screwed up file ownership on external drives.
My guess is that nobody said that file ownership and protection on external drives is unsupported.
The support engineer did not say "Oh, that's not supported" or words to that effect.
Quote from that support article:Doing this is also directly supported by Apple (link below).
Again, we seem to have very different definitions of what supported means. But I give up now, I am sure Apple will fix this "supported" feature any day now. I have had tiny 250GB Macbooks for years and had no issue storing my data elsewhere and never had to move the entire user directory. Nobody forces you to store the data on the internal drive. The only app I found that did not support being moved from ~/Library at all was some cloud sync, I think it was either O365 or iCloud, and I fixed that with a symlink.Update the user name in that field, but don't remove /Users/. For example, if “User name” is johnappleseed, then “Home directory” should be /Users/johnappleseed.
Of course not, they had no idea what you're talking about. Customer facing Apple support can handle a ticketing system and reads off a script, they're not unix sysadmins. Apple support is also known to pretend known issues don't exist.The support engineer did not say "Oh, that's not supported" or words to that effect.
Everyone please file bug reports via Feedback Assistant.
That link talks about renaming the home directory, whilst keeping it in /Users. It is not about moving it to another location.Placing user home directories off the root filesystem is an ancient and preferable Unix practice, especially when there are multiple users. Doing this is also directly supported by Apple (link below).
Change the name of your macOS user account and home folder - Apple Support
You can rename your macOS user account and home folder, which were named when the account was created.support.apple.com
https://www.reddit.com/r/MacOS/comments/124fods/_/je9yt8u
Caveat: while you have SIP disabled, you need to login to each user account that has a non-boot-drive home directory (i.e. do steps 5-6-7 for each account).
You can delete them and create new ones that are aliases of folders on another drive. There are permissions that you have to overcome (an ACL which denies delete to everyone), but otherwise it works fine. I have deleted my Music and Movies and replaced them with aliases to their locations on another disk. I have kept my Pictures in my home folder, but I am sure I could move it too.when putting data folders out of the home folder and on an external drive, is there a way that the original "Music", "Pictures" or "Movies" folders be redirected to this new location? Because they're folders you can't delete and adding alias to the new ones clutters the home folder.
sudo rsync -ah -A -X -U -N -H --info=progress2 "/Volumes/Macintosh HD/Users/${USER}" "/Users" --exclude "Library/Application Support/MobileSync/Backup" --exclude Library/iTunes --exclude Library/Logs --exclude Library/Messages/Attachments --exclude Library/Photos --exclude Audio --exclude Backups --exclude Documents --exclude Movies --exclude Music --exclude Pictures
for d in "Library/Application Support/MobileSync/Backup" Library/iTunes Library/Logs Library/Messages/Attachments Library/Photos Audio Backups Documents Movies Music Pictures; do ln -s "/Volumes/Macintosh HD/Users/${USER}/${d}" "/Users/${USER}/${d}"; done
Is there a way to repair user home folder permissions/ownerships/ACLs?This uses the MacPorts rsync binary to preserve ACL’s and extended attributes; note that the native macOS /usr/bin/rsync doesn’t have all of these flags.
That warning is there because changes can cause significant problems with the user account, particularly permissions. For instance, the User ID should not be changed without knowing what the implications of that change are. Such changes are not easily undone, hence the warning.
The permissions on home folder and top level folders within home folder should be like this:Is there a way to repair user home folder permissions/ownerships/ACLs?
ls -lahe@O /Users
...
drwxr-xr-x@ 90 gilby staff - 2.8K 6 Apr 10:03 gilby
0: group:everyone deny delete
ls -laheO ~
...
drwx------@ 25 gilby staff - 800B 2 Apr 16:26 Desktop
0: group:everyone deny delete
...
sudo chown <user>:staff <folder>
sudo chmod +700 <folder>
sudo chmod -N <folder>
sudo chmod +a "group:everyone deny delete" <folder>
diskutil resetUserPermissions
and repairHomePermissions
. These commands do more than just change top level permissions - e.g. change things within ~/Library.Do you maintain multiple backups? If so, rsync from a backup. There is no substitute for 3-2-1 backups. I was reminded in this episode that even a RAID is no substitute for maintaining backups.Is there a way to repair user home folder permissions/ownerships/ACLs?
I do maintain multiple backups using SuperDuper! (weekly) and Time Machine (daily). When doing potentially dangerous things, I also take a backup of my user folders to keep "air-gapped" from my activities.Do you maintain multiple backups? If so, rsync from a backup. There is no substitute for 3-2-1 backups. I was reminded in this episode that even a RAID is no substitute for maintaining backups.
The permissions on home folder and top level folders within home folder should be like this:
Code:ls -lahe@O /Users ... drwxr-xr-x@ 90 gilby staff - 2.8K 6 Apr 10:03 gilby 0: group:everyone deny delete ls -laheO ~ ... drwx------@ 25 gilby staff - 800B 2 Apr 16:26 Desktop 0: group:everyone deny delete ...
With the same for all of Desktop, Documents, Downloads, Library, Movies, Music, Pictures
To change [TEST THIS ON SOMETHING UNIMPORTANT]:
If ownership is not right, you needsudo chown <user>:staff <folder>
If POSIX permissions are wrongsudo chmod +700 <folder>
If ACL is wrong:
Remove ACL:sudo chmod -N <folder>
Add ACE:sudo chmod +a "group:everyone deny delete" <folder>
NOTE: ACL is an Access Control List which comprises of one or more ACEs (Access Control Entry).
----
The whole area of resetting a user account is very murky with Apple at various times saying how to do this (in Support articles) and then later removing those articles. Often discussing the use ofdiskutil resetUserPermissions
andrepairHomePermissions
. These commands do more than just change top level permissions - e.g. change things within ~/Library.
Have read of https://eclecticlight.co/2020/02/18/repairing-permissions-in-your-home-folder-has-changed/ and https://eclecticlight.co/2022/11/18/repairing-home-folder-permissions-a-mystery/ from Howard Oakley to get a feel for the confusion, warnings and possible ways forward.
Hi, I just wanted to let folks know about an issue I'm having with Ventura 13.3 - and to see if maybe anyone has a fix.
For years I've kept my Home directory on an external Thunderbolt SSD. It's all been more or less fine until I upgraded to 13.3 a couple of days ago. When the system restarted, it hung while logging back in to my main user account (stored on the external SSD). I have an admin account with the Home folder on the internal SSD, and that could login just fine. No matter what I tried, I could not get the Mac to startup with my main user account on the external SSD.
Apple recommended I reinstall 13.3 - so I did that, creating new Users, etc.
That allowed me to create a new User for myself and to use the Home directory on the external SSD. All seemed fine.
Except that when I went to the Mac App store, I could not login. It would accept my username and password, but the login dialog box would disappear, allowing me to click "Sign in" again, but never sign me in.
The only way I can get everything to work again is to put my Home folder back on the SSD. When I do that, I can again log in to the Mac App store (and iCloud generally) and everything works fine.
Just wanted to give everyone a head's up and see if maybe someone has found this to be a problem and has a work-around.
Yeah, this was a pretty serious issue causing data loss ... I could see them pushing this update out just to fix this one issue.It has been reported that 13.3.1 fixes this issue
It has been reported that 13.3.1 fixes this issue:
Update: Mac Home directory bug fixed with macOS Ventura 13.3.1
The System Integrity Protection affects setups that store Home directories on external drives.www.macworld.com