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

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Fair warning, I'm probably gonna ramble a bit...

The other day, I was gifted a mid-2010 Mac Mini from a friend. Seems stock (2.4 Duo, 2GB RAM, 320GB). The system had originally been in use as a touch screen kiosk in a mall or something, primarily running Win7 via BootCamp. Being PC users at heart, my friend started by wiping all the drive partitions, and...found himself stuck. Not sure what else he tried before giving it to me, but he was unable to get any OS loaded back onto it himself.

So I start fiddling with it.
Booted a High Sierra Install USB (all my install USBs during this process are made wia TransMac on Win10, for now) relatively quickly, seemed to complete the initial stage of the install fine (apart from the date changing nonsense), and rebooted. During that first reboot, install progress appeared to stall almost immediately....let it sit for a couple hours with no obvious progress, so rebooted and started over...

The first thing noticed is, from here on out, boot from USB takes FOREVER. ~10+ minutes from power to install menu. I erase/re-partition the drive again and start the install over. The next umpteen install attempts with High Sierra and/or Lion all fail/error out at the 2-3 minutes remaining mark, with the hard drive still left in an unbootable state (i.e. not showing up on my boot menu). High Sierra would perform it's install process quickly, Lion would stall at several points, taking a good 15-20min longer than High Sierra to fail.

Additionally, while the Lion USB seemed to boot a little faster than High Sierra, it would hang at the Language Select menu for a good 10+ minutes, unresponsive. Mouse would move, but not respond to clicks. Display would auto-sleep and was able to return. But otherwise just unresponsive.

At this stage, I broke down and pulled the hard drive, tossed it in my dock for testing.
The original drive produced a couple weird results. Namely, what should have been an 8192KB cache only reported as ~7202KB, and the drive would only report as Sata 1.5 instead of 3, with speeds that seemed to match. SMART data otherwise reported normal.
So, I swapped the drive with a newer Hitachi 320GB I had that tested much better.
This did not change the Mini's behavior at all.
But at least I knew I could trust the drive now.

After a few more (unchanged) attempts at High Sierra and Lion, and fell back to Snow Leopard and gave it a shot. Initially, it went the same...slow to boot from USB, hung for a while at Language, install seemed to stall at places but seemed to complete after roughly 30-45 minutes. Like the others, this one errors at the end of install, but this time it was a "couldn't boot from target drive" error or some such and directed me to the Startup Drive utility. Startup Drive utility gave a bless error -- drive couldn't be unmounted, I determined. A simple reboot and we were on our way....

Snow Leopard booted into intial setup. Like the install, it hung for quite a while at Language. But once things reached desktop, it seemed smooth-ish. Likewise, on reboot, the desktop remains unresponsive for several minutes. And, while in use, there are frequent freezes (still with mouse movement) that can last 1-5 minutes.

While installing system updates for Snow Leopard, the system reboots fairly quickly, but hangs on the update screen for a while. A hazy, purple screen overlay...like the screen hasn't fully faded in yet...you can still faintly see the Software Update window behind it, and you can see the progress bar moving, but the mouse cursor is also locked. As updates reach around the 75% mark, the screen will come fully into focus and mouse movement is restored.

While the system *seems* to be operating within acceptable temps, I can't help but wonder if this is all some sort of thermal issue. (MFC reports the CPU die temps as 50's on average, and haven't seen it about 66 yet -- interestingly, when things are "frozen", I can still watch things like MFC updating every couple seconds -- but MFC also doesn't appear to be showing the GPU temp.) I'm debating pulling the board and refreshing the heatsinks to see if that helps any.

I've not yet been able to run ASD on the system yet. I'm still working on getting ASD 3S139. (That should have been my first step, but I apparently lost my old archive torrent which had individual files, and am waiting on a full 50+GB archive to download. Perhaps tomorrow.)

As old as this thing is, it doesn't hardly seem worth the trouble, but I'm very very stubborn, and I'd really like to reach a point where I can get this thing stable, add some ram to it, maybe an SSD, and have a nice little productivity box running High Sierra tucked discreetly away on my desk.
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Overheating? Is the fan running? Blow the dust out.

Fan's definitely moving air, exhaust channels are clear. Overheating was about the only thing I could think, given the current lack of information. (Why must Macs obfuscate so much?)

At the moment, from a cold boot, it takes a couple minutes to boot to the Snow Leopard desktop.
The desktop is then unresponsive (no clicks, no mouse-over tooltips) for a good 10 minutes. But yet not entirely frozen, as I still have mouse movement, and I can see MFC temp and rpm data update in the system tray every couple seconds.

With MFC temp data being all I have to go on, temps look normal:
CPU Diode at 53C, CPU Heatsink at 47, Proximity at 46. Everything else below that, save PSU at 57.
MFC doesn't show a GPU-specific label, so I don't know what's going on there, if anything. I would think Proximity would be a clue, but I don't know the exact sensor placement yet.

I'm hoping ASD can give me something else to go on, but it's gonna be a while before I can get that running.

Any other thoughts for identifying the real problem ?
Any other apps I can run to dig into this thing and root out the underlying cause?
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Beginning to think this Mini might just be borked. Specifically, I think the issues I'm having probably stem directly from the NVRAM (and/or SMC).

As I mentioned, I was able to get Snow Leopard installed, slowly, with the only obvious hiccup being that it failed Bless at the end of the initial installation. However, with no other boot drive in the system, this didn't seem to affect it.

Snow Leopard ran (poorly, as described), and was able to get all available updates installed, and downloaded the El Capitan installer, and ran it... Likewise, it failed at the end of install, unable to set the new boot options for restart.

Digging into it, I see very plainly "nvram: nvram is not supported on this system", which we know isn't supposed to be true.

Attempts to access or modifiy the nvram via terminal, normal boot or safe boot, result only in "not supported".
Attempts to use Cmd+Opt+P+R, with both wired and wireless keyboards, result in no visible changes. (Although at some point during this whole mess, I completely lost my normal Apple boot chime...all I'm greeted with now is the sound of the optical bay cycling.)
Attempts to reset the SMC (power cycle) result in no visible changes to behavior.

ASD 3S139 EFI tests all pass (with only a hiccup on SMART attributes).
ASD 3S139 OS tests seem to pass.

I'm at a loss.
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
I would very much love to do that, if you would kindly tell me how.
(I tried to update to 1.5, but that requires Lion.)
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Okay. Getting closer and nowhere all at the same time.
This is what Terminal gives me when I attempt to bless the update...

Niccador$ bless -mount / -firmware "/Applications/EFIUpdate/MM41_0042_03B_LOCKED.scap" --recovery --verbose
EFI found at IODeviceTree:/efi
GPT detected
No auxiliary booter partition required
System partition found

Returning booter information dictionary:
<CFBasicHash 0x104302e90 [0x100245ee0]>{type = mutable dict, count = 3,
entries =>
0 : <CFString 0x100019a60 [0x100245ee0]>{contents = "System Partitions"} = <CFArray 0x1043028f0 [0x100245ee0]>{type = immutable, count = 1, values = (
0 : <CFString 0x104303030 [0x100245ee0]>{contents = "disk0s1"}
)}
1 : <CFString 0x10001a2a0 [0x100245ee0]>{contents = "Data Partitions"} = <CFArray 0x1043032a0 [0x100245ee0]>{type = immutable, count = 1, values = (
0 : <CFString 0x10022a9b0 [0x100245ee0]>{contents = "disk0s2"}
)}
2 : <CFString 0x100019a20 [0x100245ee0]>{contents = "Auxiliary Partitions"} = <CFArray 0x104301d00 [0x100245ee0]>{type = immutable, count = 0, values = ()}
}

Substituting ESP disk0s1
Mounting at /Volumes/bless.VPAp
Executing "/sbin/mount"
mount_msdos: /dev/disk0s1: Permission denied
Returned 18176
/sbin/mount returned non-0 exit status
Failed to determine auxiliary partition mountpoint for /
Error while writing firmware updater for EFI

And, reattempted using sudo, changed that last half to:

Substituting ESP disk0s1
Mounting at /Volumes/bless.Q7jK
Executing "/sbin/mount"
Returned 0
Creating /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE if needed
Deleting previous contents of /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE
Opened dest at /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE//MM41_0042_03B_LOCKED.scap for writing
preallocation not supported on this filesystem for /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE//MM41_0042_03B_LOCKED.scap

Type/creator set to / for /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE//MM41_0042_03B_LOCKED.scap
/Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE//MM41_0042_03B_LOCKED.scap created successfully

Relative path of /Volumes/bless.Q7jK//EFI/APPLE/FIRMWARE//MM41_0042_03B_LOCKED.scap is \EFI\APPLE\FIRMWARE\MM41_0042_03B_LOCKED.scap

IOMedia disk0s1 has UUID 35093651-F242-4276-B21B-F6698E9B1D0F
Write to RTC: 0
Could not find IODeviceTree:/options
Executing "/sbin/umount"
Returned 0
Error while writing firmware updater for EFI

Thoughts?
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Oddly enough, much like the original Snow Leopard install, despite the bless errors, the firmware update ran on reboot and seemed to install properly.

It did not, however, change the NVRAM situation at all. Still trying to dig through logs for some other clue.
 

saulinpa

macrumors 65816
Jun 15, 2008
1,257
716
You did the PRAM reset (cmd-option-P-R). Maybe also pull the battery. Replace the battery.
 

Niccador

macrumors newbie
Original poster
Sep 23, 2017
24
4
Dear God I feel stupid.

Nvram kb reset fixed the problem, although I had to go through a few wired kb to find one that work correctly. (None of my wireless kb's did the trick, nor any of my normal "fancier" wired kb's....had to find one of my cheapest "dumbest" wired kb's I had stashed, and it worked right off.)

One little kb shortcut and the whole thing is magically fixed, like night and day. Now to try installing High Sierra from scratch again.

EDIT:
High Sierra installed beautifully this time. Everything looking good, bit sluggish but that's probably the 2gb of ram. Time to invest in 8gb, and welcome this little box to it's second life. :)

Thanks so much for trying to help out.
 
Last edited:

guyguy17

macrumors member
Mar 31, 2017
86
10
I have the same issue as the OP with regards to a Mac mini 2010 and the computer hangs or halts for 5-10 minutes. I could use some help as well.

What was the fix or resolution?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.