Developer Preview 2 install wants "Setup User" password

The Mac Mini was bought new in June, and is a MacMini7,1, so I;m pretty sure it's not an old one.

Overnight, the progress bar has not moved on at all. so I think we can abandon that. My next planned steps are:

Check that the syadamin did not set it up for a locked drive for external access (He's going to laugh at that, because nobody here uses a mac as their desktop or laptop).

Power cycle, and assuming we get back to the "Setup User" password request, try those default passwords. If that doesn't work, I'm not sure what to do.

John

The sysadmin says ithe original 10.10.3 was installed from a USB drive. The machine has never been connected to another another Mac: we only bought it in June and we haven't used it for anything else. So I guess it's power cycle time.

So a new Mac. Well the key word might be "FileVault" - is there any chance that the sysadmin opted for to encrypt for security?

If no password can be found, I'd suggest that the next step should be booting into Recovery Mode. If you have the option to reinstall OS X (as opposed to "erase and reinstall" then it will install 10.11 over itself without affecting your data. It's possible that it may not let you though, in which case salvaging the data should be the priority because if you get it fixed through AppleCare, it will come back working, but very likely with none of your data on it.

Well, I power-cycled it, without holding down any keys. But instead of the blue "Setup User" screen, it came back up with a login screen, although network accounts weren't available. Loging in as the local administrator got me an OS X desktop, and About this Mac says it's OS 10.11, 15A204h. Does that sound right for DP2? I guess I'll try shutting down and restarting, and see if I can persuade it to to talk to our NIS.

There is no data on the machine that would require salvaging: originating anything on a beta OS that I don't understand very well would be foolishly brave IMHO. It's being used strictly to test software for compatibility with 10.11 and to do experimental builds with Xcode 7's compiler, so that we can find any problems, and be ready to release as soon as 10.11 is released.

It's now offering me the update to DP3, and I might as well take it. I haven't managed to connect it to NIS yet, but the sysadmin reckons he knows how to put that back.

The machine was not encrypted: there is no reason to do so, since it will never be taken out of the office, and doesn't have any business information on it.

Good, Safe Mode must have allowed it to get just that critical bit further with the installation. And yes, that build is Beta2.

You're right of course about data management and beta software (particularly OSs), but I've communicated with so many people with installation issues on these forums that don't have those principles hard-wired that I've started to assume the lack thereof.

Yep, upgrading to DP3 is definitely a good idea, not least because the integrity of the DP2 update is in question.

I have no adequate explaination for the "Setup User" account and blue screen.

Network issues seem to have persisted, for those that have had them, over the last update or two; I hope you're the exception - Good that your sysadmin is confident of a fix either way.

Glad you got it sorted 🙂

Thanks very much for your help! I've noted the salient points in my platform history document (I work with lots of OSes, and memory isn't good enough).

Sorry to be late at the party, but after the initial install of DP1 I noticed the following after running the setup assistant:

There was an extra (dmg? of about 55 MB, 7,2 MB used ) mounted as disk3, and was mounted at /private/var/setup/

This folder contains files owned by _mbsetupuser_ (I was testing on a macbook pro 13" 2011)

and contained mostly a Library folder, which contained lots of data similar to a user's Library folder.

I assume that this is something like a 'Template' folder.

after my first reboot this mount point was gone, but the user was still there ( id _mbsetupuser

uid=248(_mbsetupuser) gid=248(_mbsetupuser) groups=248(_mbsetupuser),12(everyone),61(localaccounts),701(com.apple.sharepoint.group.1),100(_lpoperator)

I can see it in dscl, output at the end of this post

I have no idea what happened, but I think it is a special user that is supposed to be used (once?) during initial setup.

If one stops the initial setup, maybe JGD did something special during this phase, with the result it tries to run at the wrong time....?

So I have no answers, only more questions.

Do others see this _mbsetupuser (or a similar name on iMac's?), uid 248, home ?

$ dscl . read /Users/_mbsetupuser
dsAttrTypeNative:accountPolicyData:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-/
<plist version="1.0">
<dict>
  <key>failedLoginCount</key>
  <integer>8</integer>
  <key>failedLoginTimestamp</key>
  <real>1437399001.147074</real>
  <key>passwordLastSetTime</key>
  <real>1436789092.3617449</real>
</dict>
</plist>
dsAttrTypeNative:IsHidden: YES
AppleMetaNodeLocation: /Local/Default
AuthenticationAuthority: ;Kerberosv5;;_mbsetupuser@LKDC:SHA1.C3C83EE22ECE5CFC82B1D4C1CB78F4DBD75D0BFC;LKDC:SHA1.C3C83EE22ECE5CFC82B1D4C1CB78F4DBD75D0BFC ;ShadowHash;HASHLIST:<SALTED-SHA512-PBKDF2,SRP-RFC5054-4096-SHA512-PBKDF2>
GeneratedUID: FFFFEEEE-DDDD-CCCC-BBBB-AAAA000000F8
NFSHomeDirectory: /var/setup
Password: ********
PrimaryGroupID: 248
RealName:
Setup User
RecordName: _mbsetupuser
RecordType: dsRecTypeStandard:Users
UniqueID: 248
UserShell: /bin/bash

I didn't do anything special that I know of; I downloaded the DP2 update and let it install itself. There were't any controls to use and I didn't do anything at the command line: OS X is sufficiently unlike other UNIXes that I don't try to use my (minimal) UNIX sysadmin knowledge on it.

The somewhat unusual thing about the machine is that it's connected to a NIS domain, as a source of what OS X calls "network accounts". That hasn't given trouble since the OS X 10.5 betas, although it gave plenty of trouble then.

And now it seems time for DP4...

John

Well, the problem of asking for a password for "Setup User" reoccurred when installing DP4. Turning the machine off and on got me past that, and it seems OK so far.

Hi again 🙂

As per mjsanders' investigations, you could look to see if there is a vestigal /private/var/setup folder. I have no setup folder there, so I'm assuming that it got properly deleted as part of the update process.

I've had the same issue on every beta since 2. Just finished Beta 6 install this morning and was sitting at the "Setup User"... holding power and booting up again seems to get around it. Filed radar... its now listed as a dupe.

Duplicate of 21212482 (Open)

Picture of the login...

https://dl.dropbox.com/s/71tiu1fshcqmzag/FullSizeRender.jpg?dl=0

I still have an _mbsetupuser logged in. Not sure if or how to delete it or force it to end.

This is still happening... 10.11.1 installed and the same problem. My radar was closed as a duplicate and the main ticket (21212482) is also closed so I have no idea whats going on. I guess from now on my install process includes holding down the power button at the login screen.