Nicolas Junod

Q: Which files prevent a normal boot on Maverick 10.9.5?

What can I do to check files that could be preventing the boot to go passed the spinning wheel/grey screen preventively ?

 

An October 2nd restart of OSX 10.9.5 on my iMac 2,9 Ghz Intel Core i5 resulted in the too famously known "grey screen with spinning dental wheel" on Octobre 2nd. I tried all tips and tricks that I could read on this forum and apple support, to no avail, including restoring the day before Time Machine (connected by WIFI to my NAS), restoring a new OSX... finally the only thing that worked was to re-install a restore of September 29th.

 

What did I install since the 30th September ? The bash fix update (yet not asked under the update software tool)  the HP update and, because my ISP provider suspected virus/trojan using my IP address for DoS actions, the famous "Avast" antivirus. I also activated my OSX firewall.

 

So I restored the 29th Sept version which had none of these 4 and proceeded with the bash update, the hp update and the firewall. Remember I installed Avast only Oct 2nd and, as such, no files were present in my 29th Sept restore.

 

Yesterday, I had to perform a restart and... the issue started again. After hours, I ended up reloading my 29th September restore which worked.

 

However this time I did not apply the bash fix update not the hp one and even less so the firewall. I don't know if this will do the trick but really don't dare restarting (and have to spend yet again hours and hours waiting for a restore and selecting all my files and folders).

 

I read on some files that may be spinning in circle trying to get to something validated and which could be the issue of the persistent grey screen. But frankly I am no expert and this is the first time in - literally - decades that I experience such situation.

 

Any expert help welcome !

 

Man thanks & best regards,

 

Nicolas

iMac (21.5-inch, Late 2012), OS X Mavericks (10.9.5)

Posted on Oct 7, 2014 3:21 AM

Close

Q: Which files prevent a normal boot on Maverick 10.9.5?

  • All replies
  • Helpful answers

  • by Mike Sombrio,

    Mike Sombrio Mike Sombrio Oct 7, 2014 3:42 AM in response to Nicolas Junod
    Level 6 (17,283 points)
    Apple Watch
    Oct 7, 2014 3:42 AM in response to Nicolas Junod

    REmove and/or don't install Avast. You don't need it.

  • by Linc Davis,Solvedanswer

    Linc Davis Linc Davis Oct 7, 2014 6:54 AM in response to Nicolas Junod
    Level 10 (208,037 points)
    Applications
    Oct 7, 2014 6:54 AM in response to Nicolas Junod

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.

    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.

    Step 1

    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.

    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.

    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.

    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.

    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.

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

    Step 2

    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.

    Step 3

    Sometimes a startup failure can be resolved by resetting the NVRAM.

    Step 4

    If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.

    Step 5

    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.

    Step 6

    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.

    Step 7

    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.

    Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.

    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.

    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)

    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.

    Step 8

    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.

    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.

    Step 9

    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  

    Step 10

    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.

    Step 11

    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.

    Step 12

    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.

    Step 13

    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 7, 2014 7:53 AM in response to Mike Sombrio
    Level 1 (4 points)
    Oct 7, 2014 7:53 AM in response to Mike Sombrio

    Thanks Mike but by installing a 29th Sept restore both times, I loaded a backup that did not contain any Avast files. Really interested to know which files could make the Mac spin and stay as such at boot up.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 7, 2014 8:08 AM in response to Linc Davis
    Level 1 (4 points)
    Oct 7, 2014 8:08 AM in response to Linc Davis

    Thanks Linc,

     

    I very quickly saw that post after my first "no restart" on Oct 2nd and followed the list nearly completely : I am OK on 1, not having 2, 5, 7, 9, 12, 13 (no genius store in the area) I went through 3, 4, 6, 8 (all good on disk repair, and permissions repairing fine but seing the same errrors coming again when relaunching repair permission right after the first repair permission process finished), 10 (was fine except that it didn't recuperate all my settings, App pwds etc).

     

    My next - unvoluntary - trials would be 11 but I still would have hoped for some savy tech Unix/OSX person to help me go through crash codes, plist types of files or other launchd, launch agent and other daemons that sit on my disk and could be safely dumped, etc. : whereever a file could prevent a startup being côrrupted (in the early (Mac) days one would dump a few corrupted app preferences and things went fine again...)

     

    Best regards, Nicolas

  • by Linc Davis,

    Linc Davis Linc Davis Oct 7, 2014 8:23 AM in response to Nicolas Junod
    Level 10 (208,037 points)
    Applications
    Oct 7, 2014 8:23 AM in response to Nicolas Junod

    You might be able to learn something from the system log messages written during the boot failure, but it's not clear how you would access them.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 7, 2014 8:40 AM in response to Linc Davis
    Level 1 (4 points)
    Oct 7, 2014 8:40 AM in response to Linc Davis

    On my MacintoshHD/Library/Application Support/CrashReporter/ I have 3 files :

     

    The first one at 23:39 last night which is the time I ENDED an earlier date recovery which proved unsuccessul (Oct 6th backup)

     

    AnonymousIdentifier_020CDCC3-412D-5604-8262-2BE3838EC3A8.plist

     

    And then two more at 03.04 this AM (when the 2nd restore (Sep 29th backup) ended running and proved successful) :

     

    DiagnosticMessagesHistory.plist

    SubmitDiagInfo.domains

     

    In that same Library under LaunchAgents I have 9 plist files all older than 25th September 2014 and refering to apps I use. Actually writing this I found one related to an app I don't have anymore - dumped it.)

     

    In that same Library under LaunchDaemons, 8 plist files, all related to apps I use.

     

    On my other Library (the one where you need to press "Alt" to see it on the Finder's menu list), also under Application Support/crash reporter I have about 10 plist files, all older than 23rd September except on which was this afternoon 14:22 (I wasn't even around) :

     

    Intervals_020CDCC3-412D-5604-8262-2BE3838EC3A8.plist

     

    In this same Library, LaunchAgents folder : 5 plist files all older than 27 Feb 2012 (wonder if I can dump these...)

     

    Best regards,

    Nicolas

  • by Linc Davis,

    Linc Davis Linc Davis Oct 7, 2014 9:59 AM in response to Nicolas Junod
    Level 10 (208,037 points)
    Applications
    Oct 7, 2014 9:59 AM in response to Nicolas Junod

    If there's a panic or crash report, please post the contents.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 7, 2014 10:17 AM in response to Linc Davis
    Level 1 (4 points)
    Oct 7, 2014 10:17 AM in response to Linc Davis

    Hi Linc

     

    No file under "/Library/Logs/DiagnosticReports/". Any other folder I should look for ?

  • by Linc Davis,

    Linc Davis Linc Davis Oct 7, 2014 10:37 AM in response to Nicolas Junod
    Level 10 (208,037 points)
    Applications
    Oct 7, 2014 10:37 AM in response to Nicolas Junod

    See what's in /var/log/system.log. Not too many lines, please.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 7, 2014 11:11 AM in response to Linc Davis
    Level 1 (4 points)
    Oct 7, 2014 11:11 AM in response to Linc Davis

    Just pages and pages of code... starting at 02:22.00 which is in the middle of the successful restore process.

     

    Not posting these hundreds of lines on this forum. Since it is a success ful process (at the end), not sure it'll bring anything.... unless we can narrow down by searching a specific text... for example, with the keyowrd "error".... one of many :

     

    Oct  7 02:22:39 localhost mDNSResponder[46]: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 00007FC173819B60 iMac-A820662153DC.local. (Addr) that's already in the list

     

    What do you think ?

     

    Best regards,

  • by Linc Davis,

    Linc Davis Linc Davis Oct 7, 2014 12:15 PM in response to Nicolas Junod
    Level 10 (208,037 points)
    Applications
    Oct 7, 2014 12:15 PM in response to Nicolas Junod

    That's not relevant. The steps I posted earlier will lead to a resolution.

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 8, 2014 2:52 PM in response to Linc Davis
    Level 1 (4 points)
    Oct 8, 2014 2:52 PM in response to Linc Davis

    Well, well, another update prompting a restart and a grey screen again. This time I followed step 11, i..e full erase of my drive, clean install of OSX and migration from my Time Machine backup. Worked well. Let's see if it'll hold the next restart process... I'll try and give myself a few days  before I go through another update requiring a restart : need some rest and right now my confidence level is a little low... wonder why ?!

  • by Nicolas Junod,

    Nicolas Junod Nicolas Junod Oct 17, 2014 11:13 PM in response to Linc Davis
    Level 1 (4 points)
    Oct 17, 2014 11:13 PM in response to Linc Davis

    After a week's vacation abroad, I finally decided to see if "step 11" indicated by Linc Davis had done the trick. After careful Time Machine and mirror-like types of backups, I went ahead and restarted the Mac, prompted anyway by the latest iTune latest, with much apprehension...

     

    But the Mac restarted just fine and fast !

     

    Thanks Linc,

    Best regards,

    Nicolas