Currently Being ModeratedMar 29, 2012 5:13 PM (in response to Charlie.Loxely)
Please stop doing things like a Windows user. Everything you've done so far has made matters worse.
First, CNET is not a reliable source of technical information. Never do anything based on what you read on CNET unless it's confirmed independently.
I've never heard of "Avanti," and it's not clear from your description what it is. It sounds like some kind of useless crapware.
On the other hand, I do know what "MacKeeper" is: it's a trojan. You'll need to remove it, not according to the lying developer's instructions, but according to the instructions here:
But first you have to be able to boot. The following support article is somewhat outdated. Where it refers to booting from an installation disc, you should boot from your recovery partition by holding down the key combination command-R at the chime.
Currently Being ModeratedMar 29, 2012 6:59 PM (in response to Linc Davis)
Thank you for your link - as it happens I had just found it myself, so it's good to know it's good to hear it recommended. I also read up on the boot partition. Since it's a reasonably new iMac I'm going to hope it has one.
As for thinking like a Win user, I have to confess that I still wrestle with my inability to get inside the OS X There are pros and cons to this, I'm sure, but at moments like this I think 'In Windows I could fix this!" (chuckles) Anyhoo, I'll see how this plays out and keep this thread posted.
Thank you, Linc.
Currently Being ModeratedMar 30, 2012 6:17 AM (in response to Linc Davis)
Well, I've run through all the stuff on the page previously discussed, and I've also run the utilities in Recovery Mode (http://www.macworld.com/article/1161088/hands_on_lion_recovery_mode.html), but I'm still in the same boat.
Since the nature of the problem is not disk related anyway, I'm wondering if there is a way to restore the proceoss through Terminal. Any ideas, please?
Currently Being ModeratedMar 30, 2012 6:28 AM (in response to Charlie.Loxely)
What exactly is happening? My understanding is that the boot process is hanging at a gray screen. If that's so, and you've taken all the steps suggested in the Apple Support article linked above (substituting the recovery partition for an installation disc), then you have a hardware failure.
Currently Being ModeratedMar 30, 2012 8:38 AM (in response to Linc Davis)
Well, given that I don't have an OS install disk and don't use time machine, the only other option seems to be to reinstall Lion online. I hesitated there because I can't tell if this will overwrite all my user data. I'm a student and atm my external is chocked up with virtual machines that I need for coursework
So here's where I'm at right now:
I've done everything in the article except this online reinstall (including using the option to view the safe mode process, if that info is helpful), and I still have the same symptoms: I turn it on and still get nothing beyond the white screen with an apple and a spinning grey 'wait' indicator. I'm quite certain it's not hardware related, because it happened immediately after I stopped the launchd process. There were 3 launchd processes, and I chose the one connected with my username.
Does that make sense?
Currently Being ModeratedMar 30, 2012 9:14 AM (in response to Charlie.Loxely)
... I can't tell if this will overwrite all my user data.
Currently Being ModeratedMar 30, 2012 10:45 AM (in response to Linc Davis)
Not a single one, sadly. Life is strange: A new external was first on my list of new purchases.
I'm convinced, however, that it relates to this launchd file. If my understanding is correct, launchd is critical to loading user displays. If that's the case, and if it got corrupted somehow, iti could cause this inability to load, perhaps.
If this is a clue, I can get into the iMac from my laptop via the wireless. As per usual I can see and manipulate its data files, but have no access to the system files. After connecting, if I attempt to "share screen" I enter my ID and password as per usual, then the dialogue box goes into the same spinning loop as the iMac monitor is in. So this seems to point toward a software level display issue. But truthfully I'm way out of my depth.
Currently Being ModeratedMar 30, 2012 10:54 AM (in response to Charlie.Loxely)
My thoughts are that you can do nothing at all with the computer until you've backed up your data. After that, if you think you know a way to fix the damage without reinstalling, you're on your own.
There are several ways to back up a Mac that is unable to fully boot. You need an external hard drive to hold the backup data.
1. Boot from your recovery partition (10.7 or later), a local Time Machine backup volume (10.7.2 or later), or your installation disc (10.6.8 or earlier.) Launch Disk Utility and follow the instructions in the support article linked below, under “Instructions for backing up to an external hard disk via Disk Utility.”
2. If you have a working Mac, and both it and the non-working Mac have FireWire ports, boot the non-working Mac in target disk mode by holding down the key combination command-T at the startup chime. Connect the two Macs with a FireWire cable. The internal drive of the machine running in target mode will mount as an external drive on the other machine. Copy the data to another drive.
3. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Currently Being ModeratedMar 31, 2012 4:52 AM (in response to Linc Davis)
Yes, it saddens me, but that seems to be the case. (sigh) Late last night I realized that this computer might, just might, still be under warranty, and maybe, just maybe this issue could be addressed under it.
I went through Apple, and sure enough it is. I've arranged for a phone call with them this am, although I believe you have covered pretty much everything they may say. There is one hope, but it's a long shot, and that is that someone there will know how to restart whatever process is not functioning via the laptop. I'm not holding my breath, however.
Linc, you rock. (smiles) I am so grateful to you for taking this time with me. Seriously. (curtsies) I'll post a follow up if I find another solution, as I'm sure you'd be curious to know.
Be well, happy weekend and thanks again!
Currently Being ModeratedMay 9, 2012 7:58 AM (in response to Charlie.Loxely)
To anyone who has stumbled across this looking for answers to a similar problem, the final solution was replacing the drive. In the process, however, I was able to 'mostly' repair the directory structure with Disk Warrior (an excellent program specifically for this task and recommended by Apple techs.) While this did not fix my problem, it helped just enough that I could get access to my data in target mode via a Firewire cable. This enabled me to port the data through my laptop onto an external drive. Not a perfect solution, but the data is the important thing. Hats off to the phone techs and to my local MAC store, Mac East.
Good luck to any of you who are struggling with this kiind of thing.
Currently Being ModeratedMay 9, 2012 8:36 AM (in response to Charlie.Loxely)
For anyone finding this thread: Disk Warrior is an expensive and specialized application whose only use is to try to recover data from a damaged volume that Disk Utility can't repair, and for which there are no backups. It's not a maintenance tool; it's a recovery tool. If you have adequate backups — which means multiple backups — you’ll never need a recovery tool, and therefore Disk Warrior is useless to you. Don't waste money on it. Spend the money on backup drives instead.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points