OSX Mavericks won't boot after changing user home folder

Hi guys,
I have a clean install of Mavericks on my macbook pro 17" and have two drives in. One is hdd (in place of superdrive) and the other is ssd where OSX is installed.
I have uset the following:
If you right-click on the User in the Users & Groups system preferences, choose "Advanced Options..."
You can then change the location of the home folder
to change location of my user home folder and set it up to be on the hdd but now OSX Mavericks won't boot. I get the progress bar on boot and it just freezes no matter how long I left it.
Can anyone help me out?
Thanks!

I managed to boot after dozen tries and restored the location of the home folder to where it was at the first place.
The thing is, on my second drive I have the whole user folder with data, settings and everything else in it and would really like to use it in the Mavericks.
I guess I could just copy it over the one in the Mavericks and it should be good?
Not sure, why this is the issue now since on previous OSX releases this home folder changing thing worked without problems :/
If anyone else have the solution for this problem please do feel free to let me know!
Thanks!

Similar Messages

OSX Lion won't boot after Bootcamp installation interrupted

Hello, I started a Bootcamp installation on my OSX Lion Mac Pro. Once I realized that I could only use Windows 7, I had to hold off on the installation until I located my Windows 7 disk. I had set the Bootcamp partition size to 100 GB on a 500 GB Drive. Due to threatning weather, I shutdown the computer.
Now the OSX Lion does not boot! I have been reading much information on this topic to see about fixing the problem. I talked to Apple Support and so far it is still not working. I was able to boot using the recovery partition "Disk Utility -> First Aid -> Repair Disk". When I ran Repair Disk there were some errors reported and repaired, then OSX still not booting. I installed Lion on another drive using recovery and that works OK. I was hoping to install Lion on the original drive and still not disturb my data files like music, photos, etc. That volume with OSX is greyed out and does not mount. I am thinking that the GPT had been modified and since Windows was not installed on Bootcamp, there is no way to boot on the original drive /dev/disk2. I read about a backup GPT, so I am wondering if I can use the backup GPT to fix the boot problem.
Thoughts?
Thanks,
David

Thanks for the fast reply. Ill try this again. Did this the first time, but wouldn't boot again. I've since done a,fresh install of Lion, and it created the proper recovery partition. I didn't have this before, because I cloned my old drive, when I upgraded to an SSD drive. Didn't know about the recover partition. Ill try again, and see if I can get it to work.
Just need to figure out the driver situation, with my Nvidia Quadro Mac video. Not worth trying again, if I have to use default generic video drivers.

Solaris 10 won't boot after changing the CPU

Hi. I was running Solaris on my Intel-based desktop machine. It was running fine. One day I upgraded my CPU and since then Solaris won't start. Immediately after it tries to load itself, it displays something on the screen really fast ( something with "dumping" in it) and then reboots.
I runned Solaris in fail safe but I cannot run reboot -r for example. It says that reboot has wrong parameter or something. And I don't know what else to do.
Please help.
Thanks.
P.S. I'm not 100% sure that the problem is related to changing the CPU. Maybe I configured something wrong when working in Solaris prior to the hardware change. But I think that's unlikely because I'm usually pay attention when changing settings in Solaris and don't dive in dark waters.

Right after I wrote my previous post I looked again at the web page Darren recommended and I figured out what it was all about. I had troubles understanding the procedure in the first place because I wasn't familiar with mounting partitions and I didn't know what /a refers to. On another site I found out about the command that saved me: mount /dev/dsk/c0d0s0 /a A bit later I found out that when starting Solaris in single user mode (failsafe for example) the partition is mounted automatically to /a when you choose to update the boot archives.
(As a tip for beginners like me, once in single user mode use the Delete key instead of Backspace :P ).
So, the procedure explained on that site is:
In case of a hardware mismatch, use one of the two methods that follow:
Method 1 (Recommended)
1.Move path_to_inst          ex: # mv /a/etc/path_to_inst /a/etc/ORIGINAL_PATH_TO_INST      2.Remove all old device links          ex: # rm /a/dev/rdsk/c* ; rm /a/dev/dsk/c* ; rm /a/dev/rmt/*   3. Rebuild path_to_inst and devices          ex: # devfsadm -r /a -p /a/etc/path_to_inst Note: If you are worried about the bootblock being corrupt, reinstall it.       # cd /a/usr/platform/`uname -i`/lib/fs/ufs
      # /a/usr/sbin/installboot bootblk /dev/rdsk/<c#t#d#s0> 4.Unmount the root slice and reboot          ex: # umount /a ; init 6Method 2
From the OK> prompt, do a 'boot -ar'.
Accept the default for all questions except the path_to_inst file.
When you get to that one, specify /dev/null.
It should then prompt you if you want to create a new /etc/path_to_inst file from scratch. Say yes.
So I tried method 1, but no success. First of all I noticed that the devfsadm command didn't create the /a/etc/path_to_inst file. As many times I have tried it (even after I read a lot more on the Internet regarding these commands) I never made it to work. Somewhere on the net somebody asked about the "-p" argument that is not explained in the man pages of the command and the answer was that it specifies the path to the path_to_inst file wich makes sense but doesn't work. Somewhere else it was suggested that the "-p" argument to be ignored and the new path_to_inst file to be looked under /etc ; this was not the case for me.
I tried method 1 many times with small variations, within the virtual or the real machine, but it never worked.
So I tried method 2 as well, but no luck either. First of all, for all other beginners facing this kind of problem, on a x86 machine there is no OK> prompt; it's a SPARC "feature". But "boot -r" commands or alike can be issued using "reboot -- -r".
So I have tried all the variations I could find on the internet -r,-a,-ra,-rav, but this command didn't work either. I always got the message
bootadm: Cannot update menu. Cannot reboot with requested arguments.I never quite figured what "menu" is all about. My guess was that it refered to the grub menu/commands for booting and that it couldn't change those. So I
read on the net a few things about the booting commands in GRUB bootloader and I tried a few variation but they never worked. Indeed the changes I did to the commands were not saved, as the bootadm erros would indicate. Am I wrong?
After reading about the GRUB commands I got a little bit more familiar to what goes on at booting time and later I found an article in the Sun Documentation called x86: How to Boot the Failsafe Archive to Forcibly Update a Corrupt Boot Archive ( http://docs.sun.com/app/docs/doc/819-2379/6n4m1vlfi?a=view ). There I so this command
To forcibly update the corrupt boot archive, type:
     # bootadm update-archive -f -R /a
Unmount the device.
     # umount /a
Reboot the system.
     # init 6I have tried it, looked like it is searching through the hard-disk, after a while finished and I rebooted but with no effect.
This is where I am now.
Any idea of why devfsadm would not create the path_to_inst file?
Any ideas of what to do else or where I could have got it wrong?
Thank you.

Macbook Pro 13" won't boot after changing ram.

So i ordered a 4Gb corsair ram for my Early 2011 MBP 13" and tried installing the same. I already had 2 x 2Gb sticks on it. I removed one 2Gb stick and added the 4Gb stick but now my systems wont boot at all. No sound, it won't even charge. i tried putting in the old ram and boot, but even that isnt happening now. Is there anything i could be doing wrong?

Sorry for a late update.
Went to the apple store and they fixed it for me in under 10 minutes. Said " It had nothing to do with the RAM, some issue with the battery".
Now i have 6 gigs of ram on my MBP .

Mac won't boot after updating to OSX 10.6.4

I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
1) boot dead machine in Target Disk Mode (iMac)
2) boot good machine off Snow Leopard disk (MacBook)
3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
4) ran software updates
5) shut down MacBook then shut down iMac
6) rebooted iMac- all was good
I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
Thanks everyone for your help!

Password not accepted after changing user name

I changed my user name in the system preferences -> user and groups -> advanced options.I did not change my password tho.
I then put my macbook to sleep. When I wake it, it won't accept my old password!
I did some searching online, and found solutions which work for previous versions of Mountain Lion or Lion here. OS X: Password may not be accepted after changing user's full name
However I believe I am using a 10.9.3 (I may have updated to Mavericks, I am sorry I forgot), so none of these tricks work for me.
Can someone help me out? much thanks!

Hello emmyraye,
Thanks for using Apple Support Communities.
Please reset your password by following the directions in the user tip linked to below.
Reset the user password in OS X Lion, Mountain Lion and Mavericks
https://discussions.apple.com/docs/DOC-4101
Take care,
Alex H.

Macbook pro won't boot after installing update 10.9.3

macbook pro won't boot after installing update 10.9.3

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

Mac won't boot after power chord became unplugged accidently.

Mac won't boot after power chord became unplugged accidently.
I have a Mac Mini running very latest version of OSX. I was making a recording with QuickTime; when I needed to plug in a USB recording device into the back of the Mac Mini, as I pulled the Mac off my shelf to do this, the power cable came out and the Mac lost power.
I plugged it back in and powered up the Mac. I get the grey screen with Apple logo and the spinning grey wheel; then it goes to a blue screen (as usual) and I get the "starting OSX..." progress bar. When the progress bar finishes, I'm left with a blue screen only, no dock, no apple icon at top left, nothing across the top, no nothing.
So far, I've booted from the original disc and repaired the permissions as well as the disc, then re-booted, but same old blue screen.
I have another iMac G5 machine, so is there any way I can at least retrieve the important HD files from the Mac Mini to my G5, before throwing the broken Mac Mini away?
Can anyone advise please?

Hi, Nigel.
Not to differ with my colleagues here, but there's an important question that wasn't asked.
1. You wrote: "So far, I've booted from the original disc and repaired the permissions as well as the disc, then re-booted, but same old blue screen."Did Disk Utility report any errors it could not fix when you ran Repair Disk? I suggest you run the procedure specified in my "Resolving Disk, Permission, and Cache Corruption" FAQ. Perform the steps therein in the order specified.
2. You may also want to run the Apple Hardware Test that came with your Mini to be sure nothing shorted when the power cable was removed from the computer. I've seen it happen, hence I usually recommend removing the power cable at the wall before disconnecting the power cable from the computer. See my "Apple Hardware Test" FAQ.
3. Repair Disk gives your Mini a clean bill of health, the blue screen may be the result of some Startup or Login item that was corrupted due to the sudden power outage. My "Troubleshooting Startup and Login Items" FAQ can help you pin that down if such an item is causing the problem and may help you avoid and Archive and Install.
4. If you elect to go the Archive and Install route, see my "General advice on performing an Archive and Install" FAQ for some important tips on this process.
5. As FYI, this is the kind of problem that makes one glad they've implemented a comprehensive backup and recovery solution. For advice on the backup and recovery solution I employ, see my "Backup and Recovery" FAQ. Computing without a comprehensive backup and recovery solution is like driving without auto insurance.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

Mac OS won't boot after 2007-009 1.1 update

Hi all
Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
Any help would be really appreciated.
Thanks

I have been booting up for...2.45 hours now
Good grief!
Here are a few hints about what you should have done:
There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
If you are updating Safari (or just have):
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692

Computer won't boot after installing latest iTunes update

Won't boot after the apple screen. Turns black and disk stops Help! Was running Mavericks.

Hi Neodoc,
Welcome to the Apple Support Communities! I understand that your MacBook Pro will not boot past the Apple logo. There may be a few troubleshooting steps I would recommend for this situation. The following article outlines the steps to perform to get this resolved for you.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
I hope this helps,
-Joe

My Mac Pro won't boot after installing the latest update

Im running the latest OSX on my mac and recenty did a small updated that i believe contain a few security thing and bug fixs but when restarting the machine after the update it would not boot again after the apple logo has appeard apple script is displayed on the screen contain what i think is boot script failing to run. I have been able to boot the system in safe mode. does anyone have and solution for this as i realy don't want to reinstall the OS
Thanks

The most common cause for "Won't boot after software Update" is Directory Damage that existed before the Update, but was made worse by adding files during the Update.
The most common cure for that Directory Damage problem is to boot in Safe Mode, which takes five minutes to repair the disk, then comes up demanding your username and password, even if you normally auto-login.
Rarely, third-party add-ons are made obsolete by an update. In this case, booting in Safe Mode (with few Apple extensions and NO third-party extensions loaded) works fine, even if normal mode does not work.
Have you tried normal mode again after your Safe Boot?

Mac mini 2009 mavericks won't boot. Blank display no logo,etc. Tried all keyboard boot functions, no help. replaced RAM w/known good. No help. Removed HD mounted in external enclosure and ran permissions and repair. No help. Upgraded HD to Yosemite a

Mac mini 2009 Mavericks won't boot. Chimes and power light comes on. USB ports have power. Blank display no logo,etc. Tried all keyboard boot functions, no help. Replaced RAM w/known good. No help. Removed HD and mounted in external enclosure and ran permissions and repair. No help. Upgraded HD to Yosemite and was able to boot another mini from HD mounted in external enclosure, reinstalled HD still no boot. Any ideas on how to proceed appreciated.

- Make an appointment at the Genius Bar of an Apple store. You have a hardware problem.
Apple Retail Store - Genius Bar

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear.

MacBook Pro won't boot after trying to install 10.7.3 update. Start up stalls at Apple logo and spinning gear. Computer won't even start in safe mode.

My daughter's MacBook Pro was doing exactly the same thing. I don't know if it had anything to do with the latest update. She called me about a week ago saying that her MacBook began running slower by the day . She then called me Friday and told me that it wouldn't get past the gray screen and the gear just kept on spinning. I did everything I could over the phone including Safe mode which it wouldn't go into and thought maybe it was the hard drive. She took it to the Apple store. Originally, they also thought it was the hard drive. It ended up being a corrupted operating system (Lion). Apple genius simply re-installed Lion and she's back up and running. Good thing she backed up right before it crapped out. She'll be restoring everything tonight. Don't know if re-installing Lion will help your situation, but it did the trick for my daughter.

[SOLVED] Arch won't boot after I created a separate /var parition

Arch won't boot after I created a separate /var parition on an existing installation.And let me confess: it was maybe stupid trying to do it on an existing install.
I edited the fstab correctly, copied the files using rsync preserving permissions. Then I kept a backup of /var using tar. Then went on to delete everything under /var, ie /var/*, the /var folder is still there. All this I did from a live CD. After that I booted into my arch linux. Here I get messages about systemd successfully finishing fsck on each of my partitions, then the screen starts blinking. And there is no more output. Pressing Ctrl+Alt+Delete causes systemd to stop its services and reboot.
Having realized I had borked my system, I removed the /var line from fstab and restored /var from the tar file I made earlier. Again I did this from a live cd. Rebooted into my arch system, and again similar issues, namely that after fsck and messages informing a few services had started, the screen keeps blinking.
The live cd I used for reorganizing my partitions was elementary OS freya. They have GParted in there. I also have an arch install iso lying aroung from May 2013. If necessary, I can download the latest version. I am currently typing from a Windows installation I dual boot from.
I don't know how to extract any boot logs as I am locked out of the system. Here is my fstab in any case:
# Filesystem information
# /dev/sda5 LABEL=fs_root
UUID=b9d739cf-fd8c-46dd-a919-bd827dc47c66 / ext4 rw,noatime,data=ordered 0 1
# /dev/sda9 LABEL=fs_var
UUID=ec0f7a49-dccd-43ab-8651-9aa3fdb41cc7 /var ext4 rw,noatime,data=ordered 0 2
# /dev/sda2 LABEL=fs_boot
UUID=0e8ab31a-3bda-4b85-a901-a36f21b1583d /boot ext2 rw,noatime 0 2
# /dev/sda6 LABEL=fs_home
UUID=d9e63c47-274e-447f-ad01-0d97afe0fd34 /home ext4 rw,noatime,data=ordered 0 2
# /dev/sda7 LABEL=fs_swap
UUID=7301227c-e9f3-41b8-9d0f-4cf3c159491c none swap defaults 0 0
# /dev/sda3 LABEL=fs_win
UUID=12B639D1B639B5D7 /fs_win ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,nofail,noauto,x-systemd.automount 0 0
# /dev/sda3 LABEL=fs_share
UUID=D272269772268079 /fs_share ntfs uid=1000,gid=1000,dmask=027,fmask=137,showexec,noauto,nofail,x-systemd.automount 0 0
I would greatly appreciate any help.
Last edited by richcocoa (2015-05-03 18:04:44)

Have you moved everything from /var to /new_var (i named it for learning purpose)? You shoud copy content from /var but not on the fly but booting from arch iso cd, and than you shoud mount your / into arch-chroot environement, mount all of your mount points and than copy content from default /var to new /var. The copying should be done with this
cp -rax
and you can add -v switch to verbose output. I have my own /var moved the same way.
The simples way is:
-boot the arch iso cd
-mount all of your mount point (i created here in this step /new_var to move /var to a new place, and this /new_var i put in /etc/fstab as /var later)
-copy /var to /new_var with -rax or -vrax (recursive, archive, this filesystem or verbose, recursive, archive, this filesystem switches)
-umount all of it
-reboot.
Last edited by firekage (2015-05-02 07:49:20)

My MacAir 1st gen. won't boot after latest OS X Lion update.

My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen. Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
Have you done a PRAM reset, CMD+Option+p+r...
http://support.apple.com/kb/HT1379
In fact, do 3 in a row, takes a bit of time.

OSX Mavericks won't boot after changing user home folder

Similar Messages

Maybe you are looking for