Single-user mode

When I start up my computer and I want to get into single-user mode, it just goes to regular login.  Is there another way apart from command s or does something need to be changed.  Yes, I can access my computer, I just want to make an administer account without the disk.

Well you should not have killed it. Rollback might take much more time than same query would while running normally. I would say wait. DONT RESTART SQL SERVER SERVICE or take Database offline
What was query was linked server used in query. Was it distributed transaction ? If it was simple query it would take time but SQL Server would roll it back
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article

Similar Messages

  • Data back up from Single User Mode

    I have a problem with my 700 MHz iBook, dual USB, with OS X 10.3.9.
    Unfortunately the OS doesn't start up because of "overlapped extent allocation" problem...
    I would like to re-install the complete OS but before doing it, I would like to back up some directories.
    Is it possible to save some data, by connecting an Ipod or some sort of external peripheral, from the Single User mode?
    If yes, how can I do it?
    Thank you in advance from your kind support.

    Before giving up the ghost check out these:
    Manually fix Overlapped Extent Allocation Errors without Disk Warrior
    Overlapped overlapped extent allocation errors can be the bane of any Mac user's existence. Often, these errors go unnoticed until the problem becomes visible: your Mac might refuse to boot, crash unexpected, or worse, critical data might disappear from the Finder. Disk Utility can detect, but not fix overlapped extent allocation errors, and certain third-party utilities, such as Alsoft Diskwarrior, can fix them, but generally without reporting the consequences.
    Overlapped extent allocation error occur when the file system thinks that two files are occupying the same area on the hard disk, hence overlapping on the same "inode," which is the structure which holds the location of the data blocks the file occupies, and also file permissions and flags.
    Clearing the "overlapped" or "overallocated" extent allocation essentially means that you'll have to lose some data, because the only way to remove the overlap is to delete the file that's occupying the inode. So, if you suspect, or find out, that the guilty file is a critical system file that resides in one of the hidden system directories such as /etc /var /usr/ or visible system directories such as /System or /Library, and you don't want to reinstall the whole OS (which might not fix the overlapped extent allocation anyway), it's good to have another disk available to copy the files back to your original disk if necessary: a second bootable hard drive or a firewire drive connected to your Mac when you remove the misbehaving file. Just make sure that when you copy the file back to your boot disk that the permissions are correct, so it's best to use the "ditto" command, so that all sticky bits, flags, and permissions are preserved.
    In case you didn't know, you don't have to boot from an install CD in order to check for overlapped extent allocations. All you need to do is restart your Mac, while holding down command + S to boot in "single-user mode."
    At the command prompt that appears, type:
    $ fsck -fy
    If you have an overlapped extent allocation, you'll see:
    "Overlapped Extent Allocation" (File 123456d)
    No matter how many times you run fsck -fy, you'll never be rid of the error.
    So, simply issue the following command:
    find / -inum 123456 -print
    Note the "d" was dropped, or any extra letter that appears after the inode number.
    The find will return a file name that matches with the inode number, and the path to that file. If you remove the file then the fsck will not return this error next time you run it.
    However, before you can delete the file(s) in single-user mode, you'll need to mount the file system. Type:
    $ mount -uw /
    When done, issue the "sync" command, and that will flush the write cache so that all pending writes are written from memory to the disk. Also, since most OS X 10.3 Macs use the HFS+ Journaled file system, it might be a good idea to disable the journal before booting into single-user mode by typing:
    $ sudo diskutil disableJournal /
    then re-enable it when done fixing the overlapped extents and rebooting normally:
    $ sudo diskutil enableJournal /
    Chris Anderson is a long-time Linux propellerhead who just got his first Mac, an ibook G4, and can't keep his hands off of it. He currently works as a "The Architect" and general visionary for a maker of world-class collectibles.
    If you own Disk Warrior then it should be able to repair a drive with overlapped extents.
    There are two backup utilities included in Unix - psync and rsync. You will find them in the /usr/bin/ directory. For documentation simply enter: man psync or man rsync. In order to write data while in single-user mode you need to issue the command: /sbin/mount/ -uw / (Note: there is a "space" between the "uw" and the "/".) To mount an external drive you will need to provide the mountpoint for it in place of the "/", e.g., "/Volumes/volname") without the quotes.

  • How do i repair my hard drive in single user mode when disk is full?

    Hi there Apple Community!
    I have an old Macbook Pro 17" with an upgraded 500GB harddrive and 4GB memory. I'm running Mac OSX Lion.
    Was hoping you could help me out.  THis is the situation:
    Long story short I spilt wine on my macbook and the screen went a bit blobby. Switched it off for a few days, removed the battery etc. etc. Opened it up cleaned out as much of the wine as possible, but unfortunately some of it came in behind the LCD, so now the screen has a nice red stain.  Obviously I'm not going to try to clean that out of the LCD. 
    My Macbook Pro still worked for a few days after that, but then my harddrive gave up.  I booted in the Recovery HD menu, verified the drive and I got the error "Keys out of order - This disk needs to be repaired, click Repair Disk." I attempted to repair the disk but got the error "Keys out of order - Disk Full Error - The volume could not be repaired".
    Unfortnately of this 500GB I only have about 7GB free on it, as I have a huge iPhoto and iTunes library. I did make a TIme Machine backup of my user directory, but not the system files.  I don't really want to do a clean install because:
    1) I'm paranoid that there's something I did not fully back up
    2) I don't want to have to download the whole Mac OSX Lion again. I should have made a USB bootable backup when I had the chance.  I don't have access to a broadband connection.
    What I feel are my viable options, are as follows:
    1) I did buy a replacement internal 500GB harddrive, so I can probably try to make an image of the hard drive to this new drive, but not sure how. I believe it's through the Disk Utility with the "New Image" option but not sure how to go from there.
    2) Start up in Single User Mode and delete some unnecessary files and re-attempt to run the fschk -fy utility again (I tried this earlier and got the same Disk Full Error).  - the problem with this is, I'm not familiar with the command line and have no clue how to delete files.  I don't know my way around Unix.
    3) I can also probably attempt to make a Ghost Image or Acronis Image of the failed drive to this new drive, but not sure if Norton Ghost or Acronis True Image will be able to read this HFS drive - I believe it's possible as it's a simple hard drive clone. 
    If you can guide me in the best option - probably there is a better solution than my proposed ones above, I appreciate any feedback and comments you might have!

    hi Baltwo,
    So I ended up copying my user folder to another harddrive. I managed to download the whole osx lion again, reinstalled, and recovered my home folder using this discussion:
    I have managed to get all my files back. My iTunes library works fine, but my iPhoto library when I open it, get the following error:
    iPhoto cannot be opened because of a problem.
    Here's the error log
    Process:         iPhoto [1540]
    Path:            /Applications/
    Version:         8.1.2 (8.1.2)
    Build Info:      iPhotoProject-4240000~8
    Code Type:       X86 (Native)
    Parent Process:  launchd [209]
    Date/Time:       2012-09-19 19:56:45.528 +0200
    OS Version:      Mac OS X 10.7.4 (11E53)
    Report Version:  9
    Sleep/Wake UUID: 7948ABE2-5294-4F87-B6E3-777095A2F2EE
    Interval Since Last Report:          4780 sec
    Crashes Since Last Report:           9
    Per-App Crashes Since Last Report:   9
    Anonymous UUID:                      70117D38-03EA-4F9C-B810-50B743864B9E
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/iLifeSlid eshow
      Referenced from: /Applications/
      Reason: image not found
    I've done an Apple Software Update but it didn't find an update for iPhoto.
    One thing to note is, this library was originally created on iLife 08, upgraded to '09 and it stayed on that version. It hasn't een upgraded to iLife '11.  It worked fine on my previous install of OSX Lion.  How do I recover the library without upgrading to '11 ?

  • 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.
    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):
    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.

  • Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

    Can't log in with valid password, can't boot from disk, can't access disk utility, in single user mode can't reset password as appears locked in caps mode with '?' for forward slash, can anyone help?

    Which keyboard layout you were using? German, French ... I suppose your layout is reset to the default: US and you are unable to find the "?" or "/" ...
    Please have a look into the keyboard viewer, to see how the layout of your keyboard is actually.

  • I changed my wheel group properties to no access at top disk level.  I messed up, how can I change back in single user mode "command s" as I am now in Thailand and not able to access startup disks?

    I messed up, I changed my "Wheel group" properties to No Access ( or something other than the default) at the top level of my startup disk "Macintosh HD".   Now my computer won't start up, I just get the spinning wheel of death.    I also am in Thailand right now, so I cannot go to a Genius at an apple store, nor do I have startup disks available.
    So I was hoping there was a way to change back the properties of my disk (Volume) in single user mode (via Command +s) during startup, i.e. can I do a chmod command on the Macintosh HD listing under the Volume Directory.    Or where do i fix this?   Is it fixable without startup disks, etc...
    If you could also please let me know you have an answer, I WOULD REALLY APPRECIATE IT!!! 
    thanks so much
    <Edited by Host>

    Thanks for the info on command-R, didn't know about that!!!
    Yes I changed the sharing "Wheel Group" permissions on my hard drive via Get Info.    But that's all I did.    And then most of the apps wouldn't respond with anything.    So not knowing I did something stupid, I decided to re-boot, and then nothing but the Wheel of Death at startup.
    I was trying to limit access to my computer on this network, changed my public folder settings, and then I thought why not the whole hard drive, but at that time I had no idea what the "Wheel Group" was... so I shouldn't have touched it, BUT IT DID ...... argggggg....
    I managed to go to an internet cafe & research the problem yesterday.    I used the command +s single mode to get in, and then did the necessary steps to mount the drive so I could make changes.   I basically did this:
    Boot into single-user mode (boot while holding down CMD-S)
    Follow the on-screen instructions to mount the file system as read-write (a fsck command followed by a mount command)
    Type the following: "chmod o+r /" followed by "chmod o+x /"
    Type "exit" to leave single user mode and complete the boot sequence.
    I found it at this link
    It worked... thank God!!!   Well so far so good.   
    I was going to try my own fix by chmod on the Hard drive listed under Volumes directory, but that doesn't seem to match the info under Get Info Window.    So I just used the fix above.    I probably should now go and do "Disk Utility - repair permissions", however I am a little gun shy right now, so I will probably wait until I am back in the States so I can go to an Apple store if it messes up.   Right now I'm following the "if it ain't broke, don't fix it" MOTTO...
    So Thomas I just wanted to say THANKS for replying so quickly, and I really appreciate your help!!!
    (yes I know I shouldn't have used my email addresses, but I WAS DESPERATE, but that's still no excuse)
    Hopefully maybe this thread will help someone else out in the future....
    Okay, thanks again!

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

    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' [ 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

    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\
         \mount drive\
         mount -uw
         \open 'directory access'\
         lauchctl load /System/Library/LaunchDaemons/
         \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)

  • Wipe a HD via Unix in Single User Mode?

    Is it possible to wipe a hard drive using diskutil or another method when booting up in Single User Mode? We routinely need to wipe drives and if possible, this would be the easiest.
    I suspect because the OS that boots in Single User Mode is on that same drive will make this impossible.
    Thanks in advance for your tips and comments,

    Yes, you cannot erase an OS while it's 'hosting' the erasure. Single user mode is part of Mac OS X, so it's on the hard drive, not in the firmware or anything super-low-level like that. Oh well. So... you might be able to erase the vast majority of user, application, and even OS files, but it won't be complete and won't be 'as good as' a volume-format.
    A couple alternatives come to mind (sorry if you know all this. Not trying to be pedantic or patronizing, just making sure you know your options).
    We keep host computers around just for running wipes, backups, and diagnostics that cannot run from a drive holding the booted OS. You simply restart the to-be-wiped Mac holding the 't' key, connect it via firewire, and treat it as an external hard drive.
    You could also just boot from a Mac OS X install disc and wipe from the copy of Disk Utility included on the disc. Better yet, throw a +bona fide+ copy of OS X onto a pocket hard drive, boot the victim-Mac from that (hold option while it is first starting up), and wipe the internal HD normally, now that it's not in use. You could maybe even use single user mode in the booting OS, like you'd imagined, and format from there (I'm not sure that would be faster than letting it boot normally, though, as you might have to use "dd" or some other similar low-level wipe method, as I don't think the frameworks required for Apple's cli "diskutil" are available in single user mode).
    I haven't tried to use it on a Mac, but I have a 256 MB USB flash drive with, er, ['Darn' Small Linux|] on it for diagnosing Windows boxes. It runs a script on boot which, if you don't intervene to run utilities or what-have-you, will wipe all attached hard drives and shut down. I keep it locked up for understandable reasons, but its super useful just as a time-saver, booting most machines and beginning the countdown-to-wipe in under ten seconds.
    Anyway, let us know what your goals and thoughts are.
    Cheers, Joel

  • 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: 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 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.
    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 victim="process4bbfc78">
    <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">
    <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">
    <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">
    <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">
    <databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
    <owner id="process6d44718" mode="S"/>
    <owner id="process4bbee38" mode="S"/>
    <waiter id="process4bbfc78" mode="X" requestType="wait"/>
    <databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
    <owner id="process4bbfc78" mode="S"/>
    <waiter id="process6d44388" mode="X" requestType="wait"/>
    <databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
    <owner id="process4bbfc78" mode="S"/>
    <waiter id="process6d44718" mode="X" requestType="wait"/>
    <databaselock subresource="FULL" dbid="5" dbname="unknown" id="lock4671600" mode="S">
    <owner id="process4bbfc78" mode="S"/>
    <waiter id="process4bbee38" mode="X" requestType="wait"/>
    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.

    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:
    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"
    Thanks for your help!

    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

  • Single-user mode: How to mount and access an external USB drive?

    My MacBook Pro HD is acting up. Cannot boot normally or into "safe mode". Cannot reinstall OS without wiping out the HD. Need to recover some critical files but DiskUtil First Aid and Restore options cannot successfully complete. Problem traced down to "invalid node structure" which means I either have a hardware problem or my filesystem partition directory structure is corrupted. I need to recover some files that are not backed up (timin issue with my regular backup process).
    I can boot into single-user mode, mount the root file system (/sbin/mount -uw /) and can see/navigate the rot filesystem structure via good UNIX command line. Here's what I would like to do (in single-user mode):
    1. Mount an external USB drive (250 GB already formatted as Mac OS X Extended)
    2. Copy various files and/or directories from my HD to the external USB drive (UNIX cp command)
    I realize I could go spend $$ for the Disk Warrior or Data Rescue products (or something similar) that SHOULD help me recover my HD or files, but it seems silly to do this when I can see, touch and taste them from within single-user mode....
    Comments? Suggestions?
    TIA --
    P.S. Once I've recovered my files, I'll try to reformat the HD and then reinstall the OS. And THEN go have Apple look at my machine (thank goodness for AppleCare coverage)!

    1) Boot system in single-user mode (SUM) with external HD attached.
    2) Execute the following UNIX CLI commands once SUM boot process is completed:
    # fsck -fy
    # mount -uw /
    # mkdir /Volumes/target_directory
    # mount -t hfs -w /dev/diskXXX /Volumes/target_directory
    # cp -RXv /source_directory /Volumes/target_directory
    Where XXX is the device-level name for your external HD's data partition. In my case this was /dev/disk1s2. It may take some experimentation to identify this device name if your system has multiple HD's.
    3) Verify contents were successfully copied onto the /Volumes/target_directory.
    Comments and observations:
    - Do NOT use "/" as your source directory - cp will make a second (redundant) copy of /volumes/target_directory
    - I was able to successfully copy ALL files off my HD despite the fsck command's "invalid node structure" error message with this simple procedure. YMMV, depending on the state of your HD.
    - The repeated disk0s2: I/O error warnings displayed during the SUM boot process did not seem to have a negative effect on this procedure. I also received this same error warning intermittently as I navigated the mounted filesystem did not seem to be a problem, either. Again, YMMV.
    Commercial software:
    I downloaded ProSoft Engineering's Data Rescue 3 product (trial version) before spending $99 to attempt to recover my "bad" HD's data via mounting to a good system with FW target mode. It could not successfully complete its "QuickScan" process and immediately hung on block 0 of 390M during its "Deep Scan" process. The product did seem to function properly on an operational system. ProSoft's technical support was responsive and helpful but had no answer for my "Deep Scan" error.
    I did not attempt to use Alsoft's Disk Warrior 4 product. I could not find any trial software available and was reluctant to spend $100 based upon the mixed reviews and comments on this discussion forum as well as other reviews. Alsoft does claim to address the "invalid node structure" error in their marketing materials. Hindsight being 20/20 - I saved $100 by using this simple procedure.
    Final note:
    Neither Leopard nor Snow Leopard's installation DVD could recognize the bad internal HD when trying to do a reinstall. While DiskUtil was able to "see" the bad internal drive it immediately failed when I tried to do an "erase and format". Took the system to my local Apple store and the Genius ran a tool called "SMART Utility" from Volitans Software ( SMART utility confirmed that my HD was bad so it was replaced. AppleCare pays for itself (once again!).

  • Single user mode or client install?

    Finally got my mini server ordered again (long story maybe later) I will be using it as my main computer and am wondering what is the easiest set up, boot up in single user mode or install SL client?

    Ok So maybe word it a bit different, what is the easiest way to transfer all my stuff from my MBP to have the mini set up exactly as my MBP?

Maybe you are looking for