IMac hanging on boot after 10.10.3

Greetings all,
After upgrading to 10.10.3, my iMac (12,1) started freezing regularly, necessitating a forced shutdown and restart. After two days of this, it failed to boot up at all, but would automatically power down about 1/3 of the way through the boot process.
I detached all devices except the keyboard and mouse and tried booting into Safe Mode with the same results (shut down). I then booted into Recovery Mode and ran Disk Repair. It found that there were errors with the disk (I did not make note of them at time), and that I should backup what I could (already done via Time Machine), reformat the HDD, and restore the backup.
I did this and everything seemed to work OK. However, upon returning home from work, I found that my iMac was frozen again (the mouse moved the cursor, but neither the Dock or any apps would respond). I tried rebooting again, only to find it hanging about halfway through the boot process.
I tried booting into Safe Mode again, but it would hang at the same point. I booted into Recovery Mode and ran checked the disk and everything is fine. So I then tried booting in Verbose mode, and got to this at the fsck_hfs point:
Executing fsck_hfs (version hfs-235)
Warning: couldn't block sleep during cache updae
Warning: proceeding w/o DiskArb
/dev/disk0s2 on / (hfs, local, journaled)
AppleAHCIDiskQueueManager: :setPowerState(alpha-numerical series, 3 -> 2) timed outafter 101096 ms
And that is where we are stuck.
Of course, this thing is, like, ONE MONTH past the AppleCare warranty's expiration date.
Any advice would be appreciated, or even any input as to whether the problem is with the system, or with the HDD. This is the first iMac I've had in since 2001 that hasn't last me six years or more, so I am kind of bummed... =(

Well, I was able to throw a new copy of Yosemite onto an externall HDD and booted from that just fine so, as rkaufmann87 surmised, it is likely an hdd failure. I'm just surprised that there is so little available documentation about this type of error message (as seen when fsck is run).
rkauffmann87 - Getting to an Apple store is not a viable option... =(
seräkare - I'm guessing that we are in the same boat. Are you able to, or even have access to the parts, to try doing what I did above?
Lucky for me, I got to perform HDD replacement surgery on the same model of iMac at my work and, except for the known fan issue (which is resolved by using third-party fan control managers), it is working just fine. I have yet to do the same for my iMac, but my boss was kind enough to let me install my backup on one of work's spare iMacs to use at home until I have the chance to do so (just weighing my options about what new HDD/SSD to install).
The steps are incredibly easy and can be found at iFixit.

Similar Messages

IMac won't boot after power outage

I got a power outage a couple of hours ago. And now my iMac won't boot. When I power it up, it gets pass the white screen with the apple logo. The screen than turns blue with a spinning cursor. The cursor spins for about 10-15 minutes and stops but the normal login screen never appear and it won't boot into the desktop either. I just got a blue screen.
I have boot into the install Disc1 and did the disk repair and premission repair but it didn't help.
Any idea?
Sidney

Oh man, what a disaster!
I tried to do an Archive and Install but the installation hanged at the end of disc 2 after running an iWeb script (according to the install log) with about one minute left. I have waited for two hours but it just hanged there with all the drives spin down.
To make the problem worse. There was no way to quit the install at that point because all the menu items were disabled. The only way out was to power off. But when I powered it back on, it booted right into install directly asking for the disc 2. If I put the disc in it will install again and hang at the same spot.
Disc 2 contains iLife. I know Apple wanted to make things simple but why can't they give me an option to skip it? After all, iLife was already installed.
I finally got it working by booting from disc 1 and did a clean install. It took me all night to re-download all the updates and reinstall many applications. Fortunately, I have my address book, calendar, and most of my works backed up to .Mac so it wasn't a total lost.
On the bright side. Now my iMac is working better than before. I used to have problem getting auto sleep to work but now it works perfectly. Safari also had problem accessing charts (but Camino was fine) in a few web sites like schwab.com. Now everything works.
Lenn and David. Thanks for all your helps.
Now I am looking for a better backup solution so that the recovery won't be this painful if disaster strikes again. Any suggestions?
Sidney

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)

White iMac will not boot after 10.6.8 upgrade

I downloaded the 10.6.8 upgrade last night. This morning, the white plastic iMac will not boot.
I have tried evey known keyboard option.
I have tried booting from the snow leopard dvd.
I have zapped the pram.
Nothing!
Please, any help would be great.

We bought 2 iMac's 27inch with i7 Quad-core. Did the update a couple of hours ago. My Mac asked to reboot after update, but i didn't accept and worked with iTunes for a while. Then rebooted manually. After reboot it took about 15 minutes to reboot (light-blue screen with nothing on it, not even a mouse). My Wife also did the update of 10.6.8 and rebooted when asked. Her iMac also took 15 minutes to reboot, bus update was unsuccesful! So did update again and then denied reboot and rebooted manually! (Apple-logo and then choose "restart").
When we did that, iMac was very fast and updateproblem was solved! So deny reboot and reboot manually and problems are over. Same deal with 2 brandnew iMac. I'm guessing this is an issue. To much of a coincidence for me!

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

IMac won't boot after trying to migrate files to macbook?

While trying to migrate info from my IMAC to my Macbookpro all work froze on both puters. Macbook starts and runs alright. But my IMAC won't boot at all. Tried startup disc and it won't get past picking a destination because it doesn't list one. I made a boo boo hear and need help fixing this.

Drive Preparation
1. Boot from your OS X 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.
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. Quit DU and return to the installer. Install OS X.

IMac won't boot after iTunes Match - Get diskos2 i/o error. Help!

So after almost 24 straigth hours up uploading songs to iTunes Match, I woke up this morning and my iMac wouldn't boot. Gets stuck on the gray screen with the apple logo. I booted in verbose mode keep getting a "diskos2 i/o error." With a little googling some people say it's a bad sector and to erase and reinstall Lion others say it's a failing hard drive. Disk Utlity in Recovery Mode says the drive is ok. Any thoughts out there on what I should do? Thanks!

I am having the same problem. The machine loads just to the point when it says "Loading Mac OSX", then its non responsive for hours. The keyboard and mouse still work, but it won't move past that point.
When I try to repair the disk, it gives me an error message indicating that the disk cannot be repaired. I am bad at backing up my files, so I want to avoid a fresh reinstallation.
The worst part is I had just purchased Disk Warrior, and that won't boot up.
If no solutions are found, does anyone know a way that to initiate the computer in disk mode, so I can hook up another Mac to it, and save all the files?
-alfredo

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/.

IMac won't boot after ram upgrade

For some reason, my iMac late 2013 3.4Ghz quad core i5 won't boot with new ram modules added. New ram is exact same specs as original that came with the iMac. I've tested the new ones on their own in the iMac, and the system boots up fine. Same goes with just using the original ram. But when I put all 4 together, the iMac doesn't boot up. Not even the chime.
Combinations I've tried are:
1-Old
2-New
3-Old
4-New
No boot
1-New
2-Old
3-New
4-Old
No boot
1-New
2-Old
3-New
4-empty
No boot
1-Old
2-New
3-Old
4-empty
No boot
1-New
2-Old
3-Old
4-New
No boot
1-Old
2-New
3-New
4-Old
No boot
The only combinations that work are:
1-New
2-empty
3-New
4-empty
Boot good
1-Old
2-empty
3-Old
4-empty
Boot good
I just got off the phone with Apple, and they are saying all modules have to be the same size. ie. all 4GB or all 8GB. Can't mix and match sizes. Which is strange, because I've never heard of this. My Mac Pro has different speed ram modules, with different sizes in it. As long as I install ram in pairs, it runs like a charm. I've even heard the new iMacs don't have to have ram installed in pairs.
I'm wondering if slot 2 and 4 are maybe damaged? I haven't tried using just slot 2 and 4. To my understanding, you have to use 1 and 3 first. Can anyone confirm this?
Also, I've read a couple of people had to wait 30 seconds for the chime when they installed new ram in their iMacs. I didn't wait 30 sec to see if it would boot. Never heard of any Mac taking 30 sec to just chime in. lol Has anyone else experienced this? Is there a fix? Tx.

CLICKY CLICK---> iMac: How to remove or install memory
Or
Apple>About This Mac>More Info>Memory: Double click "Memory Install Instructions" at the bottom right of window.
my iMac late 2013 3.4Ghz quad core i5
Conflicting info. Your system profile shows: Mac Pro, Mac OS X (10.6.8). Please update/correct.

IMac won't boot after power failure during 10.5.6 update

Help!
Tried to update last night and at something like 80% install, we had a power cut. iMac won't boot at all now - get to a grey screen which tells me to restart. Don't have a wired keyboard. If I did - what are the steps to get this working again.
I believe I have a good backup, but don't want to risk as all the family photos are on the iMac.
Thanks in advance.

Thanks for the help, but can't even get to a screen where I could type anything! I know I'm being dumb here.

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

After software update, iMac hangs on boot and restarts over and over again

I verified and fixed the permissions and disk with no issues.
By default, my iMac enters into an old Windows Bootcamp partition I no longer have so whenever I restart my computer I have to hold down option to boot into the Mac OS.
All this trouble for a lousy Quicktime update.
Any help much appreciated.
- Jeff

Have you done a SMC and PRAM reset? Give those a try, they're simple to do and could fix your problem. Here is how:
1. Turn off your iMac and unplug everything from it for 30 seconds.
2. Plug in the power cord, keyboard and mouse only.
3. Press the power button and immediately hold down the Option, Command, P & R keys until you hear the second gong then release the keys. Your machine will start up normally, then check for the issues you are having.

IMac will not boot after 10.10.2 update

Hello all, I could really use some help. I downloaded 10.10.2 from the app store on my iMac (previously upgraded to Yosemite through app store), and when the system restarted, I would see the white screen with the apple logo and the progress bar about a third of the way across. then the system would ether restart or hang. Here is what I have done so far.
1. I am unable to boot to recovery mode using 'command R'... nothing happens and it goes back to the apple logo and a progress bar that get to a third of the way and stops.
2. I am able to press 'option' during boot and get 3 options for loading (system, recovery, and a Yosemite install disk i made on a USB). selecting any of these options returns me to the apple logo and the progress bar that gets stuck at a one third complete.
3. I am able to select safe and verbose mode. the machine will sometimes get all the way to "system up time in milliseconds" before it reboots.
4. I am able to boot to single user mode. I have run '/sbin/fsck -fy' until it no longer displays 'modification have been made' and it displays 'volume appears to be ok" (takes 2 runs). from here i have tried both rebooting, and exiting, both result in the white screen with the apple logo and the progress bar getting to a third of the way.
5. i have tried clearing the NVRAM
6. I don't have another mac with firewire or thunderbolt to try targeted disk mode
7. i have had 1 success in getting to the log in screen using verbose mode. during the boot there was a whole screen of the same line repeated many times, it said "BUG in process suhelperdt[167]: over-released legacy external boost assertions (1 total, 1 external, 0 legacy-external). after i logged in it reported that the system has un-expectedly shutdown, and that it would send a report to apple (is this a kernel panic?). i hit yes and then show the details. then the system hung up, and rebooted. then hung up again during boot with the same "BUG" message above.
I've got good time machine backups, and don't mind doing a complete reload if i can ever get to that option.
Thanks in advance for the help.

I have a 27 inch imac (10,1 late 09) that was doing the same intermittently during 10.10.2. In a fit of frustration, I updated yesterday to 10.10.3 and now the computer is doing exactly as you describe. I cannot get past the white screen at all. I have booted into recovery, verified and fixed the drive even though it it checked out fine. and attempted a fresh download on a clean partition. nada... i can get into safe mode, and I tried installing the SMC fan control, switching off transparency, and lowering my resolution. none worked.
I was convinced my hard drive was dying (when I had 10.10.2), and replaced it last week with a SSD. The SSD ran great for about a week, then had the same problems. I never had a problem with 10.10.1 or prior. I have checked my ram, and that does not fix the problem (swapping all four into the front dime slots in sequence).
This computer has run great since 09, and I have never had any issues until now, but it is now a very expensive paperweight. I cannot do the internet recovery that sets up the original OS the machine shipped with (too old for that feature), and it will not let me download a previous version of OS X from the app store (I have mavericks, lion, etc there).
I think my apple love affair is officially over. Looks like i will be searching for a pre-yosimite computer to download a usb version of mavericks or lion, and I sure as **** am not buying another apple product in the near future! I was very close to pulling the trigger on a new macbook, sure glad I did not waste my money -again-.

Hanging on boot after upgrading server.app

After upgrading to 10.9 Server.App my boot hangs at "/etc/rc.server: line 14: /etc/rc.server.firewall: No such file or directory" and won't boot into safe mode either. Anyone know how I can fix this without restoring from a backup?

Cameron, thanks for your feedback.
I'm on a 2011 iMac, with a DIY Fusion Drive (I added a SSD inside). I always had slow startups. I thought it was the custom Fusion Drive's fault, but now I know it was not.
Now I can't boot at all, just after applying the most recent 10.9.2 security update. This is a software issue. The iMac was running Mountain Lion Server, then I upgraded to Mavericks but did not upgrade to Mavericks Server. However there were remains of the old 10.8 Server app.
As I said, yesterday I deleted all those remains (booting from an external drive). However I forgot the most obvious thing: open that **** /etc/rc.server file and comment out line 14.
This morning I booted the iMac again, in verbose mode. The message about /etc/rc.server was not there, at last, but fsck was launched and took a long time. I had to go to work, where I am now, and I don't know if fsck finished its work. I'll let you know...

My imac hangs during starup after installing update

I installed the new update for OSX lion this morning and after installation the mac rebooted and it hangs on the gray apple screen.

The system was working fine before the update.
I got severals errors with the restore disk permissions the first time I ran it. The second time it didn't return any errors. The disk utility din't return any errros.
After booting in safe mode and hhaving the system hang again I ran the repair disk permission utility again and keep getting the same errors that are being repaired even after running it 5 times is a row.
The Imac is 3 months old and came with Snow Lzapord installed whitch I upgraded to Lion after startup thru the up-to-date program Apple offered.
Thanks for all the help seeing this is my first Mac

IMac hanging on boot after 10.10.3

Similar Messages

Maybe you are looking for