Mac mini server hang at startup

My mac mini server (1st gen) installed with Lion server has a strange problem.
At some point, it stop to deliver it services (imap, dhcp and ical server). I connect on it (wich take a long long time), make it restart by the system menu entry.
It restart, and stay forever with the blank screen with Apple logo and the waiting circle which loop.
No way to restart.
I then boot on a Mountain Lion installation USB key (I loose my Lion one :-( ), choose the restore from time machine option, selecting the last entry on my Time capsule, everything goes well, and the server restart with no problem. I can even restart it by the system menu.
But after 2 or 3 month, it has the same problem, and again no way to restart without restoring the last time machine backup.
It's now the third time it does this, and it's make me go crazy.
I've try to start in verbose mode, and I have the following fsck error message :
disk0s2 : I/O error.
Invalid node structure
(4,26622)
the volume on macintosh hd could not ve verified completely
fsck failed !
I've try to start on single mode and do the fsck -fy -> same result.
Does someone has an idea of why it does this ?
Regards,
Marc

Just recently I ran into a problem when I tried to Verify my hard disk and when it tried to verify the catalog, it responded "Invalid sibling link." Repair Disk didn't work. I searched the web and Apple's site, and couldn't find anything useful except to buy DiskWarrior or reformat the drive. Knowing that OS X is built on Unix gave me a few clues on how to proceed. The solution is pretty simple:
    1.    Boot off the OS X CD (reboot, hold C while booting).
    2.    The installer will load up, go to Utilities in the menu and run Terminal.
    3.    Type df and look for the drive that has your Mac system mounted---you'll have to unmount this. On my MacBook Pro, it was /dev/disk0s2.
    4.    Type umount /dev/disk0s2, replacing disk0s2 with whatever disk your OS lives on.
    5.    Type fsck_hfs -r /dev/disk0s2. If you umounted the wrong thing, it will complain that you can't repair a mounted drive. Go back and umount the right thing and repeat this step.
Just for fun, you might want to run another fsck_hfs on your disk (use the -f option because your drive is probably journaled). Hope this helps someone so they don't buy a program that's going to do pretty much what we did with fsck_hfs, and so they don't waste time searching for an answer to no avail. By the way, TechTool Deluxe (3.1.1) didn't find the Catalog problem for some reason (you'll have this on a CD if you have AppleCare), which is why I resorted to fsck.
http://hints.macworld.com/article.php?story=20070204093925888

Similar Messages

Mac Mini Server Hangs, Gets Sluggish

New 2012 Mac Mini Server (2Gig i7 with 8GB memory). Server App is off, and I'm using it as a standalone unit. Running iTunes on an external Thunderbolt RAID. Running Safari with several tabs open. The iMac generally gets irratic within an hour or so: iTunes may be sluggish, Safari slows or stalls, then eventually the whole system hangs with the fan running at full speed. I have re-set the contoller by removing power for a while and then re-initializing. No help. Seems for a loaded iMac something is very wrong. Any guesses.

1. This comment applies to malicious software ("malware") that's installed unwittingly by the victim of a network attack. It does not apply to software, such as keystroke loggers, that may be installed deliberately by an intruder who has hands-on access to the victim's computer. That threat is in a different category, and there's no easy way to defend against it. If you have reason to suspect that you're the target of such an attack, you need expert help.
2. All versions of OS X since 10.6.7 have been able to detect known Mac malware in downloaded files. This feature is transparent to the user, but internally Apple calls it "XProtect." The recognition database is automatically updated once a day; however, you shouldn't rely on it, because the attackers are always at least a day ahead of the defenders.
The following caveats apply to XProtect:
It can be bypassed by some third-party networking software, such as BitTorrent clients and Java applets (see below.)
It only applies to software downloaded from the network. Software installed from a CD or other media is not checked.
3. Starting with OS X 10.7.5, there has been another layer of built-in malware protection, designated "Gatekeeper" by Apple. By default, applications and Installer packages downloaded from the network will only run if they're digitally signed by a developer with a certificate issued by Apple. Software certified in this way hasn't actually been tested by Apple (unless it comes from the Mac App Store), but you can be reasonably sure that it hasn't been modified by anyone other than the developer. His identity is known to Apple, so he could be held legally responsible if he distributed malware. For most practical purposes, applications recognized by Gatekeeper as signed can be considered safe.
Gatekeeper has, however, the same limitations as XProtect, and in addition the following:
It can easily be disabled or overridden by the user.
A malware attacker could get control of a code-signing certificate under false pretenses, or could find some other way to evade Apple's controls.
For more information about Gatekeeper, see this Apple Support article.
4. Beyond XProtect and Gatekeeper, there’s no benefit, in most cases, from any other automated protection against malware. The first and best line of defense is always your own intelligence. All known malware circulating on the Internet that affects a fully-updated installation of OS X 10.6 or later takes the form of so-called "trojan horses," which can only have an effect if the victim is duped into running them. The threat therefore reduces to a battle of wits between you and the malware attacker. If you're smarter than he thinks you are, you'll win.
That means, in practice, that you never use software that comes from an untrustworthy source. How do you know whether a source is trustworthy?
Any website that prompts you to install a “codec,” “plug-in,” or “certificate” that comes from that same site, or an unknown one, is untrustworthy.
A web operator who tells you that you have a “virus,” or that anything else is wrong with your computer, or that you have won a prize in a contest you never entered, is trying to commit a crime with you as the victim. (Some reputable websites did legitimately warn users who were infected with the "DNSChanger" malware. That exception to this rule no longer applies.)
“Cracked” copies of commercial software downloaded from a bittorrent are likely to be infected.
Software with a corporate brand, such as Adobe Flash Player, must be downloaded directly from the developer’s website. No intermediary is acceptable.
5. Java on the network (not to be confused with JavaScript, to which it's not related) is a weak point in the security of any operating system. If a Java web plugin is not installed, don't install one unless you really need it. If it is installed, you should disable it (not JavaScript) in your web browsers. Few websites have Java content nowadays, so you won’t be missing much. This setting is mandatory in OS X 10.5.8 or earlier, because Java in those obsolete versions has known security flaws that make it unsafe to use on the Internet. The flaws will never be fixed. Regardless of version, experience has shown that Java can never be fully trusted, even if no vulnerabilities are publicly known at the moment.
Follow these guidelines, and you’ll be as safe from malware as you can reasonably be.
6. Never install any commercial "anti-virus" or "Internet security" products for the Mac, as they all do more harm than good. If you need to be able to detect Windows malware in your files, use the free software ClamXav — nothing else.
Why shouldn't you use commercial "anti-virus" products?
Their design is predicated on the nonexistent threat that malware may be injected at any time, anywhere in the file system. Malware is downloaded from the network; it doesn't materialize from nowhere.
In order to meet that nonexistent threat, the software modifies or duplicates low-level functions of the operating system, which is a waste of resources and a common cause of instability, bugs, and poor performance.
By modifying the operating system, the software itself may create weaknesses that could be exploited by malware attackers.
7. ClamXav doesn't have these drawbacks. That doesn't mean it's entirely safe. It may report email messages that have "phishing" links in the body, or Windows malware in attachments, as infected files, and offer to delete or move them. Doing so can corrupt the Mail database. The messages should be deleted from within the Mail application.
ClamXav is not needed, and should not be relied upon, for protection against OS X malware. It's useful only for detecting Windows malware. If you don't need to do that, avoid it. Windows malware can't harm you directly (unless, of course, you use Windows.) Just don't pass it on to anyone else.
8. The greatest danger posed by anti-virus software, in my opinion, is its effect on human behavior. When people install such software, which does little or nothing to protect them from emerging threats, they get a false sense of security from it, and then they may do things that make them more vulnerable. Nothing can lessen the need for safe computing practices.
9. It seems to be a common belief that the built-in Application Firewall acts as a barrier to infection, or prevents malware from functioning. It does neither. It blocks inbound connections to certain network services you're running, such as file sharing. It's disabled by default and you should leave it that way if you're behind a router on a private home or office network. Activate it only when you're on an untrusted network, for instance a public Wi-Fi hotspot, where you don't want to provide services. Disable any services you don't use.

Mac Mini server hangs during periods of heavy outbound traffic

I first noticed this last night, when trying to set up Time Machine backups.
The backups will run for around 30 minutes on average, and then the Mini will go into a state where the mouse still works and most commands work, but no network-related things will work: the machine won't respond to pings; Networks preferences will hang when you try to open it; Server Manager will hang when you open it, and so forth.
This occurs regardless of whether I am using gigabit ethernet or wireless ethernet.
I swore it was Time Machine's fault, so last night I made sure it was turned off, and the machine was completely stable again in the morning so I thought things were okay.
But just now, I was watching a video over the network from a shared directory on the Mini, and it acted up in exactly the same way as before, and this happened twice in a row when watching two separate videos.
Interestingly, it seems to be okay to copy large amounts of data to the Mini, as over the past week I have copied around 1.5TB of data to the Drobo attached to it with no problems at all. It just seems like copying any amount of data away from the system dooms it to have a crash.
But there was a 10.6.2 update at some point during all of this, and I'm not confident that it wasn't the update which caused the problem.
Is anyone familiar with these symptoms? What can be done?

It's running Server (I cross-posted to the server forum after being advised to.) There is a gigabit switch on the way to a Billionton 7504VGO router/modem. The problem itself is separate from Internet connectivity though, as the computer becomes inaccessible from the local network when it occurs.
I think I am narrowing in on the problem though, as it seems to reproducibly occur on some files and not others. On the Time Machine side of things, if I exclude my home directory then it seems to work even for the initial backup which takes ages. On the sharing side of things, there are video files which crash it reliably and then others which don't. Interestingly it seems to be the newer files which work more reliably, which makes me think it's something about the files which were transferred to the Mac when the data was first brought over from the previous machine I was using.

Mac mini server (late 2012) - mLion 10.8 - hangs on startup

Just got a Mac Mini server late 2012 running mLion 10.8...out of the box...I was setting up my Server and the Wiki & profile manager went out. I surfed around and found a wipe solution (/Applications/Server.app/Contents/ServerRoot/usr/share/devicemgr/backend/wipeD B.sh) through terminal which did work. Later on they went out again after changing my host name or some ip options for the server but my Open directory started erroring as well. Tried to do the terminal thing and I got a error. So I shut-down and restart only to get the pinwheel screen. Tried safe mode (shift) to no avail. Then to lion recovery (cmd+r) which open the terminal and disk utility. ok. But from here I'm lost. I found somethings to check like fsck and chmod 775, checking/verify permissions but they didnt get it. I'm thinking its a permissions problem but I'm not sure. Any thought on what to check out from here?

6 hr reboot of mLion thru the cmd-r start up worked...it took me back down to 10.8.1 from 10.8.2...just had to reload some apple updates to the server.app and java....maybe some other things too...anything on mLion prolly...not sure yet, but all my apps and files were still there...
*The reboot didn't fix Profile Manager or Wiki in the server.app but it did get me back online and OD is ok again...
*Sifted some articles about the OD, wiki, PM stuff and my problem is similar to this https://discussions.apple.com/message/20561662#20561662
So...this thread is prolly in the wrong place srry bout that...Here's a link to the lion server board.
https://discussions.apple.com/community/servers_enterprise_software/mac_os_x_lio n_server

MAC Mini Server Startup Problems

Help!
MAC newbee. Just bought a new MAC Mini Server, got monitor connections in place; have wireless keyboard and trackpad; at startup I get the white screen with apple background then followed by a screen with a graphic with some rounded-corners rectangle; it just sits there with the rotating gear, rotating forever.
SUpports says I need a wired, USB, keyboard to get it started. Makes no sense to me. Help anyone? I am about to return the product--with disgust.

Below is my the answer to a previous helper. Yes, you need to start with USB before setting your devices to work with bluetooth. Thank you jut the same. Best, Larry
----------------my response-----------
Thanks. You are right. I bought a cheap USB keyboard and mouse and have been doing fine ever since. All's well and working.
There is a rather subdued mention of the need for an initial USB connection in the documentation, however, you'd think that sales--that department is a bit on the weak side--would have said something to me while putting my order together for bluetooth devices only.
Oh well....have been doing fine ever since...all set up. Again, sincere thanks.

HT4805 Mac mini server startup

I purchased a used Mac mini server and can get past the startup screen for the setup process. There is a little spinning wheel in the lower left hand corner of the initial server setup screen. Anyone see this before?

Did you erase the boot drive and reinstall from the original media? That should be the first thing you do after buying a used computer. You of course ran the Apple Hardware Test before buying it.

Mac Mini Server Boot Camp Windows 8.1 White Screen Issue

Hello Apple Peeps!
I have a Mac Mini Server 2012 which I have had for around 6 months. I use it quite a lot mainly for Music Production on the OS X side and Graphic Design on the Windows side.
I recently decided to factory restore it as I wanted to spring clean it and reorganise the way some of my apps were installed. The way I had it set up was it was running OS X on one SSD and Windows 8.1 (installed using Boot Camp) on the other SSD. The way I went about the factory restore was I first used disk utility to erase/format the Windows SSD to Mac OS Extended (Journaled) and then went about the factory restore of OS X onto the other SSD as normal (following instructions from the Apple website).
The issue I am having now is that my newly installed Windows 8.1 (used solely on a single SSD) is hanging on a white screen for quite a long time before the Windows splash screen shows up, where before when I would boot or restart into Windows there was no white screen and it would go straight into the Windows splash screen and load to the desktop very quickly.
So my question is...
Why do I get this prolonged white screen before the Windows 8.1 splash screen appears? How can I get rid of it? It was certainly not present on my previous installation. Can anyone advise me what the computer is doing during this time so that I can do some further research into a solution.
What I have tried already....
1) PRAM & SMC reset.
2) Setting the startup disk to Boot Camp in both OS X and Windows 8.1.
3) Reinstalling Windows 8.1 through Boot Camp.
MAC MINI SERVER (LATE 2012), 2.6GHZ QUAD CORE I7, 16GB RAM, 2 x 256GB SSD, OS X 10.10.2, Windows 8.1 (Retail), Boot Camp Assistant (5.1.3), Covered By AppleCare.
I would really appreciate some help with this ;-)

I have right clicked on each SSD in Device Manager and selected the option 'Properties' from the drop down menu, which brings me to this window...
I'm not sure where I can find Device Attributes, I have clicked on each of the tabs in the window above, as far as I can see none of them mention AHCI enabled or anything similar. Thanks for all of your responses by the way...much appreciated!

Mac Mini Server will not go into recovery?

I've just bought a Mac Mini Server 2012 model, and when I try and boot to recovery or safe mode, the boot hangs, then the machine restarts with the 'Your computer restarted because of a problem' message. The machine boots to normal mode fine, and can also boot to startup manager, which shows a recovery partition. I've tried resetting the NVRAM, as well as booting straight from Apple's servers. Both have not helped. The previous owner said he reinstalled OSX from recovery before he gave it to me, which leads me to believe it could be something other than a faulty drive. In addition, Disk Utility has not thrown up anything. If anyone could shed some light on this at all it would be very much appreciated as I'm starting to get a little bit annoyed!
Thanks.

The first thing you should do after acquiring a second-hand computer is to erase the internal drive and install a clean copy of OS X. How you do that depends on the model. Look it up on this page to see what version was originally installed.
If the machine shipped with OS X 10.4 or 10.5, you need a boxed and shrink-wrapped retail Snow Leopard (OS X 10.6) installation disc, which you can get from the Apple Store or a reputable reseller — not from eBay or anything of the kind. If the machine has less than 1 GB of memory, you'll need to add more in order to install 10.6. I suggest you install as much memory as it can take, according to the technical specifications.
If the machine shipped with OS X 10.6, you need the gray installation discs that came with it. If you don't have the discs, order replacements from Apple. A retail disc, or the gray discs from another model, will not work.
To boot from an optical disc, insert it, then reboot and hold down the C key at the startup chime. Release the key when you see the gray Apple logo on the screen.
If the machine shipped with OS X 10.7 or later, it should boot into Internet Recovery mode when you hold down the key combination option-command-R at the startup chime. Release the keys when you see a spinning globe.
Once booted from the disc or in Internet Recovery, launch Disk Utility and select the icon of the internal drive — not any of the volume icons nested beneath it. In the Partition tab, select the default options: a GUID partition table with one data volume in Mac OS Extended (Journaled) format. This operation will permanently remove all existing data on the drive, which is what you should do.
After partitioning, quit Disk Utility and run the OS X Installer. When the installation is done, the system will automatically reboot into the Setup Assistant, which will prompt you to transfer the data from another Mac, its backups, or from a Windows computer. If you have any data to transfer, this is usually the best time to do it.
You should then run Software Update and install all available system updates from Apple. If you want to upgrade to a major version of OS X newer than 10.6, buy it from the Mac App Store. Note that you can't keep an upgraded version that was installed by the previous owner. He or she can't legally transfer it to you, and without the Apple ID you won't be able to update it in Software Update or reinstall, if that becomes necessary. The same goes for any App Store products that the previous owner installed — you have to repurchase them.
If the previous owner "accepted" the bundled iLife applications (iPhoto, iMovie, and Garage Band) in the App Store so that he or she could update them, then they're linked to that Apple ID and you won't be able to download them without buying them. Reportedly, Apple customer service has sometimes issued redemption codes for these apps to second owners who asked.
If the previous owner didn't deauthorize the computer in the iTunes Store under his Apple ID, you wont be able toauthorize it under your ID. In that case, contact iTunes Support.

FileMaker Server problem on Mac Mini Server - Mac Mini won't boot

I just installed a brand new Mac Mini Server today, and also FileMaker Server 11. A first-timer for both Mac OS X Server and FileMaker Server, I made an error as explained below, and right now I don't know how to get back on track with the system. It won't boot.
So, how did this happen?
At first everything was proceeding according to plan. I configured the pre-installed Mac OS X Server on the Mac Mini with users, groups and services. This was tested from clients and this seemed to work just fine. Then I installed and configured FileMaker Server. This was also tested from a client, and the example database that came with FMS was served up just fine.
The problem arose when I tried to install my existing FileMaker databases. I simply checked to see where in the file system the example database was located, and then copied my old databases to that location (I think it was Library > FileMaker Server > Data > Databases or something close to it - can't check it now...). I had the FileMaker Server Admin Console running, and hit the Refresh button hoping that this would make FileMaker Server find the databases.
This was my first error. I should have read ahead in the instructions to see that one is supposed to use an Upload Database assistant instead...
What happened when I hit refresh was that the FileMaker Server Admin Console became completely unresponsive with a spinning ball as cursor. I left it for about an hour hoping it would terminate, but gave up and tried to shut it down. It wouldn't close, so I force quit it from the Finder. Then I tried to shut down FileMaker Server, but I needed to force quit this as well. After this I thought it would be best to reboot the Mac Mini, so I shut it down, but now it won't even boot, it just stays on the screen with the spinning wheel for ever!
I have tried all the keyboard options while booting, but nothing seems to help. In safe mode, the grey progress bar just grows to about one third, then disappears and leaves the eternally spinning wheel.
The server version of the Mac Mini doesn't have an optical drive, only two internal hard drives. I tried to reinstall from scratch using the optical drive on another Mac on the network. The startup disk appeared when I tried to boot the Mac Mini holding down the option key, and after about 20 minutes or so of the spinning wheel I could actually access the discs. I started by running Disk Utility to check disk permissions. There were a lot of repairs concerning permissions and groups, especially on "Library". It said "ACL differs on Library", I don't know what this is but this was repaired. I then ran Repair Disk. The volume appeared to be OK.
When I tried to reinstall Mac OS X Server however, this failed with the message
"You can't upgrade this version of Mac OS X because a newer version is installed. Mac OS X Server couldn't be installed on this disk." I don't know how this can be, but I may have run software update earlier today.
What should I try next? Should I erase the primary HD and try to install again? Or should I install the system software on the secondary HD? Or should I just try to reboot as is in the hope that the disk permission repairs did the trick...?
Any helpful pointers would be greatly appreciated!

Hello there, I came across your post when browsing the forum for passive advice. I am in the same boat as you and am a first timer for both of these tools. I work for a company who now needs to expand its network and database capabilities. I have been assigned this task and these are the tools i have opted for. I have not yet purchased them and i am pleased to find someone who has my desired setup. Could you please advise on the simplicity of the setup and whether an advanced knowledge is required.
I want to use it in a mixed operating system environment. Is this possible?
Regards
Matthew

Getting AHT to work on Mac mini server

I have a intel core 2 duo Mac mini server (macmini4,1), and I'm having sporadic freezing/locking issues. I am trying to run the apple hardware test but it doesn't work, holding down the 'd' key does nothing. If I try single-user mode startup it works fine so there doesn't seem to be an issue with the keyboard. Since this is the server I also don't have an optical drive to go to to boot from the install disc. Why doesn't this work? Is there an alternative way to get this to run that doesn't involve the install disc?

Actually, this problem is only partially solved. I still get "Can't connect to local MySQL server through socket '/var/mysql/mysql.sock..." when I type 'mysql'. I can access mysql by typing 'sudo mysql', but still get the socket error when connecting via php, so I think I still need to get to the point where I can type mysql without sudo.
Also, I went ahead and installed MySQL 5 with the tar package.
Message was edited by: rabbitdog

Mac Mini Server freezing in install when choosing PPPoE

I have a Mac Mini Server and when I go through the installation procedure and choose the connect PPPoE from the Network settings, the installation hangs every time.
I have already tried several clean installs from the Mac Mini Server disc to no avail.
Suggestions?
Thank You.

What part of the install process do you have trouble with? I'm assuming, and I think Tony did as well, you're talking about the server setup assistant that launches once the OS is installed. Naming your server/domain is a critical part of setup, as is DNS. If you put faulty configs in during setup, or try to setup services before DNS is working, you'll run into trouble - so please include whatever you're trying to do - if you're new to servers, most everybody around here will be helpful or at least understanding.
In any event there's a great tutorial at
http://www.wazmac.com/serversnetwork/fileservers/osxserversetup/index.htm
While I agree with Tony that PPPoE isn't the best bet, you ought to be able to make it work - but you will need a static IP for your server. Best bet is probably to make it a static IP on your LAN using NAT and let your router/firewall have the live IP. But more info is always better - what are you trying to setup and what other equipment/network stuff is already going on? There are a lot of ways to setup a server and to setup a network, and there is certainly no one correct solution. Somebody smart (like Tony) may be able to give you a lot more options with more details. I'll try too, but I'm far from the most knowledgeable person around these parts.
Another thought - if you're not using the advanced server, I believe you need DNS set up beforehand somewhere - if you just enter your ISP's DNS server info, it won;t have any records for your server. The Wazmac setup notes will walk you through setting up your own DNS for your LAN and using your ISP's DNS for everything on the WAN side.
Message was edited by: Jeff Kelleher

Mac Mini Server freezes hard, too hot?

Hi,
Our Mac Mini Server (half a year old) with the newest system crashes hard now and then.
It could run for up to three weeks occasionally but now in the summer it could sometimes only run for minutes until it hangs hard with frozen mouse and clock.
I have found no other way than resetting by the power switch.
According to the technical specification it should handle up to 35°C environment. (Right now we have 28°C in the room here.)
It seemed to help a bit by installing smcFanControl and increase the fan speed.
It will crash even without any work being done on it. No special applications started. No network traffic.
If the exhaust temp is above about 32 to 34° the problems seem to worsening. Now it is 37°C despite full fan speed (5500 rpm) and it crashed after minutes.
Sometimes it will even hang during the boot process.
Have anybody else heard about such problems?

Hi MalcomKay,
I had to open a service ticket as Jiri suggested. The technician was pretty sure the crashes were caused by a defective Airport board and exchanged that (despite I doubted that and never used Airport for the server).
I came back home (2x2x120 km of travel) and started the Mac Mini Server up. I booted and run the AppleServerDiagnostics.app test from an USB. It lasted 15 minutes (until it was warmed up) and then crashed so hard it was not counted by the test. It just froze hard. It crashed when running the memory test. It always crashed before finish when running that test!
I returned the server to the Apple Service (another 480 km of travel). This time they exchanged the whole motherboard. They tested it running intense traffic and operations for one full week without a freeze. So it was a faulty mother board!
Now it has been running like a charm for months.
This is not the first temperature problem affected board Apple has delivered to me.
Good luck! /Johan
Tips: Prepare an USB stick you can boot from. It is so frustrating to have a computer without a dedicated DVD where you can boot from and run the hardware tests.

Instability in 2012 Mac Mini Server after Yosemite 10.1.1 Install

I bought a NEW 2012 Mac Mini server on clearance in the online Apple Store last month. I had a 256 SDD installed as startup drive along with Yosemite earlier this week. It crashes, freezes and randomly restarts. Not sure where to start with trying to figure this out. Any help would be greatly appreciated.
It happens under various circumstances but here is the report on the latest that happened a few minutes ago. I had clicked on the Desktop Icon "Macintosh SSD", the boot drive. I got the spinning wheel and then a spontaneous restart.
I apologize if too much of the report is included here. Not sure where to stop.
Crash-panic Report. When I clicked on Macintosh SSD (Boot Drive) I got a spinning wheel followed by a system restart.
Anonymous UUID: C76AE31B-9D00-CD21-F920-DF88D8F8A0C9
Fri Jan 23 12:15:49 2015
*** Panic Report ***
panic(cpu 6 caller 0xffffff8004fc4594): "launchd died\nState at Last Exception:\n\n"@/SourceCache/xnu/xnu-2782.1.97/bsd/kern/kern_exit.c:361
Backtrace (CPU 6), Frame : Return Address
0xffffff8018f13e50 : 0xffffff8004b3a811
0xffffff8018f13ed0 : 0xffffff8004fc4594
0xffffff8018f13f40 : 0xffffff8004fc425c
0xffffff8018f13f50 : 0xffffff800504dcb2
0xffffff8018f13fb0 : 0xffffff8004c3ac46
BSD process name corresponding to current thread: launchd
Mac OS version:
14B25
Kernel version:
Darwin Kernel Version 14.0.0: Fri Sep 19 00:26:44 PDT 2014; root:xnu-2782.1.97~2/RELEASE_X86_64
Kernel UUID: 89E10306-BC78-3A3B-955C-7C4922577E61
Kernel slide: 0x0000000004800000
Kernel text base: 0xffffff8004a00000
__HIB text base: 0xffffff8004900000
System model name: Macmini6,2 (Mac-F65AE981FFA204ED)
System uptime in nanoseconds: 10149976048674
last loaded kext at 9896523213358: com.apple.iokit.SCSITaskUserClient 3.7.0 (addr 0xffffff7f87299000, size 36864)
last unloaded kext at 9957569541796: com.apple.driver.AppleUSBCDC 4.2.2b5 (addr 0xffffff7f87295000, size 16384)
loaded kexts:
com.apple.filesystems.msdosfs 1.10
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AGPM 100.14.37
com.apple.driver.ApplePlatformEnabler 2.1.0d1
com.apple.driver.X86PlatformShim 1.0.0
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.1f2
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleMCCSControl 1.2.10
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleHDA 267.0
com.apple.driver.AppleMikeyDriver 267.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleIntelHD4000Graphics 10.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleLPC 1.7.3
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.driver.AppleHV 1
com.apple.driver.AppleIntelFramebufferCapri 10.0.0
com.apple.driver.AppleThunderboltIP 2.0.2
com.apple.driver.AppleIRController 327.5
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.6.5
com.apple.driver.AppleUSBHub 705.4.1
com.apple.driver.AirPort.Brcm4360 901.19.10
com.apple.driver.AppleSDXC 1.6.5
com.apple.iokit.AppleBCM5701Ethernet 10.1.2b3
com.apple.driver.AppleFWOHCI 5.5.2
com.apple.driver.AppleAHCIPort 3.0.7
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBXHCI 705.4.14
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.0
com.apple.iokit.IOUSBMassStorageClass 3.7.0
com.apple.driver.AppleBluetoothHIDMouse 185.3
com.apple.driver.AppleHIDMouse 185.3
com.apple.driver.IOBluetoothHIDDriver 4.3.1f2
com.apple.kext.triggers 1.0
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 267.0
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOAudioFamily 200.6
com.apple.vecLib.kext 1.2.0
com.apple.iokit.IOSurface 97
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOFireWireIP 2.2.6
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.0d49
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.1f2
com.apple.iokit.IOBluetoothFamily 4.3.1f2
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOAcceleratorFamily2 156.4
com.apple.AppleGraphicsDeviceControl 3.7.21
com.apple.driver.AppleHDAController 267.0
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.iokit.IOHDAFamily 267.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.0
com.apple.driver.AppleHIDKeyboard 175.5
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.driver.AppleThunderboltDPInAdapter 4.0.6
com.apple.driver.AppleThunderboltDPAdapterFamily 4.0.6
com.apple.driver.AppleThunderboltPCIDownAdapter 2.0.2
com.apple.driver.AppleThunderboltNHI 3.1.7
com.apple.iokit.IOThunderboltFamily 4.2.1
com.apple.iokit.IO80211Family 700.52
com.apple.iokit.IOEthernetAVBController 1.0.3b3
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOFireWireFamily 4.5.6
com.apple.iokit.IOAHCIFamily 2.7.0
com.apple.iokit.IOUSBFamily 705.4.14
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 389.1
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
System Profile:
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x10E), Broadcom BCM43xx 1.0 (7.15.124.12.10)
Bluetooth: Version 4.3.1f2 15015, 3 services, 27 devices, 1 incoming serial ports
Thunderbolt Bus: Mac mini, Apple Inc., 23.4
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655302D474E2D4620
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738454655302D474E2D4620
USB Device: Hub
USB Device: Hub
USB Device: Hub
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Serial ATA Device: OWC Mercury Electra 6G SSD, 240.06 GB
Serial ATA Device: HGST HTS721010A9E630, 1 TB
Model: Macmini6,2, BootROM MM61.0106.B03, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.8f0
Network Service: Ethernet, Ethernet, en0
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Glad that you got it solved, John. That model was only replaced at the end of last year, it is not that old and far better in terms of flexibility than the current models. Although the current models are growing away from SATA and towards PCI which, in its logical conclusion, will be faster ito access (read and write), speeds.
Linc's advice was 100% spot-on.
Have fun with your 'new' Mini
Leo

Dual boot Windows 7 on Mac Mini Server

I have a Mac Mini server (2012) with two 1tb harddrives. One has osx Mavericks installed and I have been using it for the past 5 months. The other is completely empty. I was wondering if i could partition the empty drive and install Windows 7 on it from a disc? will I have to put osx on the empty drive, or can I just boot into windows at startup by holding option? I would like to keep about 800gb of the extra drive to use for extra storage of mac files.
Thanks for any help/suggestions you may have!
Elliot

You would think it would be possible to have one drive for OS X and the other for Windows but this is not (quite) the case. If you want the second drive to be as near as possible dedicated to Windows you need first to install or copy to it OS X including the BootCamp Utility. Run the Boot Camp utility and allocate the minimum amount of space to OS X and all the rest for Windows. Then as normal install Windows.
You could after you have got Windows installed erase the (small) Mac partition.
It is necessary to do it this was as the BootCamp Utility partitions the boot drive (and only the boot drive) in to a special scheme that makes it able to run Windows on a Mac.

2010 Mac mini server remote install OS X failure

I tested re-installing OS X remotely to my 2010 Mac mini server. It worked the first time. I got to the installation process, and abandoned it without actually doing anything.
But when I tried again, it failed, and I have not been able to get it to work ever since. I went to a local Apple shop and tested at its Genius bar. People there cannot figure out the problem. They exchanged my unit for a new one.
I took the new unit home, tried, and it failed again. Then I called Apple Care. They cannot pin-point the problem, but suspected that, since I failed with two units, the problem may be with the computer that has the DVD. I am not sure about his. Here I post my story for help. The details:
1. The OS X Server installation DVD (which came with the mini) was put in a 13" 2009 Macbook Pro. There I ran the Remote Install OS X application. Selected the Installation DVD.
2. Then I started the Mac mini server, holding the down Opt key. The Installation DVD appeared from my local network. However when I selected the DVD and clicked the arrow sign under it, things went wrong. A circle with a line segment appeared briefly (indicating a problem, I think). Then the mini simply went to boot from its own hard drive where the original OS X was.
Help and suggestions are very much appreciated.
Additional information:
Remote Disc works fine. From my Mac mini, after booting into the original OS, I can see and open DVDs in the Macbook Pro.

Target disk mode method works fine. I can boot my mac mini from its installation DVD placed in my macbook pro, connected to the mini through firewire. So I don't think there is any hardware problem.
I played with a few other things. First I used another DVD, this time the one that came with my 2009 macbook pro, a non-server version OS X. When I tried to remote install it to my mini, the mini can still see the DVD but it hung after I chose to boot from it. It just showed a big circle with a line segment. It did not revert to boot the OS on its own hard drive.
Next I again ran remote install on macbook, but booted the mini to its own hard drive. From there
I changed its start up disk to Network Startup, and rebooted. The mini can find nothing on the local network.

Mac mini server hang at startup

Similar Messages

Maybe you are looking for