Skip to content
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

macOS update "booted to Recovery" because "an error occurred migrating user data" on Big Sur/Monterey w/ multi-user Nix present #4531

Open
abathur opened this issue Feb 7, 2021 · 4 comments
Labels

Comments

@abathur
Copy link
Member

abathur commented Feb 7, 2021

No need to triage this. Opening it for visibility/support. To keep this focused, I'll save detail/discussion for the related PR (#4532).


We've had several people with multi-user/daemon nix installs report trouble with macOS system updates. (Single-user installs have been the default for a while; if you don't know you have a multi-user install, you probably don't). You may also encounter this if you have nix-darwin installed (regardless of whether you have a single or multi-user Nix install).

Updates to 11.2 (and probably 11.1):

During the multiple-reboot phase of a system update, the system will boot into recovery and show the message:

Your computer booted to Recovery because a failure occurred during installation.
An error occurred migrating user data during an install.
Reinstall macOS to resolve the issue.

Updates to 11.3:

During the multiple-reboot phase of a system update, the system will boot into recovery and show the message:

If you do not know the password for an admin user, the reset operation requires resetting the passwords of all accounts on the system.
Set a password for each user on your Mac.
... long list of users including at least nixbld1-32 and your user account

Workarounds

  1. If you run into these issues during an update: Multiple users have reported getting around this problem without having to reinstall macOS or reset user passwords by simply rebooting again. Since this issue is likely to recur on your next update, you'll probably want to also apply the next workaround after rebooting.
  2. Nix now has a nixbld-user migration script that should let you skip this heartburn. Since the problem seems to recur on each update, you may want to apply this fix even if you've already installed the most recent update.

If you've been affected by this and want to report it to Apple, you can refer to the feedback I've filed: FB8997501

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/anyone-else-get-errors-on-upgrading-macos-to-big-sur/12093/2

@emilazy
Copy link
Member

emilazy commented Apr 3, 2021

This was fixed by #4532, right? Or do we still need automation to migrate existing accounts?

@abathur
Copy link
Member Author

abathur commented Apr 3, 2021

Fixed will be squishy, here.

4532 should start fixing new installs whenever a release is cut, but makes no attempt to automatically fix existing installs.

@stale
Copy link

stale bot commented Oct 2, 2021

I marked this as stale due to inactivity. → More info

@stale stale bot added the stale label Oct 2, 2021
@abathur abathur changed the title macOS Big Sur updates w/ multi-user Nix present "booted to Recovery" because "an error occurred migrating user data" macOS Big Sur/Monterey updates w/ multi-user Nix present "booted to Recovery" because "an error occurred migrating user data" Nov 4, 2021
@stale stale bot removed the stale label Nov 4, 2021
@abathur abathur changed the title macOS Big Sur/Monterey updates w/ multi-user Nix present "booted to Recovery" because "an error occurred migrating user data" macOS update "booted to Recovery" because "an error occurred migrating user data" on Big Sur/Monterey w/ multi-user Nix present Nov 14, 2021
@stale stale bot added the stale label Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
@abathur @emilazy @nixos-discourse and others