3 ms·

I was able to format the drive and whatnot... the problem is that High Sierra steadfastly refuses to kid from as RAID array (despite having been upgraded on one

by qubex 9y ago

I was able to format the drive and whatnot... the problem is that High Sierra steadfastly refuses to kid from as RAID array (despite having been upgraded on one and working from it previously), and APFS-formatted volumes are a real bloody pain to reformat. Now I’ve got a bootable system (as I mentioned, with two filesystems, an ignored /etc/fstab, and my user account with a customised home folder that requires booting into a utility account and then exiting) but my permissions are so mucked-up Excel doesn’t work (much to the perplexity of Microsoft), Mathematica’s fonts are broken, and iTunes can’t download music (despite my account recursively owning my music folder). It’s... miserable.

sitkack 9y ago
I believe your second /Users partition is marked as an external disk that doesn't respect permissions. In the finder, open the inspector panel for the drive (command I) and uncheck [] Ignore Ownership. Will still require chmod/diskrepair pass.
- qubex 9y ago
  That's very interesting and I really appreciate your interest and support, you've done more than anybody has since I got myself into this situation on the 20th of November. I have two SSDs each with an individual (encrypted) APFS volume. One (labelled Radix) is the boot volume and ends up mounted on /. The other one (labelled Usor) is meant to mount on /Users, but on account of being encrypted, gets ignored by automount (despite having a valid /etc/fstab entry) and just lingers, until I log in into a utility account, allow it to decrypt and mount, log out, and log back in as my user. My user has the home folder set to /Volumes/Usor/User/james and then it all works. But as lament, half the stuff is broken. As soon as I get back to the office I'll have a look at whether the ignore-permissions flag is set or not (I reckon it isn't, but it is worth checking). I've faced more path-blocking absurdities in this enterprise than I have in the past ten-plus years of Mac usership.
  - sitkack 9y ago
    I have almost no experience with APFS. I did run ZFS on my Macbook which required have / and /Users (on ZFS). It worked, but the performance was terrible. Sending snapshots to another machine was magical. I am much quicker to capitulate defeat in the face of unique setups like this. Or at least experiment with a VM and keep my work machine more main path. You will hit bugs, it looks like you already have.

by qubex 9y ago

sitkack 9y ago

I believe your second /Users partition is marked as an external disk that doesn't respect permissions. In the finder, open the inspector panel for the drive (command I) and uncheck [] Ignore Ownership. Will still require chmod/diskrepair pass.

qubex 9y ago
That's very interesting and I really appreciate your interest and support, you've done more than anybody has since I got myself into this situation on the 20th of November. I have two SSDs each with an individual (encrypted) APFS volume. One (labelled Radix) is the boot volume and ends up mounted on /. The other one (labelled Usor) is meant to mount on /Users, but on account of being encrypted, gets ignored by automount (despite having a valid /etc/fstab entry) and just lingers, until I log in into a utility account, allow it to decrypt and mount, log out, and log back in as my user. My user has the home folder set to /Volumes/Usor/User/james and then it all works. But as lament, half the stuff is broken. As soon as I get back to the office I'll have a look at whether the ignore-permissions flag is set or not (I reckon it isn't, but it is worth checking). I've faced more path-blocking absurdities in this enterprise than I have in the past ten-plus years of Mac usership.
- sitkack 9y ago
  I have almost no experience with APFS. I did run ZFS on my Macbook which required have / and /Users (on ZFS). It worked, but the performance was terrible. Sending snapshots to another machine was magical. I am much quicker to capitulate defeat in the face of unique setups like this. Or at least experiment with a VM and keep my work machine more main path. You will hit bugs, it looks like you already have.