Fresh install of 10.5 hangs at boot after 10.5.8 update

I'm troubleshooting a MacBook that hangs at start-up after installation of the 10.5.8 complete update. I've run Disk Utility (no errors), fsck (fixed a single error), and repair permissions (oddly, repaired a few on this fresh install). I've booted into verbose mode, and it appears that there's an infinite loop of:
localhost DirectoryService[#]: Launced version 5.8.1 (v514.28)
localhost ReportCrash[#]: Saved crashreport to /Library/Logs/CrashReporter/DirectoryService. . . .(it goes on, but it's just date info).
Again, this is a fresh installation of 10.5. The only programs that have been updated are those updated through Apple Update. I did have problems installing the 10.5.8 update through the Update utility because "the package contents could not be verified," but the update installed fine after I downloaded it from Apple's site.
Any ideas?

Similar Messages

Kernel panic on first boot after 10.6.8 update

Hi,
Here are the fact:
1) I systematically get a kernel panic on first boot after an attempt to update to 10.6.8 (was able to revert to 10.6.7 using Time Machine; now I'm running my tests on a clone). While doing the update, there are NO USB connexion to my laptop, nor ethernet connexion. Only the power cable.
2) I DO NOT use the software Hands Off which is known to cause such an issue
3) I've tested this on two different hard drive (with a clone of my system)
4) I disabled all third app on startup just to be sure this wasn't a conflict problem
5) After a kernel panic, I'm always able to boot in safe mode
6) I did try both the normal update and the combo update (same result)
Now I'm kinda stuck. The next test I'm thinking performing is to update while in safe mode. But I don't know if it will help.
And yes, my permissions are all fine. Any idea how to troubleshoot this? I believe I need to be in 10.6.8 in order to update to Lion?
Many thanks in advance!
Parneix

Hi,
Sorry about that. Below you'll find the log of my latest kernel panic.
I did follow instructions suggested by user "ds store". The only "kext" file that I've got (by running the commands in the Terminal) was related to the software LittleSnitch. I downloaded it again in order to run the uninstaller. I'll try again to update to 10.6.8 under those conditions and report here.
Mon Jul 4 11:00:32 2011
panic(cpu 0 caller 0x2abf6a): Kernel trap at 0x57cf1b5a, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000000, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x00000000, EBX: 0x096b8100, ECX: 0x01500000, EDX: 0x00000001
CR2: 0x00000000, EBP: 0x57dd3df8, ESI: 0x00000001, EDI: 0x096b8100
EFL: 0x00010206, EIP: 0x57cf1b5a, CS: 0x00000008, DS: 0x00000010
Error code: 0x00000000
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x57dd3be8 : 0x21b837 (0x5dd7fc 0x57dd3c1c 0x223ce1 0x0)
0x57dd3c38 : 0x2abf6a (0x59e3d0 0x57cf1b5a 0xe 0x59e59a)
0x57dd3d18 : 0x2a1a78 (0x57dd3d30 0x10001 0x57dd3df8 0x57cf1b5a)
0x57dd3d28 : 0x57cf1b5a (0xe 0x9790048 0x9790010 0x10)
0x57dd3df8 : 0x57cf1951 (0x96b8100 0x57cf1f64 0x57cf1f5c 0x7d22fc0)
0x57dd3e18 : 0x543f60 (0x96b8100 0x6c03f00 0x1 0x506b76)
0x57dd3e78 : 0x542137 (0x6c03f00 0x96b8100 0x7d28a00 0x9791da0)
0x57dd3f28 : 0x5426e9 (0x6c03f00 0x7d20340 0x0 0x516766)
0x57dd3f78 : 0x5443d5 (0x6c03f00 0x8 0x57dd3fac 0x1)
0x57dd3fc8 : 0x2a179c (0x9773aa0 0x0 0x2a17ab 0x7c1b000)
      Kernel Extensions in backtrace (with dependencies):
         com.apple.iokit.CHUDKernLib(3)@0x57cf0000->0x57cf3fff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
10K540
Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacBookPro5,5 (Mac-F2268AC8)
System uptime in nanoseconds: 54454580752
unloaded kexts:
(none)
loaded kexts:
com.Cycling74.driver.Soundflower          1.5.1 - last loaded 54075922238
com.Logitech.Control Center.HID Driver          3.2.0
at.obdev.nke.LittleSnitch          2.2.05
com.apple.Dont_Steal_Mac_OS_X          7.0.0
com.apple.iokit.CHUDUtils          3
com.apple.driver.AppleIntelYonahProfile          14
com.apple.driver.AppleMikeyHIDDriver          1.2.0
com.apple.iokit.CHUDProf          3
com.apple.driver.AppleUpstreamUserClient          3.5.7
com.apple.driver.AppleIntelPenrynProfile          17
com.apple.driver.AppleMikeyDriver          2.0.5f13
com.apple.driver.AppleHDA          2.0.5f13
com.apple.driver.AppleGraphicsControl          2.10.6
com.apple.driver.AppleMCCSControl          1.0.20
com.apple.driver.AppleIntelNehalemProfile          11
com.apple.driver.AirPortBrcm43xx          423.91.27
com.apple.driver.AudioIPCDriver          1.1.6
com.apple.nvenet          2.0.17
com.apple.driver.AppleBacklight          170.0.46
com.apple.kext.AppleSMCLMU          1.5.2d10
com.apple.driver.SMCMotionSensor          3.0.1d2
com.apple.driver.AppleIntelMeromProfile          19
com.apple.driver.AirPortBrcm43224          428.42.4
com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
com.apple.driver.AppleLPC          1.5.1
com.apple.GeForce          6.3.6
com.apple.filesystems.autofs          2.1.0
com.apple.driver.AppleUSBTCButtons          201.6
com.apple.driver.AppleUSBTCKeyEventDriver          201.6
com.apple.driver.AppleUSBTCKeyboard          201.6
com.apple.driver.AppleIRController          303.8
com.apple.driver.AppleUSBCardReader          2.6.1
com.apple.iokit.SCSITaskUserClient          2.6.8
com.apple.iokit.IOAHCIBlockStorage          1.6.4
com.apple.BootCache          31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
com.apple.driver.AppleUSBHub          4.2.4
com.apple.driver.AppleFWOHCI          4.7.3
com.apple.driver.AppleEFINVRAM          1.4.0
com.apple.driver.AppleAHCIPort          2.1.7
com.apple.driver.AppleUSBEHCI          4.2.4
com.apple.driver.AppleUSBOHCI          4.2.0
com.apple.driver.AppleHPET          1.5
com.apple.driver.AppleSmartBatteryManager          160.0.0
com.apple.driver.AppleRTC          1.3.1
com.apple.driver.AppleACPIButtons          1.3.6
com.apple.driver.AppleSMBIOS          1.7
com.apple.driver.AppleACPIEC          1.3.6
com.apple.driver.AppleAPIC          1.4
com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
com.apple.security.sandbox          1
com.apple.security.quarantine          0
com.apple.nke.applicationfirewall          2.1.12
com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
com.apple.iokit.KLog          2.4.5
com.apple.iokit.IOSurface          74.2
com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
com.apple.iokit.IOSerialFamily          10.0.3
com.apple.driver.AppleHDAHardwareConfigDriver          2.0.5f13
com.apple.iokit.CHUDKernLib          3
com.apple.driver.DspFuncLib          2.0.5f13
com.apple.driver.AppleSMBusController          1.0.10d0
com.apple.iokit.IOAudioFamily          1.8.3fc2
com.apple.kext.OSvKernDSPLib          1.3
com.apple.driver.AppleHDAController          2.0.5f13
com.apple.iokit.IOHDAFamily          2.0.5f13
com.apple.driver.AppleBacklightExpert          1.0.1
com.apple.nvidia.nv50hal          6.3.6
com.apple.iokit.IOFireWireIP          2.0.3
com.apple.iokit.IO80211Family          320.1
com.apple.iokit.IONetworkingFamily          1.10
com.apple.driver.NVSMU          2.2.7
com.apple.driver.AppleSMC          3.1.0d5
com.apple.driver.IOPlatformPluginFamily          4.7.0a1
com.apple.driver.AppleSMBusPCI          1.0.10d0
com.apple.iokit.AppleProfileFamily          41
com.apple.NVDAResman          6.3.6
com.apple.iokit.IONDRVSupport          2.2
com.apple.iokit.IOGraphicsFamily          2.2
com.apple.driver.AppleUSBMultitouch          207.7
com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
com.apple.iokit.IOBluetoothFamily          2.4.5f3
com.apple.iokit.IOUSBHIDDriver          4.2.0
com.apple.iokit.IOUSBMassStorageClass          2.6.7
com.apple.iokit.IOSCSIBlockCommandsDevice          2.6.8
com.apple.driver.AppleUSBMergeNub          4.2.4
com.apple.driver.AppleUSBComposite          3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
com.apple.iokit.IOBDStorageFamily          1.6
com.apple.iokit.IODVDStorageFamily          1.6
com.apple.iokit.IOCDStorageFamily          1.6.1
com.apple.driver.XsanFilter          402.1
com.apple.iokit.IOAHCISerialATAPI          1.2.6
com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
com.apple.driver.AppleFileSystemDriver          2.0
com.apple.iokit.IOUSBUserClient          4.2.4
com.apple.iokit.IOFireWireFamily          4.2.6
com.apple.iokit.IOAHCIFamily          2.0.6
com.apple.iokit.IOUSBFamily          4.2.4
com.apple.driver.AppleEFIRuntime          1.4.0
com.apple.iokit.IOHIDFamily          1.6.6
com.apple.iokit.IOSMBusFamily          1.1
com.apple.security.TMSafetyNet          6
com.apple.kext.AppleMatch          1.0.0d1
com.apple.driver.DiskImages          289.1
com.apple.iokit.IOStorageFamily          1.6.3
com.apple.driver.AppleACPIPlatform          1.3.6
com.apple.iokit.IOPCIFamily          2.6.5
com.apple.iokit.IOACPIFamily          1.3.0

[Solved] UEFI. System hangs on boot after successfully activating swap

Alright.
Unnecessary Background:
I've been using Arch for years. I just bought a stupidly good computer with a bunch of specs that I don't think are relevant, except for the fact that I am using an X99-pro. It has RAID support, but I am not using that currently. I bought all the parts and finished constructing it this morning (I live in Japan, so that was a while ago). Normally, I have no problems with installation; however, I wanted to do this one UEFI mode. After booting into the live disk, I checked to make sure everything was working as it should. Arch recognized my graphics card, most of my ram (one of the cards is a bit finicky for some reason), my SSD and HDD, along with the built-in WiFi (although it is an annoying broadcom one, so I need to install the driver separately later). Now, there are plenty of sources of error in here:
Problem:
I got through the arch installation and tried gummiboot. It would hang every time after successfully activating swap. I tried grub, too, but had the same problem. Because gummiboot is much less cumbersome, I switched back to that. Interestingly, systemd will sometimes recognize my drive twice before activating swap, and if I edit my fstab to ignore the swap completely, it hangs on the next step with is mounting the boot partition. I would like to point out that because I am not able to successfully boot my system, I cannot provide the exact messages for you guys, which may pose a problem.
Solutions I have tried:
1. Chrooting / mkinitcpio -p linux
2. modifying fstab / removing swap from it completely
3. fresh re-install
Sources of error:
1. Construction. Everything seems appropriate on the live usb, but maybe there is a problem in which ports I used for the SSD and HDD
2. UEFI. It could be that UEFI just doesn't like mounting multiple things and freezes up when put on the spot.
3. Legacy. It could be that this is not a problem with UEFI or my construction, but something I missed in the installation.
Additional info:
Partitioning scheme:
sda1: ~500MiB boot / EFI partition
sda2: ~4G swap
sda3: ~110G /
sdb: ~2T, untouched (for storage later)
I apologize for any typos and hope it was readable. I am super exhausted and going to take a nap. I'll check back in on this in the morning.
Last edited by Leios (2015-02-08 00:16:27)

Please post the output of:
# gdisk -l /dev/sda
lsblk -f
And the contents of your gummiboot loader.conf and arch.conf (or whatever you've called it).
Post the output of the commands after you have mounted all your partitions and (arch-)chroot'd into your system.
You can use wgetpaste to post the outputs, as described by @ewaller here:
https://bbs.archlinux.org/viewtopic.php … 8#p1500528
Alternatively, pipe the command output to a text file and export it (using a live distribution or a USB stick).
You should remove swap from your fstab -- systemd mounts it automatically anyway.

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)

Fresh installed FF-7.0.1 stop crashing after hareware swap??

A fresh install FF-7.0.1 crashed like every visit to any page. But after a System swap from a Celeron to an Athlon-xp, it's solid like a rock. The IE-8 on The Celeron 1.8 was working perfectly. Except for the Motherboard and the Processor, everything else the same, the DDRs, the hard drive, Etc.

A fresh install FF-7.0.1 crashed like every visit to any page. But after a System swap from a Celeron to an Athlon-xp, it's solid like a rock. The IE-8 on The Celeron 1.8 was working perfectly. Except for the Motherboard and the Processor, everything else the same, the DDRs, the hard drive, Etc.

Hangs on boot after lion upgrade

I've upgraded to Lion and since upgrading my macbook pro hangs when booting about 4 out of 10 times. I get to the desktop and then get a never-ending spinning color wheel.
2.8 Gb core 2 duo
8 GB ram
Summer 2009 model

When you boot in single user or safe mode, all third party software is prevented from started. So it is possbile one of your third party party applications that are starting at boot is not compatable with the new RAM. I would try turning it all off and then test them all each in turn.
Allan

Imac won't boot after 10.6.8 update

Not sure where to start with this...
Just tried to boot after the latest 10.6.8 update and have the grey screen with the spinning disk.

I would suggest that you do the following as a start:
Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If the drive is OK then download the Mac OS X 10.6.8 Update Combo installer and reinstall the update. See if that resolves your problem.
If the above does not fix the problem then you will need to reinstall Snow Leopard:
Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.

Won't boot after 10.5.2 update (external HDD)

it boots fine with 10.5 from my external USB HDD
after 10.5.2 update, it hangs at the apple logo grey screen with gear spinning
PS: boot from external USB HDD

I have had the same problem and have so far (despite the autofsd suggestion) had no success fixing it. This is on a completely clean installation (which booted fine) with the latest updates including 10.5.2 (which doesn't boot at all).
I have installed Mac OS X on external (USB and Firewire) drives before without any problem and I wanted a development environment for some work I am doing on Aperture 2 (so I need 10.5.2) without running the risk of messing with my existing installation of Aperture 1.5.
The drive itself is the very drive the machine came with so that shouldn't be an issue, although it is of course, now in an external (powered) enclosure.
Playing with the autofsd plist (and also renaming /usr/libexec/autofsd) has had no effect.
I'll try the ps suggestion and see what that turns up.

Cant find Mac OS boot after win 8.1 update.

Hi there,
Ive had a look around the net for a possible solution but no luck so far.
I recently installed Win 8.1 on a partition. My Macbook pro is a model A1398.
I was trying to create a shared partition. From Mac OS I made the new shared partition ex-FAT. I went into Win 8.1 reformatted it (cant remember if I left it at ex-FAT). In the process of restarting Win 8.1 was nice enough to download some updates and restarted itself.
From then on it doesnt see the Mac OS boot any more. Doesnt even boot into Windows! It has start up errors. I tried the command + R option and I cant do the following either:
1. I cant seem to do anything useful (unless Im missing something) with Disk Utility. Diagnostics show that the Mac OS X install is fine.
2. Cant re-install because it cant see any boot disk options to select from.
Right now Im screwed. Cant do anything with my "fancy pants" macbook pro. Any help would me much appreciated!
Cheers.

Had to revert to wiping everything out and starting from scratch. Didnt have a back up so thats the only way. Set the partition to GUID and Mac OS journalled.
Command + Option + P + R and then set it all to just one partition. Then re-install mac OS.
If the above start up option didnt work, try the command R then try the above option again.
Hoe this helps someone.

HELP Mac Mini will not boot after 10.5.1 update

After I tried installing 10.5.1 I received a warning message that the update will not be installed because of an error and I should contact the vendor. After that the Mini tries to reboot. It keeps repeating the process over and over. I have tried to do safe boot mode by manually turning off the computer and then restarting while holding shift, but nothing happens. Can anybody help?

BBlades wrote:
I think the problem might be with the external HDD I am running with this machine. I am reinstalling everything now from my time machine backup. I just added this hard drive the other night and it is loud as all **** and I believe it is why my machine has crashed. Before I added the drive, my system was running pretty good. It is a Calvary 160gb drive. I think I am going to have to send this POS back to newegg and get myself another Lacie drive, because my other Lacie is running smoothly.
I'd go with the LaCie. I got two from Amazon, 320 and 500 and both are quiet, have 800MHz FW and I have had no problems with either of them. The new one also has a 3-position switch - Off/Auto/On which allows it to sleep when not being accessed when in Auto.
I suspect that your external HD was the problem all along.

No BOOT after 10.8.3 UPDATE

Hi after updating to 10.8.3 i'm stucked in the grey boot screen.
Booting in verbose mode shows me
disk0s2 : media is not present
in single user mode if i launch fsck -yf it shows me:
Failed to issue COM RESET succesfully after 3 attempts. Failing..
disk0s2: no suck device
update/reload mount for / failed: Device not configured
The only way to make the system active is to boot with TARGET option and select the disk.then it boots properly..
any help how to fix that s°*T of update?
Thank you

Hold Command and R keys while your Mac is starting to start in Recovery HD. Then, open Disk Utility, select your OS X partition on the sidebar and verify the disk. Is it OK? If not, repair it.
If it doesn't show any problem, the update damaged the operating system. Close Disk Utility and reinstall OS X. You won't lose anything you had stored before updating.
Sometimes, problems like this happen after a OS X update, and we don't know exactly their reasons. Maybe a third-party extension, maybe a corrupted OS X package, maybe a hard disk failure. To prevent problems like yours, I recommend to install a maintenance update as OS X 10.8.3 downloading the Combo version from the Apple webpage. This version gives less problems than the version you download from the App Store and it can be used to update all your Macs downloading that update once

HT6114 MAC Air slow to boot after 10.9.2 update.

I have a 2011 MAC Air. After the 10.9.2 upgrade my laptop takes about 20 minutes to boot from power off. Once started it works fine, it is just extremely slow to boot. Prior to the update I could boot in about 10 seconds. Any thoughts how to resolve this issue?

Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
    b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
     Boot to the Recovery HD: Restart the computer and after the chime press and hold down the
     COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the
     computer and after the chime press and hold down the OPTION key until the boot manager
     screen appears. Select the Recovery HD and click on the downward pointing arrow button.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
     Reinstall the 10.9.2 update: OS X Mavericks 10.9.2 Update (Combo).
4. Reinstall Lion/Mountain Lion, Mavericks: Reboot from the Recovery HD. Select Reinstall Lion/Mountain Lion, Mavericks from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Reinstall the 10.9.2 update: OS X Mavericks 10.9.2 Update (Combo).

Mac Pro new update won't boot after 10.8.2 Update 1.0

It just stays on the apple screen during boot after entering pw for account.
Its been over 5 min that it just stays in that screen. Anyone else seeing this after doing 10.8.2 Supplemental Update 1.0?

Reinstalling Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion: Select Reinstall Lion/Mountain Lion and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.

Hangs during boot after Security Update 2007-006 Installed

Hello out there,
As I said in the Subject, I installed Security Update 2007-006 on my MacBook Pro running OSX 10.4.9 and now it wont boot. just from playing around with it in single user mode I think it hangs sometime when configd is starting, but I don't know exactly when or why it's not booting correctly.
Any suggestions on what to do? Any help would be greatly appreciated.
MacBook Pro Core Duo Mac OS X (10.4.9)
Mac OS X (10.4.9)

The A&I, saving user and network settings, installation, just moves all current OS required stuff into a previous system folder and installs all new OS stuff. Afterwards, you'll have to bring it up to the latest version. It doesn't wipe the HD. If that doesn't work, then you can try via the other computer. If neither work, then you'll be forced to do an erase and install. That's why a bootable backup/clone is so valuable.

[SOLVED] Fresh install, Two failures and hang

Solution: Needed to mount my boot partition (EF filesystem) to /boot/efi instead of /boot. Using rEFInd
Hi, so I've read the beginners guide inside and out and I'm having the most difficult time installing arch.
I've probably wiped it at least a dozen times and everything seems like it is going to start up and I get a few failures on startup which results in a hang afterwards
1)
[FAILED] Failed to start Create Volatile Files and Directories.
see 'systemctl status systemd-tmpfiles-setup.service' for details.
2) (this one cycles 6 times before hang)
[FAILED] Failed to start login service.
See 'systemctl statuse systemd-logind.service' for details.
x6
Then I get
[OK] Reached Target Multi-User System.
[OK] Reached target graphical interface.
then the hang where I can't do anything but hold down my power button.
I tried restarting the system with my liveCD (usb) and mounting up my directories and looking into the systemd files but they just say they load ok and there aren't any issues.
I've scoured google and really can't find anything to fix this issue. Any advice would be welcome for sure!
I know I can install Arch on this laptop because I was successful once. But then I wiped it to try out OpenSUSE, and since then I can't get passed these errors.
Thanks in advance!
Last edited by 15goudreau (2014-06-28 16:45:53)

15goudreau wrote:
efibootmgr displays
BootCurrent: 0004
timeout: 2 seconds
bootorder: 0001,0000,0002,0003,0004
boot0000* linux boot manager
boot0001* linux boot manager
boot0002* CD/DVD Drive
boot0003* Hard drive
boot0004* UEFI:Sandisk U3 Titanium 3.27
Edit: Because there are two linux boot managers that prompted me to explore them in my options. The first one 0000 returns an error saying a bootable device needs to be inserted. The second one 0001 loads the boot screen but displays the error. My harddrive just displays a blinking cursor that doesn't do anything. Almost as though after the errors I get through the linux boot manager, it passes on to my hard drive and it can't do anything....
ran the create microsoft directory code and such. Rebooted. No change. I'm going to run the other debug things you mentioned.
Tried booting from UEFI shell. When I ran cd \EFI\arch I get "target directory not found" and \EFI\archlinux also gets target directory not found
OK it is not entirely clear what the boot process is doing here and it looks like the most likely problem is a gummiboot config error. Your boot order in the efibootmgr command shows that entry 0001 is the first one that it will try which you have as "linux boot manager" - which presumably will find the gummiboot entry but perhaps it is not configured correctly. Certainly you don't have any \EFI\arch or \EFI\archlinux directories since you previously quoted the contents of the /boot/EFI/ directory using the ls -l command. in \EFI\ there are only a Boot and a Gummiboot directory.
I am not clear why you had to run the command that created the boot entries twice but presumably the entry at boot0000 is likely invalid from the first attempt. You can use the efibootmgr command to delete nvram entries as well as recreate them. I expect it might be a good idea to delete entry 0000, and maybe also 0001 and then create a new entry yourself using the efibootmgr command.
When you say that entry 0001 "loads the boot screen" - do you mean that it does successfully start the gummiboot bootloader but that gummiboot then fails to load the kernel? If so then that would suggest that the problem lies with the gummiboot configuration files, but that the uefi boot process does start correctly and loads gummiboot. If that is the case then I would probably delete the nvram entry 0000 and then make sure that the default order was showing that the first entry that will be tried will be gummiboot (which seems to have its entry as "linux boot manager". I don't use gummiboot myself so I don't have knowledge of what its boot screen looks like.
You can use the efibootmgr command to write a new entry similar to :
efibootmgr -c -d /dev/sdX -p Y -l /EFI/Gummiboot/gummiboot.efi -L "Gummiboot"
where sdX is the drive you have for ESP, and Y is the partition number. So in your case sdX is sda and Y is 3 if your partitions are as you reported previously. Using this command will then give an entry in the nvram called Gummiboot rather than "linux boot manager". For the meaning of the parameters see the output of the command "man efibootmgr".
Check the man command for efibootmgr to see how to remove and reorder the boot entries in nvram. Make sure that the entries and boot order are sane before trying to reboot. Also make sure you only delete the entries that you created and not the ones that will boot to the usbkey or the CD.
If this does start Gummiboot correctly then you need to diagnose why gummiboot is not loading the arch kernel correctly. You can follow the wiki page at https://wiki.archlinux.org/index.php/Gummiboot and set up a manual entry to load the arch kernel as the file /boot/loader/entries/arch.conf containing:
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rw
Here the PARTUUID value to the right of the = sign is the value relating to your root partition which is in your case the output of
blkid -s PARTUUID -o value /dev/sda1
Perhaps this will help pinpoint where the problem lies. Certainly it is looking increasingly like your gummiboot config files are where the boot fails.
If you did want to try to launch your arch kernel from the uefi shell then boot to uefi shell v2 as you seem to have tried before. In your case you will need to tell the uefi shell where the kernel and initrd files are so presuming that your files system is defined as fs0 then from the shell in your case it would then be:
> fs0:
> cd \EFI\
> vmlinuz-linux root=PARTUUID=14420948-2cea-4de7-b042-40f67c618660 rootfstype=ext4 add_efi_memmap initrd=EFI/initramfs-linux-img
Since the kernel and initrd files in your case are named vmlinuz-linux and initramfs-linux-img respectively. Again the numerical value of the PARTUUID is as before the output of the blkid I quoted before.
You only need to change directory to \EFI\ since your kernel and initrd are in /boot in your case. All of these commands have to be carefully adapted to your specific case and can't just be cut and pasted from the wiki entry which only has sample commands in many cases.
I hope this helps.
Last edited by mcloaked (2014-06-23 16:53:35)

Fresh install of 10.5 hangs at boot after 10.5.8 update

Similar Messages

Maybe you are looking for