Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

vyvafc

macrumors newbie
Original poster
Nov 21, 2015
4
0
Mid-2011 iMac, 500GB HDD, 12GB RAM, Mavericks.

At start-up get Apple logo + three beeps. Have reseated RAM, and tested RAM through another computer - RAM is good, no problems. HDD healthy as per Disk Utlility/Repair in Recovery Mode. Won't boot to Safe Mode.

HDD was way too full (stupid me), but friend has taken 50GB+ off in Target Mode so that shouldn't be the problem any more.

So thinking the problem is the OS (maybe set off by my cramming the HDD?). I have two options: restore a Time Machine back-up (I should have one even of the morning before the crash occurred), or reinstall OSx (which, as the iMac did not come with installation discs, would mean an upgrade to Yosemite, yes?), both options through Recovery Mode.

I really don't know which option to choose at this point and would be very grateful for experienced users' thoughts. What are the relative merits/dangers of each path? Does one option stand out as being more sensible?

Many thanks
 
I think you would be wasting your time with both the Time Machine restore and the OS reinstall. It sounds like you have a hardware issue. Three beeps is typically bad RAM regardless of what the other test said.

The fact is won't even boot is safe mode is not good either. That is a stripped down test mode that will bypass any odd utilities or drivers you may have installed.
 
I think you would be wasting your time with both the Time Machine restore and the OS reinstall. It sounds like you have a hardware issue. Three beeps is typically bad RAM regardless of what the other test said.

The fact is won't even boot is safe mode is not good either. That is a stripped down test mode that will bypass any odd utilities or drivers you may have installed.

Hi

Thanks for taking the time to reply, I appreciate it. But, FYI, I went ahead and tried the OSx re-install and it worked. I wonder whether some script got corrupted that meant the system believed there was a hardware issue.
 
Hi

Thanks for taking the time to reply, I appreciate it. But, FYI, I went ahead and tried the OSx re-install and it worked. I wonder whether some script got corrupted that meant the system believed there was a hardware issue.

The logic that stores the beeps is in firmware, nothing to corrupt. If you heard the beeps before, the problem likely still exists.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.