Mavericks install stuck - Error log 'Can not connect to /var...'

Question

Beau Jade Author

Level 1

3 points

Mavericks install stuck - Error log 'Can not connect to /var...'

Good Evening,

I attempted to perform a fresh install of Mavericks on my Late '12 MacBook Pro from 10.8.

Using Disk Util I was required to reformat the HDD to GUID from MBR (which was due to a previous Bootcamp install)

Now when attempting to install Mavericks the loader hangs at 'About a second remaining'

The Log states:

Can not connect to /var/run/systemkeychaincheck.socket: No such file or directory

Erasing the HDD removed my Mountain Lion Recovery partition, so until a fix I'm stuck.

When booting without the Mavericks USB stick all I see is the Question Mark folder.

Please help.

Thanks,

Beau

MacBook Pro, OS X Mavericks (10.9)

Posted on Oct 23, 2013 8:51 PM

Reply

Answer 1

Beau Jade Author

Level 1

3 points

Oct 23, 2013 9:01 PM in response to Beau Jade

The 'About a second remaining' turned out to be more like 20 minutes.

It's now installing from different loader.

I will update this thread as the process continues to offer assistance to others in the same boat.

Reply

Answer 2

Oct 24, 2013 1:29 AM in response to Beau Jade

My MacPro early 2009 is doing the same - installer stuck on 'About a second remaining'. Its installing to a freshly formatted SSD in the optical drive. Help..!

Reply

Answer 3

Oct 24, 2013 2:13 AM in response to Beau Jade

I have the same problem too.. I force restart my mac then the software update also restart by itself. But after updating, the mac is VERY VERY LAG.

Reply

Answer 4

redpola

Level 1

29 points

Oct 24, 2013 7:12 AM in response to Beau Jade

I was going to say "me too" but after hanging for about half an hour it continued and seems to be working fine now.

Reply

Answer 5

vea1083

Level 3

714 points

Oct 25, 2013 5:31 PM in response to Beau Jade

The trick here is to be patient and be prepared to wait upwards of 20 minutes looking at the "About a second remaining" message while installing OS X Mavericks from an bootable USB drive. In my case I was able to successfully install OS X Mavericks after I waited for that amount of time.

Reply

Answer 6

Dec 16, 2013 12:45 AM in response to vea1083

Just had the same experience with my older Macbook Pro - stick with it (30 mins in my case) and it'll eventually move on.

Reply

Answer 7

Jan 16, 2014 8:29 PM in response to Beau Jade

Ditto here. My 15" mid-2007 Macbook Pro with a new hybrid SSD/HDD took about 25 minutes once the "About a second remaining" message appeared, but then it rebooted itself and continued installing. My USB drive has an LED activity indicator, so I knew something was happening...

Reply

Answer 8

jojoboyz

Level 1

0 points

Feb 4, 2014 10:13 AM in response to Beau Jade

connect to your wifi when installing, it maybe works.

Reply

Answer 9

MESM

Level 1

0 points

Mar 18, 2014 5:59 PM in response to Beau Jade

My 2009 15" MacBook doesn't make it past the middle of the install, but the install message says something like-

Install complete. Your computer will restart automatically, despite the blue activity bar reading at half. It has sat for several hours like this, twice now. I have an appointment at the Apple store tomorrow, but would love to solve this before, if possible.

Upgrading from Snow Leopard so I can upgrade to Lightroom 5. I'm not too savvy with all the upgrade stuff, but when I have held the power button down and rebooted, it shows the Mavericks screen and nothing else that resembles my desktop. People are talking about using disc utility, but I cant seem to access anything.

I'm sure I'm missing something. hopefully someone can tell me what it might be.

Reply

Answer 10

Lukcha

Level 1

0 points

Apr 7, 2015 2:02 AM in response to Beau Jade

I note the original poster's error message: "cannot connect to /var/run/systemkeychaincheck".

Most of the answers available online (including this thread) address the issue of hanging with one second remaining but don't explicitly discuss cases with the above error message in the Log. So, just to clarify; the solution of waiting for an indefinite period (for me it was about 15 mins) did indeed solve the issue. The system restarted itself and continued the installation process successfully.

Reply