Patching zfs root in single user mode

Hi
I have to apply the Oracle recommended patchset to a server running on zfs root with zone roots also on zfs. The usual method of patching with Live Upgrade is giving some problems after the activation of the ABE. Can the patchset be applied to the server in the traditional single user mode
Any inputs would be appreciated

Yes, you can apply the patchset in single user mode, just keep in mind that your zones need to be bootable when patching as the patch installation will "partly" boot each zone when applying the patches. So if your zones rely on any NFS mounts etc, you will need to mount these first.
An alternative is to detach your zones during patching and then attach them using "zoneadm -z zonename attach -u" (or -U see the zoneadm(1M) man page for details on the differences).

Similar Messages

Disable single user mode

Is there a way to disable single user mode? I just booted in single user mode and w/o any password I changed my root password! In my mind this is a HUGE security hole, any one could gain root access to my laptop in a matter of less than a minute! I might as well not have a root password. I have the latest and greatest security updates, but this seems to be the biggest security risk in my mind.

If someone has physical access to your computer, your software is vulnerable in the way that you describe. There are a couple of approaches to preventing this problem. I have not tried any of this so I can only point you to some websites.
One way to prevent anyone booting into single user mode is to enable a password in Open Firmware, as described at Setting up firmware password protection in Mac OS X 10.1 or later. You would have to enter the password every time that you booted. And, you definitely would not want to forget your password; if you did, I don't know what you would have to do to recover.
A second approach is to use a 3rd party patch to prohibit casual use of the single-user feature. Look here for info on such a patch: Mac OS X Single User Mode Root Access. I believe that the software discussed here forces someone to type in a password to boot in single-user mode.
One question that I have about the second approach is whether it is possible for the patch to become out of synch with a future OS update. If that happened, one would also need a way to recover.
I hope this helps. If you are really concerned, I suggest that you do some internet searching on this topic.
Rich
EMAC G4 1.0 GHz Mac OS X (10.4.8)

Single User Mode: Still waiting for root device

iMac G4.
I reset the NVRAM, PRAM. It won't attempt to boot from anything but a OS 10.4 cd; booting from OS 9 cd just leaves me at the flashing question mark icon.
If I try to boot from OS X cd, it comes back with the prohibitory sign.
If I try to boot into single user mode, it gives me a bunch of "...."has no kernal dependency lines, then a 'still waiting for root device' line, and repeats that.
Something to the effect before the 'still waiting for root device' is "Waiting on <dict ID="0"><key>IOProvider-Class</key><string ID="1">IOResouces</string><key>IOResouceMatch></key><string ID="2">boot-uuid-media</string></dict>"
Any help please?

Nevermind...I found out that the hard drive was bad...still puzzles me why it wouldn't boot from CD though, as I thought they all should even if no drive is present.

Single User Mode: Searching for root...

My 2 year old unplugged my PowerMac iMac G5 (single) and now it won't start up.
I was finally able to boot up off of Disk Warrior and replace the directory, but it won't start up past the gray Apple screen. The fan comes on after about 45 seconds and blows hard. Then, I get the circle with a line through it, in gray. I've never seen that on a mac.. the international "no" sign.
When trying to start up in Single User Mode, I get a long list of stuff either disabled, not found, missing etc and then it starts writing to the screen every 30 seconds a line like:
Still searching for root.
I've tried pulling the back off, resetting the SMU, starting up in Safe Mode, etc.
This has happened with storms before and I can usually get it back.
I don't have original install discs.

When you say you have "OSX" but not the "original install disks" do you mean the mac originally came with an earlier version and you don't have those disks, but you have a retail copy of Tiger?
The circle with the slash means that Open Firmware cannot find BootX. Basically, I think this means that Open Firmware recognises the startup volume as such but cannot hand control to the operating system at all. BootX is what it uses to get the operating system going. Without this, as you've seen, you cannot make even single-user mode.
What is SMU?
*Is your data backed up? If not, prioritise that unless you can afford to loose it.*
Does DiskWarrior repair permissions? If not and you have the Tiger retail version, try running Disk Utility to do that. I don't think this will help, but it won't hurt.
Do you have another Mac? If so and you have the retail Tiger, you might be able to use Pacifist to replace BootX (in /System/Library/CoreServices). Alternatively, if the other Mac is running the same version of the OS and is also a PPC Mac, you could try copying the file from that machine.
Before you do any of this (with the exception of the permissions repair), try to backup any data you need if that's at all possible.
- cfr

Proper procedure for patching from Single User mode

Typically when I install a patch cluster from Sun, I do a sanity reboot from the console of the server using:
shutdown -y -g0 -i6
When the system comes back online, I log into the console again and then do:
shutdown -y -g0 -i0 (to go into OBP)
then
boot -s (to go into single user mode)
The procedure above was given to me from a Sun technician.
Then I install the patch cluster and reboot. It has come to my attention that Sun recommends breaking any mirrors between your disks before patching. I wanted to know what is the best way to do this for both Veritas Volume Manager and Solaris Volume Manager. For Veritas Volume Manager, I was thinking of going into the vxdiskadm menu driven utility and choosing the option to "Remove a disk for replacement" for the rootmirror disk and then after a reboot to check that the patches did not cause a problem, go back into vxdiskadm and choose the option "Replace a failed or removed disk" and select the rootmirror which should then begin to automatically resync itself to the primary rootdisk. Any comments on if this is a proper way to do this or if someone has a better method, I would love to hear it. I am assuming a system with just two internal disks: c1t0d0s2 and c1t1d0s2
Also, if anyone can comment on how to do this with Solaris Volume Manager or if it is required would be great also.
Thanks much for any advice.

Typically when I install a patch cluster from Sun, I
do a sanity reboot from the console of the server
using:
shutdown -y -g0 -i6
When the system comes back online, I log into the
console again and then do:
shutdown -y -g0 -i0 (to go into OBP)
then
boot -s (to go into single user mode)
The procedure above was given to me from a Sun
technician.Not a bad thing to check reboot before patching, but I don't think it's in any official documentation that I'm aware of.
Then I install the patch cluster and reboot. It has
come to my attention that Sun recommends breaking any
mirrors between your disks before patching.Again, I don't know if it's "official", but if you have a backup copy that you could boot from, it does reduce the possibilities of critical problems from a bad patch.
I wanted
to know what is the best way to do this for both
Veritas Volume Manager and Solaris Volume Manager.
For Veritas Volume Manager, I was thinking of going
into the vxdiskadm menu driven utility and choosing
the option to "Remove a disk for replacement" for the
rootmirror disk and then after a reboot to check that
the patches did not cause a problem, go back into
vxdiskadm and choose the option "Replace a failed or
removed disk" and select the rootmirror which should
then begin to automatically resync itself to the
primary rootdisk. Any comments on if this is a proper
way to do this or if someone has a better method, I
would love to hear it. I am assuming a system with
just two internal disks: c1t0d0s2 and c1t1d0s2
Also, if anyone can comment on how to do this with
Solaris Volume Manager or if it is required would be
great also.Well, it'll work as you've described, but what if the patches fail? The disconnected mirror is not bootable. You'd have to go through an unencapsulation and other things from a CD.
I've often simply pulled one side of the mirror while the machine was shutdown. Since the mirror was valid prior to pulling, it will boot. If there's a problem, I shut down, swap disks, and boot from the untouched mirror. If no problem, I re-insert, reattach the disk to the diskgroup, then recover the volumes.
I don't know of any nice supported method of booting from an offline VxVM mirror that doesn't involve a very long series of steps. My method isn't supported, but it does work. If you have both disks in the machine at the same time though, it'll update the private regions. Don't do that until you're ready to sync up one way or the other. Test before doing it in production.
In any event, you should have a backup ready to go.
Darren

Can't enable root user in single user mode

hey, im having a problem. I cant enable the root user in single user mode. This is what I do:
1.boot in single user mode
2.I run the command /sbin/fsck -fy
3.I run the command /sbin/mount -uw /
4.I run the command passwd
5.I type the password and then I retype it, but it gives me an error saying passwd: cant change password for root the account is not enabled (thats not exactly what it said, but you get the point)
this worked in leopard, why dosent it work now? can someone give me an alternative way or tell me what im doing wrong?
P.S. give me an actual answer not a why enable root? and I dont want to use directory utility.

The command is wrong man. Do the following:
Boot into S.U. Mode (Cmd+S).
once the terminal prompt opens, type the following:
mount -uw / ("mount"+space+"-uw"+space+slash)
launchctl load /System/Library/LaunchDaemons/com.apple.opendirectoryd.plist
passwd root
(after you press enter it will ask the password for the root user. Type it, even if it won't show any character. Then type again to confirm. Once you had finished type: exit).
Test it and post the results.

Terminology question: "booting as root" vs. "booting in single user mode"

Terminology question: "booting as root" vs. "booting in single user mode". Are these terms interchangeable, or is there a subtle or not-so-subtle difference? (Obviously something I don't do often.)
Thanks in advance.

Boot to Single user allows root access.
It isn't "booting to root" as in Linux, but I think is as close as it gets.
You can enable root from a normal boot:
http://www.youtube.com/watch?v=Y-JEpDi-cME
Interesting read:
http://www.securemac.com/macosxsingleuser.php
This is fun:
http://osxdaily.com/2007/01/22/what-happens-in-the-mac-os-x-boot-process/

Latest Patch cluster (Feb 11, 2010) unable to run in Single user mode.

Hi ,
This is my first post in this forum.
Hope you people will help to resolve the issue.
My issue - I have downloaded the latest patch cluster (Feb 11, 20100) and tried to install it from single user mode.
Nothing happened. I have waited for more than 30 mins, still no progres.
Then I killed the process, and tried to run it in Multi user mode (To verify any issue with extraction or file) -- Its working(and killed the process) !!!
Anyone facing this strange issue ?
Appreciate your help to complete the patching.
Thanks.
sas.

Hi,
If you're encountering issues with a patch cluster bundle your best bet is to contact [email protected] From the description it sounds like there may be a filesystem not mounted in SUM that the cluster is trying to patch.

Applying Solaris Patches that Require Single User Mode

Some OS patches require single user mode and reboot. Does the standard Solaris plugin patch management handle this? If not, could I write my own patch component and simply add "init 1; patchadd; init 6" to the execnative?
Thanks - Jay

I can't speak about the Solaris plugin, unfortunately, but a single execnative call wouldn't cover what you're trying to accomplish. There's an RFE for the core SPS system to add this capability, but I don't know that it will be added soon. Remember that when you switch runlevels, a number of start and stop scripts are invoked, shutting down and starting up a number of services. To do what you want to do, you'd have to have a start script for the RA in runlevel 1. You'd also have to have a way for the RA to execute a command on startup which isn't possible today. There'd have to be a way for the MS to deposit a command for the RA to execute, restart the RA in runlevel 1, the RA would have to read the command on startup and execute it, then restart the RA to runlevel 3 (or 6, whatever is your default or previous runlevel). It's all doable, to be sure, but not with changes to the core product.

Kernel panic on MacPro in Single-User mode after memtest.

I've had about 7 kernel panics in about 7 days on a new MacPro. 2 gigs of RAM (Apple Installed). Fresh install of OSX (no user import). While going through the troubleshooting process I ran memtest in single user mode. Ran it all night no errors.
So in the morning I typed ctrl-c and then exit (i think)... it seemed to start the process of booting and I got another kernal panic. I've actually done this three times now.
I checked panic.log and all the error messages but 1 were the same. Including the ones I got in single-user mode (copied below).
Should I be able to gracefully exit out of single-user mode without a kernel panic?
Does this point to a RAM error even though memtest and AHD for that matter ran all night without finding anything?
I'm all set to try again (taking careful notes this time) to see if I can reproduce but I was hoping for some feedback first.
Thanks,
Craig
Sat Jan 27 22:17:27 2007
panic(cpu 0 caller 0x41C47CC4): Uncorrectable Fbd memory error detected. ferr = 20000000 , nerr == 00000000, fErrFat = 20000000 nErrFat == 00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x108cd8 : 0x128d08 (0x3c9a74 0x108cfc 0x131de5 0x0)
0x108d18 : 0x41c47cc4 (0x41c49f1c 0x20000000 0x0 0x20000000)
0x108da8 : 0x41c47f58 (0x406a180 0x406a180 0x2 0x820044)
0x108e38 : 0x66a712 (0x406a180 0x0 0x3ba3680 0x0)
0x108e68 : 0x66a59b (0x3b92780 0x0 0x0 0x1c)
0x108e88 : 0x67d9be (0x1c 0x108ef8 0x8 0x67f4be)
0x108eb8 : 0x67db68 (0x3b91b1c 0x17 0x3b928ca 0x3b81120)
0x108f18 : 0x68a743 (0x3b34348 0x0 0xafdd0c77 0x4cd5)
0x108f38 : 0x70a4fb (0x3b34348 0x0 0x3abac80 0x0)
0x108f68 : 0x67053f (0x3b88600 0x0 0x3b87580 0x49)
0x108f88 : 0x669c1f (0x3b6b800 0x0 0x3b87580 0x49)
0x108fa8 : 0x3ba298 (0x3b87100 0x0 0x3b92f00 0x49)
0x108fe8 : 0x19aa80 (0x25423e30 0x25423e30 0x19bad6 0xb26000)
0x25423f18 : 0x1a445b (0x10 0x1 0x4af85c 0x6)
0x25423f38 : 0x19d871 (0x0 0x0 0x25423f68 0x206)
0x25423f58 : 0x135f14 (0x0 0x0 0x0 0x19d23a) Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleMCEDriver(1.1.2f1)@0x41c44000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x664000
com.apple.driver.AppleAPIC(1.2.0)@0x709000
com.apple.driver.AppleACPIPlatform(1.0.8)@0x668000
dependency: com.apple.iokit.IOPCIFamily(2.2)@0x57d000
dependency: com.apple.iokit.IOACPIFamily(1.2.0)@0x664000
Kernel version:
Darwin Kernel Version 8.8.4: Sun Oct 29 15:26:54 PST 2006; root:xnu-792.16.4.obj~1/RELEASE_I386
MacPro Mac OS X (10.4.8)

Welcome to Apple Discussions!
Yes, your memory or memory slot, or memory seating is bad or off. "Uncorrectable Fbd memory error detected. ferr = 20000000 , nerr == 00000000, fErrFat = 20000000 nErrFat == 00000000"
Clearly a memory related issue. It may also be that memtest doesn't know how to diagnose the new kind of memory and is reporting that back to the logs. Take it in to a service center to have all the boards replaced to make sure the issue isn't reproduceable with new memory. If it is, then I'd consider the slots on the logicboard a problem.

Why can't I enter single user mode on my Mac Mini for an admin password reset?

Hi,
I recently created a new user account for my mac and deleted the old one, not realising that this was the only account with admin priveleges. As such, I no longer have access to administrator priveleges, and cannot grant them to my new user account.
I have tried to boot in single user mode and recovery mode but neither command results in any reaction on the part of my computer.
This thread follows on from a previous, unrelated disscussion:
BDAqua: If you hold alt key at bootup do you see a lock in the middle?
Yenots: No...what does this mean?
BDAqua: If it did, it would mean Firmware Password Protection was enabled, which prevents booting in other modes, so that's not the problem, are you using a wired Mac KB, or Windows KB?
Yenots: I'm using an 'Apple Keyboard with Numeric Keypad' [ http://store.apple.com/uk/product/MB110B/B/apple-keyboard-with-numeric-keypad-br itish ]
If you find me here BDAqua, hit me with your knowledge!
Any other contributions are welcome and, now we're under the right heading, will hopefully help other users who have encountered this problem.
Thanks, Cristo

Hi,
Thanks for the link to MacPilot, and the sexy screenshot. I found an archived version for 10.4 on the koingosw website. That solves getting into single user/safe mode. Though I'd be interested to see whether sudo nvram boot-args="-s" will result in single user boot.
As for creating administrator priveleges for my new user account, I've found a method which looks good:
     \single user mode\
     cmd-s
     \mount drive\
     mount -uw
     \open 'directory access'\
     lauchctl load /System/Library/LaunchDaemons/com.apple.opendirectory.plist
     \list users\
     ls /Users
     \change password\
     dscl . passwd /Users/<username> <password>
I think that this method intends that if I change the root users password I'll be changing the administrator password (as root is the only user with administrator priveleges), and subsequently be able to change my new user accounts priveleges using 'netinfomanager'. But I'm not 100%. Could you give me your opinion on this?
Furthermore, three keys 'L' 'O' and '(' aren't working on my keyboard, which means I can't try this until I find an intact keyboard to borrow. I was thinking maybe a mod version of the above instructions would work in terminal using sudo, so I could use the keyboard viewer to type the missing characters. If you have any ideas on constructing such a mod I would be interested to hear them.
Otherwise, Thank You for your help BDAqua! And enjoy your summer wherever you are.

Single User Mode : Read Only Filesystem

I can't edit files in single user mode as Root. When I try to edit them I get a msg saying "Read Only Filesystem".
I have tried chmod with no evial. I want to change my .profile as root so cls='clear'.
Any ideas?
Also when I try to login to my account in single user mode it says that account does not exist. However I'm in that accunt right now!
Thank You.

When you boot up into single user mode, there is a single recognized user -- root. That's why they call it single-user mode and not multi-user mode.
When you boot up into single user mode, the disk mounts as read-only. You have to make it writeable in order to do anything to it. I forget the actual command but it displays on the monitor nearby where it gives the "fsck" command syntax when you first boot into it. It's something like "mount -uw /" or something to that effect. It is saying to mount the root drive ("/") with user write privileges.
Then just "pico /Users/Mephux/.profile" (although I profess that I don't understand why you have to edit this file as root).
(if you find that this solves your problem, or is actually helpful towards arriving at a solution to your problem, please consider clicking on either the "helpful" or "solved" buttons above)

Single-User Mode Copying Files/System Does not Boot Past Apple Logo Screen

I have a Macbook 2.0GHZ, 2GB RAM, that recently tried to download a secuirty and keynot update. Following the download the system will no longer boot past the Apple Logo Screen with the spinning wheel. I do not have access to a OS disk yet or to a firewire cable either. I've have seen posts from others that describe how to use traget disk mode to reinstall the secuirty update manually and then they can boot their computer. Safe mode will not work. I did boot into single-user mode and run the disk utility there and it says my HD is OK. Since I do not have a firewire or an OS Disk, I am wondering if there is a way to copy those files i need to a USB pen stick then install them onto the computer via single-user mode, considering this is the only way I can boot and manipulate the machine at this time. If this is not possible please let me know so I can find a way to scrounge up a firewire cable or disk. Thank you in advance for any assistance.
Ted K

Thanks to Limnos and BDAqua I know you guys have helped others with these kind of problems from the other posts I read. I just want to list what I did exactly in case anyone wants to try to do this with a usb drive or does not have access to a boot disk or firewire cable.
1: Install security update on a pen drive
2: Boot in single user mode, CMD-S on startup
3: /sbin/mount -uw /
4: mkdir /Volumes/usb (usb can be any name, name of usb drive or anything you want)
5: ls /dev (you need to get the drive listing for the usb drive to mount it appropriately, it should be disk#s# but this is close to what the HD and Cd drives are listed as so you may need to list once before you put the usb stick in and once ater. I had issues inserting the usb drive in single-user mode and it would freeze up the root drive)
6: /sbin/mount_msdos /dev/disk1s1 /Volumes/usb (this mounts the usb drive, i had to use msdos because of how my usb drive was formatted, you may need to check your usb drive format, hfs is the apple format for usb drives but it did not work for me)
7: cp /Volumes/usb/SecUpd2009-001Intel.dmg (this copies the files from the usb drive to the root drivel, at this point you no longer need the usb drive)
8: hdiutil mount /SecUpd2009-001Intel.dmg (this mounts the disk image)
9: cd /Volumes/"Security Update 2009-001" (after i mounted the image this is how it appeared in the Volumes directory, you might need to do ls /Volumes to get the name, the quotes are important to get the whole file directory changed)
10: installer -pkg SecUpd2009-001Intel.pkg -target / (this installs the acutal update, i used the SecUpd2009-001Intel.pkg and it worked though I think you might be able to use "Security Update 2009-001" with quotes as well.)
11: reboot
i hope this helps anyone looking to do this. Thanks again to those who helpes and all the other posts that had information that helped me identify and then fix my issue! I still love my mac.

Single user mode session lost after backgound processes jump in

We have an application running on SQL server. This application restores DB very frequently using Single user mode. Following are the SQLs that are executed to restore the database in single user mode and to get the database back in multi user mode.
alter database [test-db] set single_user with rollback immediate; --This sql is run using test-db
use master;restore database [test-db] from database_snapshot = 'snapshot_test-db';
alter database [test-db] set multi_user;
After switching the test-db to single user mode some 4-5 background processes of Taskmanager jump in for the test-db kicking off the session that application has taken over in single user mode . These background process are deadlocked between them selves.
Please refer to the output of sp_who2 below at link.
http://social.microsoft.com/Forums/getfile/200625
and following is the deadlock XML.
NOTE: SPIDs in deadlock XML may differ from the output of sp_who2 as spids keeps on changing for these processes.
<deadlock-list>
<deadlock victim="process4bbfc78">
<process-list>
<process id="process4bbfc78" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="705" schedulerid="1" kpid="1648" status="background" spid="22" sbid="0" ecid="0" priority="0" trancount="0">
<executionStack/>
<inputbuf>
</inputbuf>
</process>
<process id="process6d44388" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="419" schedulerid="1" kpid="5796" status="background" spid="30" sbid="0" ecid="0" priority="0" trancount="0">
<executionStack/>
<inputbuf>
</inputbuf>
</process>
<process id="process6d44718" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="109" schedulerid="1" kpid="3908" status="background" spid="16" sbid="0" ecid="0" priority="0" trancount="0">
<executionStack/>
<inputbuf>
</inputbuf>
</process>
<process id="process4bbee38" taskpriority="0" logused="10000" waitresource="DATABASE: 5 " waittime="313" schedulerid="1" kpid="2656" status="background" spid="15" sbid="0" ecid="0" priority="0" trancount="0">
<executionStack/>
<inputbuf>
</inputbuf>
</process>
</process-list>
<resource-list>
<databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
<owner-list>
<owner id="process6d44718" mode="S"/>
<owner id="process4bbee38" mode="S"/>
</owner-list>
<waiter-list>
<waiter id="process4bbfc78" mode="X" requestType="wait"/>
</waiter-list>
</databaselock>
<databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
<owner-list>
<owner id="process4bbfc78" mode="S"/>
</owner-list>
<waiter-list>
<waiter id="process6d44388" mode="X" requestType="wait"/>
</waiter-list>
</databaselock>
<databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
<owner-list>
<owner id="process4bbfc78" mode="S"/>
</owner-list>
<waiter-list>
<waiter id="process6d44718" mode="X" requestType="wait"/>
</waiter-list>
</databaselock>
<databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
<owner-list>
<owner id="process4bbfc78" mode="S"/>
</owner-list>
<waiter-list>
<waiter id="process4bbee38" mode="X" requestType="wait"/>
</waiter-list>
</databaselock>
</resource-list>
</deadlock>
</deadlock-list>
On searching for this problem I found out that people have faced similar problem but I was unable to find out the root cause and debug steps for this problem. Stopping the SQL server is provided as a solution to kick out these background processes but this
is not a feasible in our case as code to restore DB runs very frequently resulting in this problem at a good frequency.
I also made sure that SQL Server Agent is not running. The SQL services running on server are SQL server, SQL Server Browser and SQL Server VSS Writer.
Any help will be appreciated as this is a blocker problem.
Thanks,

Hi Amrita,
We can open a transaction, make data modifications to generate a lot of transaction log, and then run ALTER DATABASE AppDB SET MULTI_USER in the same transaction. You can also refer to the following document:
Getting out of single user mode:
http://blogs.msdn.com/b/dfurman/archive/2012/01/20/getting-out-of-single-user-mode.aspx
Allen Li
TechNet Community Support

Single user mode, Lost Admin Account, and Disk Permissions

Okay, so I have quite a few issues here. I will start from the beginning.
About a week ago, I tried to install some updates and I could not get the Admin account to work. I went to the users profile and noticed my Admin account was not there. Did a quick search and found Apple's outline of how to fix this via the Operational DVD and the root user. Tried this and it would never work, because as soon as I restarted the computer or changed screens it switched back to a standard account.
Next up, I went into the terminal to check the Admin User group. As it turns out it is not there. So I find a discussion on there that outlines how to rebuild this in single user mode and the Unix prompt. So, I print it off and try to restart in single user mode. After trying two different keyboards and a sum total of 8 to 10 times, I can't restart in single user mode to get to the Unix prompt.
One last thing, last night I went into the Disk Utility on the start-up DVD. I wanted to check the Repair Permission log and I got the following:
ACL found but not expected on "private/var/root/Library/Preferences"
ACL found but not expected on "private/var/root/Library/"
ACL found but not expected on "Network"
Thoughts?
Thanks for your help!
tpp

first, the ACL messages can be ignored. if you can't get to single user mode you can't fix your admin group. the only reasons that I know why you wouldn't be able to do that is
1. a defective keyboard
2. you have a firmware password set. have you? you'd have to turn it off before you can get to single user mode.
lastly when you restart in single user mode make sure you press command+s right after you hear the chime. do not press it too early or too late. lastly, I'm not sure which instructions you've found to fix the admin group but I have them in this thread
http://discussions.apple.com/thread.jspa?messageID=8011324

Patching zfs root in single user mode

Similar Messages

Maybe you are looking for