PDA

View Full Version : Runcore 80GB (MBA revA) dead?




tomppah
Apr 7, 2010, 03:06 AM
Hello,

two months ago I finally got myself a Runcore SSD as well as I was getting really frustrated with the slowness of MBA rev A. I've been very happy with the drive but now suddenly when I tried to wake my computer it didn't respond at all, so I shut it down and restarted it, I just get the question mark blinking in the boot that it can't find the system files.

I tried to boot to the Snow Leopard disc to go to Disk Utility and when I got there, I noticed the Runcore disk wasn't listed anymore :eek:

Any suggestions? I guess I need to open it up again... :rolleyes:



aaronp1994
Apr 7, 2010, 03:07 AM
Go to the disc utility and i know your going to hate to have to do this and lose all of your data.. but re partition your data (GUID)

Pixellated
Apr 7, 2010, 03:12 AM
Go to the disc utility and i know your going to hate to have to do this and lose all of your data.. but re partition your data (GUID)

He can't as his drive isn't recognised.

tomppah
Apr 7, 2010, 04:36 AM
Alright, drive is okay. The LIF cable had loosened in use a bit and wasn't properly attached anymore. Attached the cable properly again and MacBook is up and running again :-)

stoconnell
Apr 7, 2010, 10:12 AM
Alright, drive is okay. The LIF cable had loosened in use a bit and wasn't properly attached anymore. Attached the cable properly again and MacBook is up and running again :-)

You might want to tape the cable to the drive to allow for strain relief on the ZIF interface (Rev A are PATA-ZIF, Rev B+ are SATA-LIF).

Scottsdale
Apr 7, 2010, 12:19 PM
You might want to tape the cable to the drive to allow for strain relief on the ZIF interface (Rev A are PATA-ZIF, Rev B+ are SATA-LIF).

I had to tape mine. In addition, Apple ships the drives with the cables taped.

Runcore
Apr 7, 2010, 03:47 PM
I think you lost the FW partition somehow. This has only happened about 3 times to date. You hit the lotto Grrr

You are going to have to get an RMA and send the drive back to where you got it for replacement.

Matt
Runcore

Update: I should have read the rest of the thread hehe I see the issue has been resolved without having to send the drive back. I also see that my guess as to what the issue was was incorrect. Happy to see that was not the problem.