Mountain Lion hangs during boot sequence after reinstall

I am running Mountain Lion on a late-2012 Mac Mini (the newest one at this writing), and my system got messed up after I tried to reset my primary uid to 501 (I know, first mistake) after having migrated the system from an older Mac Mini.  This worked partially, but I continued to have issues accessing some files and got tired of resetting the permissions manually. 
I tried reinstalling Mountain Lion and since then, the system fails to boot completely.  I can get as far as seeing the desktop, Finder menu, Dock, etc., but then one or more error windows pop up relating to specific resources (I think Calendar Agent was one of them, I can't remember because I then saw the spinning disk icon and the system stopped responding).  I tried restarting by turning the computer off and then on again, but continue to get similar errors after it gets almost all the way through booting.
Although I have much of my data on the hard drive backed up to an external Seagate drive on my home network, I had not been able to do a complete backup because I have many old (pre-OS X) files that contain slashes or other characters no longer allowed in filenames, and it has proven too cumbersome to update all the filenames to make it worthwhile.  Thus, I am not able to wipe the hard drive and start from scratch.
I know how to boot in Single-User mode, which does work, but don't know enough BSD/Darwin to pinpoint the source of this problem and fix it.
Any advice about how to diagnose and/or solve this problem?  I would like to be able to correct any uid and gid conflicts that may be causing this, which I believe would work, but am not sure how to do this.  I am writing this from Safari after booting in Recovery mode.
Thanks for any help with this.  - Klingon725

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not  going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Similar Messages

  • Mountain Lion Hangs on Boot when an external cloned drive is attached

    It seems that, for me at least, when I have an external drive, in this case a usb, plugged in on boot up, Mountain Lion just hangs.  This external drive is used as a clone (I use Super Duper). It can hang in one of 2 places; after inputing my password, or when trying to bring up the desktop. It is very consistent as to the hanging.  When the external drive which contains the clone is not attached, it boots fine every time.  I have no problems at all with my other external drives being plugged in at boot. They are just contain data.  Is Mountain Lion getting confused?  Anyone else experience this?

    I am stumped too. The issue is that the 'pmset -g' command does not allow changing the ExternalMedia flag.
    An observation that may be relevant to this topic is as follows: if you unmount the drive (but not physically disconnect it), sleep comes in the specified time. Upon wakeup, however, the drive is mounted again to the desktop. I've noticed this behavior with SD cards, and I assume that HDs should do the same.
    If this is the case, then it may be possible to use ControlPlane (current version is ControlPlane-1.1.4) and create an "about to sleep" situation, which triggers USB disk unmounting. Haven't tried it, but was thinking to (subsequently just gave up and eject my USB  storage manually).
    Hope this helps.
    Xen

  • P205-s6237 Hangs during boot to recovery after replace HDD

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

    I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

  • Creating my own Fusion Drive: Do I need to buy Mountain Lion from the app store to reinstall the OS? Do I lose the iLife apps?

    I just bought a Mac Mini (late 2012) with a 1TB HDD and I'm planning to install a second drive, an SSD (Samsung 840 evo) and create the Fusion Drive, and I have a couple of questions:
    1- I've read lots of articles on how to do this but I'm not sure if I have to buy Mountain Lion from the app store (to reinstall the OS after I install the second drive) since I'm not able to see it on the "Purchased" list of apps, or if I can just reinstall OS X with OS X Utilities.
    2- I read somewhere that if I make my own Fusion Drive when I reinstall OS X I will lose iLife, is this true? Or will I be able to redownload it from the store? I really don't want to lose iMovie, iPhoto and GarageBand and I'm confused about it.
    Thanks in advance for any help and information you can give me!

    Thankyou very much lllaass, that's exactly what I wanted to be sure about!

  • My mountain lion upgrade is take long after the initial installation finish it is showing increasing negative number like -50 munites remaining

    My mountain lion upgrade is take long after the initial installation finished it is showing increasing negative number like -50 munites remaining while still saying installing os x on the disk.
    I mean it starting saying time remaining about 6 munites
    Now it up to time remaing about -55 munites
    I thing something is wrong with this installation and all I did is fallow the onscreen instruction
    Thank

    You might want to just manually power down your machine and, if necessary, start the installation process anew. You're unlikely to damage anything by doing this. It may have actually installed and is just hanging when it's supposed to reboot.
    Good luck,
    Clinton

  • Ultra 5 Hangs During Boot

    My Ultra 5 hangs during boot at the following point....
    setting default ipv4 interface......
    I have tried resetting my router, unplugging the network cable, and nothing seems to work.
    John

    jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
    If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
    If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

  • K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

    Heres the problem...
    My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
    Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
    I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
    I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
    All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
    No phsysical signs of bad caps on the system board.
    I ran ran Memtest86 for 18 hours striaght with no errors.
    Ran CPU stress test with no problems.
    No IRQ,DMA,etc conflicts found.
    Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
    I have tried min install to no avail.
    Bois is retaining its settings (so bios battery is good)
    I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
    I am down to a possible cold solder joint on the system board?
    This problem started to occur about a month ago.
    If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge 
    I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
    Specs..
    Athlon 64 3500+
    2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB)  Ran in Dual config
    Geforce 6800  (BFG 6800 GT oc)
    Creative X-Fi XtremeMusic
    Antec NeoPower 480
    2 WD 36gig SATA Raptors in raid 0 (system partition)
    2 WD 120gig IDE  in raid 0 (data partition)
    Windows XP Pro
    all drivers and bios are manufacture ref and up-to-date.
    Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
    This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
    What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
    So what have we learned class?
    1. check the obvious
    2. do a complete physical inspection of your system
    3. KISS  -- keep it simple stupid

    Is this your ram:
    Quote
    Part Number: PQI3200-1024SB
    Quality Control: Comprehensively and rigorously tested
    Package: 1024MB single pack
    Organization: 128M x 64-bit
    CAS Latency: 3-4-4-8
    Test Voltage: 2.6 V
    PCB Board: 8 Layers PCB
    Heat Spreader: Mirrored Black Copper
    Speed: DDR 400 MHz (PC3200)
    Type: 184-pin DDR SDRAM
    Error Checking: Non-ECC
    Registered/Unbuffered: Unbuffered
    Warranty: Lifetime
    This is a quote from MSI web site:
    Quote
    Main Memory
      • Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
    • Supports the memory size up to 4GB 
    • Supports 2.5v DDR SDRAM DIMM 
    Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
    Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
    For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
    Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
    If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
    Post back results as there are more things one can try but lets start with the simple stuff and work up.

  • How do I download Mountain Lion onto my other iMac, after the initial install?

    I am wondering how to download Mountain Lion onto my second iMac, after the initial install.  I understand the purchase is for multiple computers, but I have completed the install on my first iMac.

    Once you’ve purchased Mountain Lion, find the installer on your Mac. It’s called Install OS X Mountain Lion.app and it should have been downloaded to your main Applications folder (/Applications).
    Right-click (or Control+click) the installer, and choose Show Package Contents from the resulting contextual menu.
    In the folder that appears, open Contents, then open Shared Support; you’ll see a disk image file called InstallESD.dmg.
    Launch Disk Utility.
    Drag the InstallESD.dmg disk image into the bottom (empty area) of Disk Utility’s sidebar (on the left).
    In Disk Utility, select InstallESD.dmg in the sidebar, and then click the Open button in the toolbar to mount the disk image’s volume in the Finder. The mounted volume is called Mac OS X Install ESD, and it also appears below InstallESD.dmg in Disk Utility.
    Select Mac OS X Install ESD in Disk Utility’s sidebar, then click the Restore button in the main part of the window.
    Drag the Mac OS X Install ESD icon into the Source field on the right (if it isn’t already there).
    Connect to your Mac the properly formatted hard drive or flash drive you want to use for your bootable Mountain Lion installer.
    In Disk Utility, find this destination drive in the left-hand sidebar and then drag it into the Destination field on the right. (If the destination drive has multiple partitions, just drag the partition you want to use as your bootable installer volume.) Warning: The next step will erase the destination drive or partition, so make sure it doesn’t contain any valuable data.
    Click Restore, and then Erase in the dialog box that appears; if prompted, enter an admin-level username and password.
    How to make a bootable Mountain Lion install drive
    https://www.macworld.com/article/1167857/how_to_make_a_bootable_mountain_lion_in stall_drive.html

  • 27" iMac Mountain Lion won't boot (Black screen) after switching to bootcamp

    Hi,
    I've been running Windows 7 in Boot Camp on Mountain Lion on my 1 month old 27" iMac without any problems. Tonight after I switched the startup partition to be boot camp the machine won't boot. I get the startup sound and the disks spin up, but the system just sits there with a Black Screen. There is no disk activity other than them spinning up.
    I've tried starting the machine while holding the option key and also command-r, but nothing is happening. I have the feeling that the bluetooth keyboard has not had the chance to connect to the system before it is hanging.
    I tried inserting a Lion OS DVD, thinking that it would at least complain and give me an option to boot back in to Mountain Lion. You can hear the DVD spin up and then go idle.
    Any suggestions on how I can recover the situation?
    Thanks in advance
    Mick

    The RAM mismatch might be the problem fix that.
    Also backup/data recover naturally, assume TimeMacine or bootable clone is corrupted and backup only files to a storage drive
    Most commonly used backup methods
    Install OS X on a external drive and boot from it.
    Create a data recovery/undelete external boot drive
    Use Disk Utility on the booted clone to Erase with middle selection (Zero) the ENTIRE internal hard drive
    Use Carbon Copy Cloner to reverse clone the clone onto the internal, copies the Recovery HD too.
    That should fix it, or else the drive or another hardware issue
    ..Step by Step to fix your Mac
    Install/upgrade RAM or storage drive in Mac's

  • Mountain Lion won't boot after restart (SSD problem?)

    Hey, I just installed ML on my OCZ Octane SSD, everything went ok, finally the setup assistant requested reboot which is what I did. However, it got stuck while rebooting and now I can only see flashing question mark icon and ML won't boot at all. The only thing I can do is to boot up in safe mode. I guess that the problem is my SSD (indilinx controller) which ML can't handle (it ran on Lion just fine). Does anyone have the same experience? Any clue how to resolve this? Thank you.

    I've confirmed with OCZ that there is a firmware issue with Mountain Lion and they are working on a fix as of July 31, 2012.
    No word from them yet, other than the official statement.
    I too had an issue with my Octane booting once after install, then never booting again. Had to to a TM restore, back on Lion till this is resolved. Kind of frustrating, but there must have been a low level system change that affected things.
    http://www.ocztechnologyforum.com/forum/showthread.php?103700-Mountain-Lion-and- OCZ-Octane-Petrol-and-Octane-S2-SSD-s

  • Hangs during boot after upgrading to Kernel 2.6.39

    I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
    The end of /var/log/everything.log is posted below.
    Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
    Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
    Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
    Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
    Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
    Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
    Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
    Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
    Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
    Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
    Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
    Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
    Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
    Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
    Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
    Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
    Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
    Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
    Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
    Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
    Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
    Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
    Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
    Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
    Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
    Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
    Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
    Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
    Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
    Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
    Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
    Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
    Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
    Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
    Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
    Any help fixing this would be greatly appreciated.

    I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
    pacman -S kernel26
    which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
    I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
    The additional logs in errors.log in the reboot that failed are as follows.
    ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
    Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
    Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    The end of kernel.log is as follows:
    Sat Jul 9 14:57:41 CEST 2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
    Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
    Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
    Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
    And this is the end of daemon.log
    Jul 26 16:27:49 O313 init: Switching to runlevel: 6
    Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
    Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
    Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
    Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
    Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
    Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
    Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
    Jul 26 16:28:39 O313 init: Entering runlevel: 3
    Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
    Last edited by TheStatsMan (2011-07-26 07:40:48)

  • Mountain Lion OS re-download it and reinstall

    I recently purchased MAC OS Mountain Lion.  After a crash and subsequent reformating of the main HD, I need to re-download it and reinstall.  From where can I do this without having to pay twice?
    It is by far the worst running OS, slow to the point of unusable, but that's another question that I will adress in a new thread.

    Once you have purchased and Installed 10.7 or later, you can re-download it using the built-in Utilities.
    In 10.6, these built-in Utilities were on the DVD with the OS Install. In 10.7 and later, a special Recovery_HD Volume should have been installed on your Hard Drive. It is difficult to erase, and should still be on your drive except for certain obscure cases where it might have been removed.
    Hold down the Alt/Option key at Startup. Be patient. After a minute or two it will draw an Icon for every bootable Volume on your Mac. If Recovery_HD shows up, choose it and proceed, and there will be options for re-installing over the Internet, provided you have a regular connection such as Ethernet or WiFi.
    If you have a new drive to install it on, that does seem to work better, but if you have erased your drive, that should work as well.
    From 10.7.4 onward, a bootable copy of the Recovery_HD is placed on your Time Machine backup Volume as well, and will show up during Alt/Option boot if the drive is attached locally and powered on.

  • Mountain Lion has long boot time between apple logo and desktop

    hi!
    i've had mountain lion since it came out and quite happy with it.
    but since about a week or 2 during bootup, after the spinning wheel stops turning and the mouse shows up in the upper left hand corner, it hangs there for about 10-15 seconds before the desktop shows up.
    during this time i can use the mouse, but all that shows is the apple logo..
    now i've made sure that no applications are to be relaunched after restart.. so the question here is: what's it busy doing during between the apple logo and the desktop? and more importantly: how can i fix it back to the way it was? it used to be a fraction of a second between the two, and now it seems to take forever!
    ps: i've a macbook pro 2010 i5 8gb (but since it worked fine before, i don't think that has anything to do with it)
    thanks in advance,
    lars

    Hi bolisaf,
    I'm having that same issue. It's annoying. It's seems to take forever, and unnecessary. When the desktop cames in the dock takes long time to show, sometimes...
    Can i ask you how long your boot time is?
    As you did not post anythong else, did you manage to work out a solution? Or there is not a solution for this?
    Thanks!
    Daniel

  • Mountain lion OSX not booting

    i installed windows 7 on my macbook pro via bootcamp. i got windows 7 up and running (which i'm currently using) but i can't boot my mountain lion os x. when i turn on computer it shows white screen for 5 secs(no apple) then goes to black and loads windows. there is a place in windows control panel where i can choose the System it boots up with but it only give me the option of booting up windows 7. I tried holding down command+R and command+option+R when booting up. but i can't get anything. please help i dont care about windows i just want my mac back the way its supossed to be!!! :/  (the osx is moutain lion 10.8 something i cant remember the other number) and ultimately i want to get rid of windows 7

    Somehow in your Windows/Boot Camp adventure you have clobbered your partition map. You should be able to boot from the network provided you have a network connection via Ethernet.
    To start reboot the computer and at the chime press and hold down COMMAND-OPTION-R keys until you see a globe near the top of the screen. This might take 15 to 20 minutes so be patient. After the globe appears wait for the Recovery HD screen to appear. From this point it's much like you were using your own Recovery HD. Do the following:
    Drive Partition and Format
    1. Select Disk Utility from the main menu and click on the Continue button.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area.  If it does not say "Verified" then the drive is failing or has failed and will need replacing.  SMART info will not be reported  on external drives. Otherwise, click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    7. Upon completion quit DU and return to the main menu.
    8. Select Reinstall OS X from the main menu and click on the Continue button. Be sure you select the correct drive on which to install OS X.

  • Arch Live CD x64 hanging during boot at "triggering uevents"

    Hello!
    I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
    I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
    Here is a picture:
    http://i.imgur.com/Y8P41nf.jpg
    I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
    Thank you!
    -- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
    (Sorry, missed that. My bad!)
    Last edited by RalphORama (2013-09-07 03:09:13)

    frank604 wrote:
    You can try nomodeset.  Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it. 
    Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
    Results:
    https://bbs.archlinux.org/viewtopic.php?id=151259
    https://bbs.archlinux.org/viewtopic.php?id=140426
    Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

Maybe you are looking for

  • SSO for prompts with Crystal and BW in BO XI 3.1 SP3

    Hello together, i have a question regarding Crystal and SSO based on a Bex Query. I created a Crystal report based on a Bex Query. Saved this to BW und published it with the BW Publisher to BOE (SAP Int. Kit is installed). In the Cmc i set the report

  • HELP disability to update iPod!

    So I clicked "Update iPod" , but then a popup showed, and said " The iPod cannot be updated. The disk could not be read from or written to. " How am I supposed to fix that?! Please help! Thank you so much

  • Delta functionality in SAP-MM   ECC 6.0

    Hi Guys, Please list the delta functionalities in ECC 6.0 of SAP-MM compared to 4.7 version. Thanks, Pallu Tillu

  • Wl server 6.0 on solaris

    downloaded wl 6.0 for solaris. keep geting disk space not enough error mesg although I have enough disk space. I exported the tmp dir env variable IATEMPDIR as instructed in the install guide. OS is sunOS 5.6, free disk space 3g and mem size 7g. Anyb

  • ColdFusion 9 in the Cloud (AWS)?

    Does anyone have any updates on where ColdFusion 9 in the Cloud stands? In October of 2009, (see link) a private beta program was announced, but I haven't seen anything since. http://www.adobe.com/aboutadobe/pressroom/pressreleases/200910/AdobeColdFu