Mac mini will not startup in safe mode

Question

Level 1

4 points

Mac mini will not startup in safe mode

AT restart while holding down shift key to startup in safe mode nothing happens, then I get a screen with lines of code, "panic(cpu 0 caller 0xffffff800ebd255a)" ,"debugger called:<panic>". Plus a lot of other code, then it goes into a loop where it continually tries to reboot with the same results.

i Have had problem with this for some time but have always been able to startup in safe mode and then restart and my system has always booted up.

at a loss and out of business now.

Mac mini, OS X El Capitan (10.11.5)

Posted on Jun 11, 2016 12:35 PM

Reply

Answer 1

lllaass

Level 10

210,519 points

Jun 11, 2016 12:39 PM in response to swrench

- Can you post a readable screenshot of the kernel panic that appears on the screen? That will provide the details necessary to better help you.

- What model Mac Mini? Some models have hardware problems

Without that:

- Try resetting the SMC and NVRAM/PRAM

Intel-based Macs: Resetting the System Management Controller (SMC)

https://support.apple.com/en-us/HT201295

About NVRAM and PRAM

https://support.apple.com/en-us/HT204063

- Try starting in Safe Mode

OS X: What is Safe Boot, Safe Mode?

https://support.apple.com/en-us/HT201262

- Boot to Recovery and repair the startup disk

OS X: About OS X Recovery - Apple Support

https://support.apple.com/en-us/HT201314

- If it is repairable reinstall the OSX

How to reinstall OS X on your Mac - Apple Support

https://support.apple.com/en-us/HT204904

- If you do not have a backup use disk utility to restore the internal disk to an external disk so you can try to recover data.

Then format the startup disk and do a fresh install of OSX

Reply

Answer 2

swrench Author

Level 1

4 points

Jun 12, 2016 5:19 AM in response to lllaass

Reply

Answer 3

swrench Author

Level 1

4 points

Jun 12, 2016 9:39 AM in response to lllaass

HI, thanks for the quick response.

I'm not sure of the exact model#, I did purchase it mid 2009. The serial #YM******9G6, Mac Mini 2.53/2X2G/320/SD/AP/BT - USA EMC No:2336.

I Did try and reset the SMC and the NVRAM but that didn't help. I tried to restart using my original MAC OS X disk, but it would eject the disk instead of booting from it, and I did start holding the C key down. I was able to take a picture of the screen with my iPad and posted it separately. There are two separate screen images with different content that showed up on different times when starting up. I'll post the second one later today.. I do have time machine and do have a backup as of yesterday morning of my files, but I'm concerned that if it is a software issue that too has been backed up.

THank you for your help, it is very appreciated.

RIck

Reply

Answer 4

lllaass

Level 10

210,519 points

Jun 12, 2016 11:33 AM in response to swrench

you have a 2.53 GHz processor that correlates to a late 2009 Mini

It is not unusual for the optical drive to fail. The one in my late 2009 Mini failed about three years ago with the symptom that it would try to read a disk and spit it out.

The image you posted said the process mds was involved and mds is used to index Spotlight search.

How old is the HD? The ne in my 2009 Mini failed about three years ago. I found that the optical drive failed when reinstalling apps the optical drive did not work.

Do you have access to another Mac? There are things yo can do if you have another Mac.

What OSX version is on the your 2009 Mini?

Reply

Answer 5

swrench Author

Level 1

4 points

Jun 12, 2016 11:32 AM in response to lllaass

HI,

The HD is the original drive. I was running the latest version of El Capitan. I do have access to my wife's Mac mini. We actually purchased

both at the same time, so I'm guessing hers is due to start having some problems also. I'm not too worried about the programs and files,

since i I have everything backed up to Time Machine on a Time Capsule drive. Guessing it's time to bite the bullet and buy new machines.

i Do appreciate your looking at all this for me.

thanks, Rick

Reply