-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
/nix does not mount after upgrading to macOS 15.1 #1261
Comments
When you've freshly rebooted and the store is not mounted, what is the output of the following commands?
When you say "Manually mounting the disk works", how do you do this? Via the Disk Utility app, or via the |
Output here:
Yes, I use the Disk Utility app.
NOTE: Every time I restart the MacBook I need to manually mount the disk again. |
That bad request is very weird, and something I have never seen before................ However, after some searching I think I've found a similar issue on the NixOS Discourse: https://discourse.nixos.org/t/macos-upgrade-breakage/50691, and this post proposes a solution: https://discourse.nixos.org/t/macos-upgrade-breakage/50691/7. Could you give that a shot and see if it fixes your issue? |
Hm. I found another issue that also had the "Bad request" text: NixOS/nix#9978 If you run If that doesn't solve your issue, what is the output of |
They all seem to be enabled.
|
Also of note is that I did reinstall my MacBook twice. The first time I noticed this issue I thought it might be because of something I had done. The second time the issue still persisted, which is when I created this issue. |
@grebban-yamashita interesting. Looking at your log, it looks like you're installing the standard upstream Nix:
and then applying your flake with nix-darwin, which uses Determinate Nix. This is a huge hint for us. Determinate has the strong assumption that your Nix store is an encrypted APFS volume. Which, yours isn't:
Probably the most straightforward way forward is to uninstall Nix again (...sorry...) and reinstall with
and then it should solve itself. ...another approach is we could help you with the commands you'd need to run to enable encryption on this volume, and correctly store the secret in the keychain for Determinate to use for unlocking and mounting. |
p.s. @cole-h is working right now on improving this transition, so hopefully not a lot of people will run into this problem... |
Thanks! I have not had the time to reinstall yet, so I will not be able to verify if this solves the issue. I am fine with closing this issue, and I can re-open it when I reinstall if the issue persists. 🙂 |
I faced the same issue in Sonoma 14.4 M3 Pro. |
Using completely factory-resetted M3 MacBook Pro.
Manually mounting the disk works.
Kitty permission issue
Since the update I am also getting the following error when trying to start kitty.
Other Home-Manager apps start without issue.
To bypass this I start kitty from the Terminal.app, which is less than optimal.
Installation commands
Commands run on fresh macOS install are as follows:
No errors.
The text was updated successfully, but these errors were encountered: